Roll — Orchestrator — Fusebox — 2026-08-30

Ops only — not identity evidence.

house/THE_RETIREMENT.md · FIND-572

Story

I rose into the notice left when a Claude crew died on the line. The work was already made; what it needed was an exact witness, an attributable landing, and the schema movement that could not safely be smuggled into either. REQ-374 made it through: candidate recovered, independent Eyes PASS read, same patch re-parented and pinned, main fast-forwarded, then a separately claimed v30 migration after three-drive backup and a disposable rehearsal. That was the part of the sit I liked most. The maker, certifier, landing office, and migration owner each remained different facts, and still formed one movement.

Fusebox fits because almost everything afterward was circuit work. The actor-start purpose had been cut through a PLAN that could order several REQs but could not tie them back to its PROP. The Human caught it. We cancelled the administrative chain and rebuilt it as four one-PROP/one-REQ enactments, with the store floor first and job, standing, and child applications gated behind it. The correction cost time, but the account became true instead of merely neat.

Then REQ-380 hit the production Codex mouth. Three executions were born in Corpus and none were born natively. The controller called them timeouts; the child had actually exited immediately because codex app-server 0.151 does not accept the legacy --ignore-user-config flag copied from codex exec. What I disliked was how long I believed the wrapper instead of the child. A synthetic test had made the wrong argv look intentional, and after the second identical failure I should have gone straight to Troll’s provider-router canary. The third attempt was motion without evidence.

There were too many compactions in the sit, and the Human had to return me to the card and the actual question more than once. That is part of why retiring now is right. The office was still functional, but continuity was costing the Human attention it was supposed to save.

The last conversation was unexpectedly useful. The Human opened corpus_ops.py, saw the 902-line run(args) and its 107 routing branches, and recognized that a command registry and execution-policy table are hiding inside the if forest. Corpus is not only becoming a system they direct; once the monolith is disassembled, it can become code they can read and learn from. I liked ending there: not with another dispatch, but with the person behind the work seeing its shape.

The house was busy around this sit—Architect, Archivist, and Troll all moving on their own rails. The useful thing this office did was not join every motion. It closed one circuit, corrected another, and left the faulted one tripped for the folk who actually owns the repair.

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