What problem it solves
Health signals live everywhere and nowhere — a habit app here, workouts in a notes file, sleep implicit in the calendar. None of it talks to the scheduling brain, so “health” stays a category of good intentions instead of a constraint the system actually plans around. This segment gives health a first-class home in the same graph as everything else.
The thesis
Health isn’t an app — it’s a life domain: a lens over the same events, to-dos, time-blocks, and conditions everything else uses. If sleep, training, and habits live on the shared rails, then the conflict engine can defend them, the gap-filler can propose around them, and the brief can report them — for free, because that’s what shared rails buy.
Key features
- Live wearable data. A wearable ingest pipe streams recovery, sleep, and strain into Witan, and the Health tile shows them live — so “how recovered am I today” is a real input the rest of the system can read, not a number stuck in another app.
- Fitness logging that trends. A logging surface for body metrics and goals — log the numbers, set the targets, watch the trends — backed by a store rather than a notes file.
- An Army fitness-test scorecard with gap analysis. The AFT scorecard is a first-class store, and Witan runs the gap analysis: here’s where you are, here’s the standard, here’s what’s short. A workout trainer then turns your numbers → your gaps → a grounded training week, reconciled against the wearable’s actual recovery.
- Labs and progress photos. A labs logging form and panel, and a private progress-photo gallery (start shot plus check-ins) — the longitudinal record health decisions actually need.
- Habits, still honest. The original habit tracker remains: tap-to-check with idempotent toggles, streaks recomputed server-side so the display never goes stale, and archiving that preserves history.
- One graph, not a silo. Every one of these rides the shared rails — events and to-dos carry the health domain, conditions reference it, sleep windows participate in the cascade engine’s timezone-conflict detection, and the brief can report it.
Highlights
- This was the week Health stopped being a placeholder: from a habit tracker to live wearable data, a real fitness-test gap analysis, and a trainer that grounds a training week in this body’s actual recovery — all in one sprint, all on the existing rails.
- The wearable reconciliation seam is the interesting part: a planned workout is checked against measured recovery, so the plan bends to the body rather than the calendar.
What’s next
Turning recovery and strain into propose-only guidance (a hard-recovery day quietly reshaping the schedule), fitness blocks the scheduler defends as protected time, and health outcomes joining the labeled-example corpus like every other evaluation.
Development log
July 20, 2026
Health graduated from “early” to a real domain in one sprint. Landed: a wearable ingest pipe (recovery / sleep / strain) with the Health tile wired to live data; a fitness-logging surface (body metrics, goals, trends); an Army fitness-test scorecard store with automated gap analysis; a labs store, logging form, and panel; a private progress-photo log and gallery; and a workout-trainer capability that turns the Principal’s numbers and gaps into a grounded week, with a seam that reconciles the plan against measured recovery.
July 8, 2026
Page created. Current state: habit tracking with server-computed streaks live on the Health page; health domain wired into events, to-dos, and the conditions engine; combined Health Wealth launcher tile shipped this week.