# ContextPulse

Canonical product surface: https://init.ydefix.build/#contextpulse

## What is ContextPulse?

ContextPulse is the first public `/init` instrument: a private-dogfood,
local-first iOS observatory for personal and mental performance. It helps one
person ask better questions about the conditions surrounding focus, recovery,
learning, decisions, creative work, and relationships.

It is not another universal score and not an automated life coach. It keeps the
distance between a record, a possible pattern, an interpretation, and a bounded
next step visible.

## What is live now?

- Current development milestone: **v0.6.0 (10) · in review**
- Release receipt: **candidate project metadata verified; exact-head physical-device verification pending**
- Product state: **private dogfood**
- Public phone: deterministic, content-free reference rendered from a pinned app contract
- Private-pod sources shown as current: Spotify, GitHub, X, WHOOP
- On-device sources shown as current: Apple Health, Calendar, Screen Time, CarPlay
- Planned adapters: Gmail, Claude, ChatGPT, Kimi, Hermes, OpenClaw

A source name identifies an input or planned adapter, not an endorsement. The
0.6.0 milestone and build 10 project metadata are current product scope, but the
candidate does not become a released build until a matching physical-device
receipt updates the showcase manifest.

## How does ContextPulse turn data into something useful?

1. **Data** — content-minimized observations such as time, duration, count, coverage, and user-marked protocols.
2. **Finding** — a relationship worth checking, with lag, missingness, sample quality, alternatives, and confounders attached.
3. **Insight** — a clearer personal question: what repeats, what changed, and what else could explain it?
4. **Bounded action** — a reversible next observation or experiment; never a diagnosis or causal command.

## What kinds of patterns can it examine?

Signals that normally live in separate tools can become comparable context:
sleep and recovery, listening and media, work blocks, meetings, communication,
movement, screen habits, seasonal context, and user-marked routines such as meal
timing, study method, caffeine cutoff, fasting windows, or supplement use.

Those routines are observations chosen by the user. ContextPulse does not
prescribe fasting, diet, medication, or supplement dosing.

## Why include unusual correlations?

Unexpected combinations can reveal a question a person would never think to ask.
The public site may illustrate examples such as low sleep plus listening context
plus a calendar window appearing alongside weaker client-meeting outcomes, or
time on X exceeding television appearing alongside more online relationship
building.

Every public example is labelled **SYNTHETIC ILLUSTRATION · NOT MEASURED**. These
examples contain no real user data, measured effect, confidence interval, or
causal conclusion. Chance, selection, travel, illness, workload, pipeline stage,
and many other confounders may explain an apparent relationship.

## Privacy boundary

The intended architecture keeps raw source data and credentials on the person's
devices or personal pod. Supported flows discard content that is not needed,
including prompts, commands, message bodies, meeting titles, and routes. Derived
metadata remains sensitive even after redaction.

The public website does not query the personal pod, native app, capture fabric,
HealthKit, or private analysis runtimes. It contains semantic product copy,
synthetic fixtures, local integration marks, and a sanitized showcase manifest.

## Is ContextPulse medical software?

No. ContextPulse is a personal wellness, reflection, and performance instrument,
not a medical device. It does not diagnose, treat, prescribe, or guarantee an
outcome. High-stakes health or medication decisions belong with qualified health
professionals, not an observational association.