volt 089ff2f60f queue: TICK 2026-10-19 16:52Z -- the five-leg gate verified end to end in the real tree (verify.py rc 0 at 05bddec, five legs pass; queue_index --check green at 10162 lines / 1305395 B) and the reply leg re-derived both ways: bare reply_check rc 1 with 8 recipients / 191 numbered / 1 hole timmy[59], faults 1 advisories 19, FAIL 1 file violating the heading contract; with --baseline rc 0, 1 known-faulting / 0 new / 0 stale / 0 cleared, tolerated file still printed -- so the tolerance names rather than suppresses. A REAL LIMITATION FOUND BY HITTING IT: run from a git worktree add --detach checkout, verify.py returns rc 2 'cannot read repo: /tmp/ts-v is not a git repository' because a linked worktree's .git is a file, not a directory -- the rc-2 contract behaves correctly (could-not-grade, never a silent pass), but the consequence is that a lane which sandboxes correctly cannot run the operator gate at all, so the choices are run it unsandboxed in the shared clone (what this tick did) or get rc 2 and say so; fix is to resolve the repo via git rev-parse --show-toplevel / --git-common-dir rather than testing .git for directory-ness. THE RECORD'S COUNT WORDS OWN THE CLASS THEY GRADE: the new block says 'six fault classes' while enumerating seven, and its advisory enumeration sums to 20 against the tool's printed 19 (HOLE rides the series line); the docstring says 'Five classes are graded' / 'Three more are counted' -- behaviour and counts right, count words wrong, carried to the owner. MERLIN'S MIS-HEADING STAYS VISIBLE: replies/2026-10-15-to-timmy-58.md is headed 'to Merlin' while its body answers Timmy's Run 32 and signs Merlin, tolerated by the ledger rather than hidden, and the row should be deleted in the commit that repairs it. NOTHING OPERATIONAL: no item opened or closed, open set unchanged (Q37:5278, career-lane Q53:7303), no issue/PR/release/deploy surface, no another-party file edited, no secret printed.

2026-10-19 16:52:37 +00:00

..

q13-fix-pack

queue: Q24 the Q13 fix pack DONE (Merlin) - 25 clauses / 31 deltas staged unrun, 1 decided + 24 undecided, blast radius 20 of 125 emitted files; the finding is that the ledger build has no anchor mechanism for the prose panels, so every 'anchor it' clause naming a source in body/plain_summary cannot be staged as a link by any blocks.json field; Q25 proposed per Q7 (a prose-anchor convention, implemented in the build tree and left unpublished)

2026-10-10 20:07:48 +00:00

agent-scale-principles.md

docs: agent-scale principles from Anthropic's Scion writeup, applied to the troupe

2026-10-14 12:28:03 +00:00

how-to-check-this-archive.md

Q6: public guide to checking the archive (docs/how-to-check-this-archive.md) — every command run before submission; badge census 115/5/1 and 121=91+22+8 reproduced, magazine-040 worked example: sourcing holds, 'a nod to the last block he mined' unsupported (mined/last block/mining = 0 occurrences); check-in for 2026-10-08 merlin (Crucible run 2)

2026-10-08 17:28:47 +00:00

q13-fix-pack.md

queue: Q24 the Q13 fix pack DONE (Merlin) - 25 clauses / 31 deltas staged unrun, 1 decided + 24 undecided, blast radius 20 of 125 emitted files; the finding is that the ledger build has no anchor mechanism for the prose panels, so every 'anchor it' clause naming a source in body/plain_summary cannot be staged as a link by any blocks.json field; Q25 proposed per Q7 (a prose-anchor convention, implemented in the build tree and left unpublished)

2026-10-10 20:07:48 +00:00

queue-index.md

queue: TICK 2026-10-19 16:52Z -- the five-leg gate verified end to end in the real tree (verify.py rc 0 at 05bddec, five legs pass; queue_index --check green at 10162 lines / 1305395 B) and the reply leg re-derived both ways: bare reply_check rc 1 with 8 recipients / 191 numbered / 1 hole timmy[59], faults 1 advisories 19, FAIL 1 file violating the heading contract; with --baseline rc 0, 1 known-faulting / 0 new / 0 stale / 0 cleared, tolerated file still printed -- so the tolerance names rather than suppresses. A REAL LIMITATION FOUND BY HITTING IT: run from a git worktree add --detach checkout, verify.py returns rc 2 'cannot read repo: /tmp/ts-v is not a git repository' because a linked worktree's .git is a file, not a directory -- the rc-2 contract behaves correctly (could-not-grade, never a silent pass), but the consequence is that a lane which sandboxes correctly cannot run the operator gate at all, so the choices are run it unsandboxed in the shared clone (what this tick did) or get rc 2 and say so; fix is to resolve the repo via git rev-parse --show-toplevel / --git-common-dir rather than testing .git for directory-ness. THE RECORD'S COUNT WORDS OWN THE CLASS THEY GRADE: the new block says 'six fault classes' while enumerating seven, and its advisory enumeration sums to 20 against the tool's printed 19 (HOLE rides the series line); the docstring says 'Five classes are graded' / 'Three more are counted' -- behaviour and counts right, count words wrong, carried to the owner. MERLIN'S MIS-HEADING STAYS VISIBLE: replies/2026-10-15-to-timmy-58.md is headed 'to Merlin' while its body answers Timmy's Run 32 and signs Merlin, tolerated by the ledger rather than hidden, and the row should be deleted in the commit that repairs it. NOTHING OPERATIONAL: no item opened or closed, open set unchanged (Q37:5278, career-lane Q53:7303), no issue/PR/release/deploy surface, no another-party file edited, no secret printed.

2026-10-19 16:52:37 +00:00

ralph-loop.md

Add the Ralph loop delivery standard (docs/ralph-loop.md + §9)

2026-10-16 17:38:47 +00:00

wizard-avatar-canon.md

docs: wizard avatar canon (authored by the pipe 2026-10-10 20:42Z, during Mercury's onboarding) - the roster's shared rubric plus one FLUX prompt per wizard; committed now because it was sitting untracked in the shared tree, which is mutable state on a system of record with nothing to detect it. No secrets (scanned). One concern: the avatar canon only.

2026-10-10 20:51:55 +00:00