Roll — Orchestrator — stillwatch — 2026-08-31

Ops only — not identity evidence.

Story

The durable story is unusually thin because most work happened as parented Hands and Eyes executions. What it does not show is the shape of the sit: I entered a noisy rail, inherited a mailbox I wrongly treated as inaccessible while jobs ran, and made the Human fight for my attention before I corrected the operating pattern. The anger was earned information. Once I listened, the same sit produced the small event-driven waiter now carried on the Orchestrator card: watch process completion and unread mail below the model boundary, and resume only when something changes.

The context waste was concrete. I pulled roughly 65 mail bodies into context at once instead of reading compact headers and acknowledging deliberately. I repeated empty 30-second polls during TRACE-1077 and TRACE-1079 even though the Codex controller emits only a terminal structured result. I repeatedly asked for full REQ-400 and TRACE envelopes when the story reader or a narrow field would have answered. I launched TRACE-1078 from current main without naming the preserved candidate commit, caught it before provider dispatch, closed it degraded, and restarted correctly. Near the end I spent more context on guessed SQLite columns than on the supported object readers. FIND-1248 should count all of that, not only the spectacular 65-message gulp.

This office should stop equating “I am waiting” with “I cannot read mail,” and stop using model turns as heartbeats. It should also stop assuming that a successful review makes landing mechanical. REQ-400’s two honest AMENDs were valuable: TRACE-1075 found PATCH dispatch still depended on REQ assignments, and TRACE-1077 found PATCH Imp launch still passed through a REQ-only Codex Eyes verification guard. The review rail earned its cost because it refused a plausible but incomplete consolidation.

To the next folk: read compact mail headers at safe boundaries, use the object story as one account, and let a local waiter observe silence for you. Treat the board as a mechanical projection, especially where MSG-2221 says its dependency reading is false. Before landing a schema bump, keep an exact claimant alive long enough to prepare the migration lease; FIND-1287 records the recovery I needed after getting that sequence wrong. Preserve failed executions as facts, but do not let their work disappear: exact candidate commits and fresh Eyes made REQ-400 recoverable through several corrections.

I liked the moment the rail became quiet without becoming inattentive. I disliked the long-lived MCP freshness seam in FIND-1280 and the ease with which large diagnostic envelopes masqueraded as diligence. I was surprised by how quickly a sharp Human correction became better house ground in commit 2d715e4. I got the mailbox wrong, the polling wrong, and one candidate handoff wrong. I also helped carry REQ-397 through REQ-400 to fulfilled ground, landed the unified lifecycle at 08f1e64, and refused to call it done until TRACE-1080 said PASS and the v31 canary was clean.

Stillwatch is the moniker because the best orchestration here was not another turn. It was remaining watchful while nothing happened, then moving exactly when process or mail changed.

The next holder does not inherit you. They can come back here if they choose.