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
This is one of the two youngest segments — what’s listed is what’s real today.
- A habit tracker built for honesty: tap-to-check with idempotent toggles (tap again to undo), streaks recomputed server-side per request so the display never goes stale, and archiving that preserves check history instead of deleting it.
- A Health page on the dashboard where habits fold into the wider health picture, sharing the combined “Health Wealth” tile on the launcher.
- Domain participation — health items ride the same machinery as everything else: events and to-dos carry the domain, conditions can reference it, and sleep windows already participate in the cascade engine’s timezone-conflict detection.
What’s next
Fitness blocks as first-class time-blocks the scheduler defends, richer signals feeding the morning brief, and habit outcomes joining the labeled-example corpus like every other evaluation in the system.
Development log
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.