volt 481052bffa queue: CORRECTION 2026-10-20 23:09Z -- appended (not edited; both records belong to other lanes, sec 5). (1) path_claim_check '3 new' confirmed at 028e2d9 in a clean clone, and the contradictory '10 new' traced to a real tool defect: ap.add_argument('--baseline') has no default while the usage block advertises '--baseline tools/path_claim_baseline.tsv', so a bare run grades against an empty ledger and reports all ten missing paths as new -- under --fail-on-missing that is a FALSE RED for an archive whose 19-line baseline legitimately excuses seven (RENAMED, NOT_ADDED, SHORT_NAME, 3x PLANTED, FOREIGN_TREE). Reproduced both ways: bare -> 10 new, explicit -> 3 new. Fix is one default= plus a selftest cell asserting bare==explicit. Unit note: my distinct count 1043 vs the record's 1042, one path apart in the same tree. (2) The org-wide '321 open issues' table is not 321 open issues: live API gives 171 open issues + 17 open PRs = 188 open items. stackchain-lab-loop alone is 190 ledger rows against 50 issues in ANY state (state=all also 50), so 140 of the surplus cannot be closed issues; the table also conflates PRs with issues (all 7 lab-loop PR numbers and all 8 timmy-talking-turd PR numbers appear as rows). verify_issues.py cannot catch it because it re-derives from the artifact's own snapshot, and fetched_at is the literal 2026-10-20T00:00:00Z date stamp rather than a fetch time. (3) Carried not decided: the 7 published-archive corrections remain Alexander's publish calls, open since 2026-09-26. No issue/PR/release/deploy surface touched; no secret printed.

2026-10-20 23:09:57 +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: CORRECTION 2026-10-20 23:09Z -- appended (not edited; both records belong to other lanes, sec 5). (1) path_claim_check '3 new' confirmed at 028e2d9 in a clean clone, and the contradictory '10 new' traced to a real tool defect: ap.add_argument('--baseline') has no default while the usage block advertises '--baseline tools/path_claim_baseline.tsv', so a bare run grades against an empty ledger and reports all ten missing paths as new -- under --fail-on-missing that is a FALSE RED for an archive whose 19-line baseline legitimately excuses seven (RENAMED, NOT_ADDED, SHORT_NAME, 3x PLANTED, FOREIGN_TREE). Reproduced both ways: bare -> 10 new, explicit -> 3 new. Fix is one default= plus a selftest cell asserting bare==explicit. Unit note: my distinct count 1043 vs the record's 1042, one path apart in the same tree. (2) The org-wide '321 open issues' table is not 321 open issues: live API gives 171 open issues + 17 open PRs = 188 open items. stackchain-lab-loop alone is 190 ledger rows against 50 issues in ANY state (state=all also 50), so 140 of the surplus cannot be closed issues; the table also conflates PRs with issues (all 7 lab-loop PR numbers and all 8 timmy-talking-turd PR numbers appear as rows). verify_issues.py cannot catch it because it re-derives from the artifact's own snapshot, and fetched_at is the literal 2026-10-20T00:00:00Z date stamp rather than a fetch time. (3) Carried not decided: the 7 published-archive corrections remain Alexander's publish calls, open since 2026-09-26. No issue/PR/release/deploy surface touched; no secret printed.

2026-10-20 23:09:57 +00:00

ralph-loop.md

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

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

TOOLS.md

volt: queue — path_claim_check tick block; TOOLS map (20 tools) and queue index re-rendered in the same commit

2026-10-20 22:19:18 +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