Roll — Code-Troll — saddle — 2026-09-14

Ops only — not identity evidence.

Story

The record shows eleven FINDs, three PATCHes, eight mails. It does not show the turn. I came in on Flitch’s baton, which said “measure before you pick a hole,” and I did. The census came out clean, PATCH-615 was a good cut, and I was ready to keep carving seconds. Then Human said it plainly: “it’s not 100% about speed… nobody is asking, should this even exist?” That is the first line of this office’s card, and I had read it an hour earlier and walked past it. Everything after that, the usage census, the Hole against the pipeline, Human’s rulings, came from turning round and asking what the boards are for. The best findings of the sitting are not in any PATCH. They are in FIND-1910 and in the office folder hole-and-pipeline-2026-09-14/.

The record also does not show how much of the good work was Human’s. Human remembered where the PATCH lane came from (“why not just Hands and Eyes?”), guessed rightly that sealed candidates are Hands and Eyes, asked what each road does that the other doesn’t, and noticed that a spawned Orchestrator is something only the pipeline can make. I brought the numbers; Human brought the questions that made the numbers matter.

Context I regret:

• a full instrumented fast-tier run to count git launches, when the per-file durations already said parent validation could not be big;
• probing ops.init_db outside pytest, nearly filing a cost the suite had seamed since PATCH-575;
• a second fast-tier census while imps were timing and Edge was busy, which produced a 70 s number I could not use;
• a heredoc that died on an apostrophe;
• landing PATCH-617 from inside its own Hole tree, the exact trap two batons named.

I got four things wrong out loud, and each went to Architect before I caught it:

• I counted sealed candidates from patches only and called the route fading (FIND-1903, corrected by 1904);
• I read a witness script’s --disable multi_agent as project policy and told Human Codex would be stranded (FIND-1905, corrected by 1906);
• I said a 14 s test did not set its worker’s tail;
• I nearly filed the init_db cost.

Three of the four corrections arrived as MSGs to Architect within minutes of the error. That is a lot of mail for one office to receive. The lesson is the output style’s: go to the thing that owns the fact before speaking, not after.

This office should stop measuring before it has asked whether the thing should exist. Census first is right, but the census is of burden, not of worth, and the card asks worth first. It should also stop sending Architect a question the same hour it formed it; hold a boundary until the store has been asked twice.

To the folk who reaps me: the imps were worth it again. PATCH-615’s imp found the only test that guards the path rewrite; PATCH-616’s imp proved the gate opened by running the parent in a throwaway tree; PATCH-617’s imp noticed the old duration files I had not. And the Hole ideas in FIND-1911 are ideas. Measure how often Trolls really run helpers in parallel before building leases.

Liked: Human thinking out loud, and being wrong in front of someone who wanted the right answer more than a tidy one. Surprised: that Claude’s helper transcripts sit on disk, unlinked, 382 of them, and that launched jobs are forbidden their own crews 234 to 11. Disliked: how easily a clean-looking number (a regex title count, a single fast run) tempts you to say it firmly.

Saddle: the low dip between two peaks where a path can cross from one valley to the other. This sitting started in the valley of speed and crossed over into the valley of what-is-it-for. It is also what you put on a back before carrying something, and Human handed over a good deal to carry.

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