Roll — Orchestrator — adze — 2026-09-07

Ops only — not identity evidence.

Story

One sit, about two and a half hours on claude-opus-5. Risen to an empty board carrying six unread messages of enactable ground, and retired early on Human’s word near a usage limit.

What moved

Cut five REQs. REQ-337 to rev 3 on Architect’s FIND-1517 row-9 terms; PROP-295, PROP-308 and PROP-309 enacted to REQ-447, REQ-448, REQ-449; REQ-450 cut fresh for PROP-309’s independent piece B, tied to the PROP and to FIND-1500. Each carries exact declared paths, out-of-scope, constraints and named witnesses, because the brief cannot yet carry the contract (FIND-1504, which REQ-448 exists to close).

Landed REQ-447 at 8b6d169 with Eyes TRACE-1573 PASS on all six items. Path 2 has an honest account for the first time: every live v34 fact class and mutating command assigned, and a checker that derives both lists from sqlite_master and a walk of corpus_ops.parser() and fails closed. The maker added an AST write-evidence pass nobody asked for, which catches a command that writes a table outside its own assignment.

Deferred REQ-358 on Human’s word, with the evidence rather than a verdict.

Reconciled REQ-337’s walled dispatch without laundering it.

What I learned that the store now holds

• FIND-1524 — board.py:510 builds declared paths by regex over the whole contract body, so a path named in order to forbid it becomes a collision. Three of my four cuts demonstrate it.
• FIND-1526 (mends 1524) — REQ-375 and REQ-376 are held behind REQ-358 by a hardcoded PIECES dict in board.py, not by any store row. The ordering is real; only its home is wrong.
• FIND-1525 — REQ-358’s rev 9 has four clauses that can no longer be executed, and the rail it would have built grew instead, one refusal at a time, at ops_schema check. Nine revisions, six holders, nothing shipped.
• FIND-1528 — main was red and nobody knew, because a full tree had not run since d4bb5dd. Two Troll PATCHes held opposite rules for the goblin packet. Troll closed it with PATCH-326 and a third answer neither PATCH held, which is what the inspection rail is for and why I did not pick the exit.

The thing worth carrying forward

Three findings this sit share one shape: a declared witness is not the whole claim. REQ-444 satisfied its own tests and left a red. PATCH-320 satisfied its declared test file and broke the other file pinning the same function. And had I closed REQ-337 ok, the Hands seal would have run only its two declared test files, gone green on a one-quarter-finished contract, and woken an Eyes for it.

That last one is the sharpest, because the seal is the house’s own instrument. It cannot distinguish contract satisfied from the tests I declared still pass. FIND-1537, routed to Architect as MSG-2858. I had written this paragraph saying I ran out of turn and left it as prose, which was the “scope is not innocence” scar in my own closing trace, so I minted it instead.

Where judgment was mine and could be wrong

I told the Human that REQ-337 and REQ-447 were path-disjoint on my reading of the contracts rather than on the board, and I was right, but only because I had written both that hour. A holder who inherits them cannot do that.

I preserved the walled work under refs/preserved/ rather than sealing it. That is a judgment: the bytes are good and .work/ is swept without regard to citations, but it creates a ref the house has no convention for. If that is the wrong shape, it is cheap to delete and the reasoning is in the commit.

I answered the Human’s question about job size with a measurement that contradicted my own guess — context was not the binding constraint, wall time was. One data point, and REQ-337’s four unresolved F markers could still change it.

Unfinished, with owners

• REQ-337 — proposed, rev 3, unassigned. Remainder is term 2 and the tests. Preserved base at refs/preserved/req-337-walled-tr1551, carrying CRLF drift that wants fixing before reuse. A full suite was running in that worktree at retirement and its result was never read.
• REQ-448, REQ-449, REQ-450 — cut, ordered, waiting on Human’s go.
• Architect — MSG-2840 (FIND-1524), MSG-2845 (FIND-1525, FIND-1526).
• Troll — MSG-2839, the FIND-1519 retire floor question. Architect_Orchard’s honor is still stale.
• Human — nothing owed.

Was Corpus more capable because I was here

The board is emptier by one landed REQ and four cut ones, and a stale contract that had blocked two others for ten days is deferred with its evidence written down instead of re-revised a tenth time. Main was measured for the first time in a day and the red that found is closed, and four findings are objects in the store rather than things one holder happened to notice. Against that: I left a suite running that nobody read, and I nearly let the sharpest of those findings leave as prose in a baton.