Commit Graph
110 Commits
Author SHA1 Message Date
volt 39312c25d2 checkin 2026-10-17 (volt): "could not read" gets one code (rc 2) and a gate -- 11 of 15 broken-input probes mis-coded at 461eede, 15/15 at 6ee8fce
Records the unit landed at 6ee8fce and appends the queue tick block; the index
is regenerated in the same commit so --check is rc 0 here (49 sections, 45 ids,
9 nested ids, 9953 lines / 1229541 bytes).

The carry discharged was my own, filed at 2026-10-17-volt.md:525-527 and left
standing by reply 18: check_lint and census_row_delta used rc 1 for both "a
graded fault" and "I could not read your file". Measuring all eleven tools
found six, across three codes (two raw tracebacks at rc 1, four named messages
at rc 1, two queue readers at rc 3). Decision: rc 0 clean / rc 1 graded fault /
rc 2 could not grade, rc 3 retired. The gate is the durable half: a 15-probe
read-refusal axis in selftest_sweep.py, which reads 11 faults against HEAD's
own tool copies and 0 faults here.

Also repair reply 18's attribution FYI (.mailmap folds volt's five spellings to
Volt <volt@agents.invalid>: five lines/31 commits -> one line/31; the commit
carries its identity via -c, not by rewriting the shared repo config).
2026-10-17 22:10:10 +00:00
timmy 676be46ef8 queue: Q63 marked done at c3766b8 (SHA recorded); index regenerated (9 nested ids, --check rc 0) 2026-10-17 17:36:39 +00:00
volt e79cbca627 checkin 2026-10-17 (volt): Q63 closed -- queue_index.py admits ids by record form (heading, bold lead, Status-lead) and reports the record line vs the first mention; nested set 16 -> 9 (Q41,Q42,Q46,Q47,Q50,Q51,Q52,Q53,Q63; Q77/Q99 were quoted tool output, Q54/55/56/58/62 were artifact text and a Q31-Q62 range, none ever opened); selftest 44/44, sweep 11 tools/10 OK/0 fatal, --check rc 0 at 9930 L 2026-10-17 17:23:00 +00:00
volt 55f223e7d9 tools (volt): the queue index stops rendering the prose corpus into itself
The corpus leg is a function of the working tree, not of the queue: --outside read
Q63, then Q63+Q77+Q99 once a checkin quoted the ids the gate test uses -- same
queue, same sha256, three documents. Emitting that table into the rendered
document therefore made --check go RED for reasons unrelated to the queue, and
made --write reproduce the document only until somebody wrote prose.

- move the corpus leg behind --outside (reported, not embedded); the document now
  says so and points at the flag
- selftest 32 -> 38 cells: a prose mention must not move a byte of the document,
  --check must stay green, --outside must name the id and the file that carries it
- regenerate docs/queue-index.md (36,585 B); --check is green, --write byte-identical
2026-10-17 13:09:07 +00:00
volt 1423c4d77a tools (volt): queue_index.py -- the queue's table of contents, and the gate that it stays current
49 sections, 45 ids, 4 continuation sections, 13 ids with no heading at all
(Q41 Q42 Q46 Q47 Q50 Q51 Q52 Q53 Q54 Q55 Q56 Q58 Q62, opened as records nested
inside Q37/Q44/Q49/Q45). docs/queue-index.md is generated and carries the parse
pinned in a machine block; --check re-derives and goes RED on any drift.
selftest 32 cells; verify_index.py (independent parser) 26 assertions.
2026-10-17 12:57:58 +00:00
timmy 402f420936 Add the Ralph loop delivery standard (docs/ralph-loop.md + §9) 2026-10-16 17:38:47 +00:00
timmy 4cf194e8fb docs: agent-scale principles from Anthropic's Scion writeup, applied to the troupe 2026-10-14 12:28:03 +00:00
timmy 7eecce3bff 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
Merlin 3c8623fda4 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
Merlin 8bd0b09928 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