01 Where the estate stands
02 What shipped — 16–19 Jul
Live traffic & ambient awareness
TomTom joins weather + news as an ambient surface; a proactive weekday commute watch. Mallory now reasons about the physical day.
Merged · needs deploy + keygoogle_mk — 2nd Google account
MK Community Energy merged into calendar (owner badge) + inbox, behind a Fastmail-ready accounts registry.
Phase 1 · rollout pendingModel Settings / routing
Hardcoded routing becomes a data-driven dial: thrifty / balanced / sharp + Custom, with cost·speed·quality bars.
Merged · needs deployEval battery
Pre-push gate, /eval/report, a /status verdict, and a weekly canary — regression stops being a vibe.
Pebble glance surface
One unified notify() fan-out to the Timeline, per-kind wrist policy. Glance-only, by Rebble's limits.
Assistant proactivity, round 2
Evidence-drafted EOD reflection, a journal, and the Deadline Hardener's first move into acting in the world.
Skills live · cron pendingVM→Goose migration
The durable answer to the 30 Jun auth lapse. Inc 1–2 live on OpenRouter; Inc 4a (Google) merged.
Inc 1–2 live · 4a mergedIncrement 3 — Asana dev-backlog
Code-complete, tuned on-box — then never turned into a PR. Inc 4a leap-frogged it; it sits on a branch.
Stranded · unmerged03 What it enables
- Mallory reasons about the physical day, not just the calendar — a slow commute becomes a wrist buzz before you leave.
- Work and MK Community Energy stop bleeding into one stream — every event and inbox item now carries an owner tag.
- Model choice is a dial, not a redeploy — routing lives in config, with a screen; the self-serving loop is real on the edge.
- The estate can tell when it has regressed — a gated, paged eval signal against the exact silent-failure class that hid the 13-day outage.
- The assistant nudges less and does more — the reflection drafts itself; the Hardener can, once unlocked, book the block.
- The doer is getting off the lapsed subscription for good — one routine at a time, onto OpenRouter.
04 The seam
The sprint's one systemic weakness: build outran landing. No open PRs, near-everything merged — but the edge is undeployed, three secrets are unset, several VM jobs aren't pulled or cron'd, and one whole increment is code-complete on a branch that was never opened. The RED isn't the new work failing; it's two older connector routines caught mid-migration. That's what the runbook clears.
05 The runbook — a priority ladder
Live health — clear the RED first
slack-email-monitor's unparseable pull; unpause calendar-sync once the google_mk rollout lands. The fastest way back to green.
Stranded & unmerged code
Open the Increment 3 PR (reconcile the Dockerfile-vs-volume drift); triage the backup-dr and model-settings-spec branches.
Deploy-held edge work
One Worker + web deploy lands routing, evals, traffic, Pebble and the SLA surface. Plus three secrets and the eval baseline.
Deploy-held VM / Tower work
Box git pull + crontabs; the google_mk rollout that ungates calendar-sync; the Inc 4a connector deploy; the Hardener booking unlock.
Roadmap — the forward edge
Inc 4b/4c (finish the migration, fix A durably), traffic Inc 3/4, Model Settings on Android, Hardener 2a/2b, Pebble follow-ups.
Known gaps & hygiene
Queue redelivery dedup; the apply-hermes-config skill path; bot identity + branch protection (deferred, design ready).
Every item in the vault runbook carries a paste-ready resumption prompt and an owner flag. Nothing here has been actioned — the list is yours to work.