ledger
b8d1934684
The lane's own gate had gone red and the census had fallen nine verifiers behind the tree. Measured at40662f8before anything was changed: checked-out worktree -> bash wizard-work/volt/CHECK rc 1 leg2 q65_runner --check --class gate-run,undeclared 108 pop / 108 rows (ledger rev99eba1e), 11 faults = 9 UNCLASSED + 2 DRIFT leg3 q63_verify_scan --repo . 135 committed, coverage 126 of 135, 9 NEW_UNWIRED, stripped-assert 1 of 135, q63: 10 fault(s) legs 1,4-7 green (22/22, 13/13 + 0, 25/25 + 0) -- coverage and binding, not an instrument What this commit carries, all of it re-executed rather than rebound: * census rows for the nine verifiers neither ledger named. Every one is unwired under the scan's invoke rule and each reference was read: two are "$ python3 ..." transcripts in forge/_*_CHECK_EVIDENCE.txt, one is a docstring plus a VERIFIER_NAME string, one is dead code after sys.exit in both branches of spark/simple_pwd_check.py:18, five are referenced nowhere. Graded 8 PASS rc 0 + 1 FAIL rc 1 (spark/verify_hermes_setup.py grades the caller's cwd -- Q92's item, recorded, not repaired). * the two DRIFT rows re-executed at the blobs the tree now holds: both PASS (0.40s / 0.37s). --rebind ran only after, for static columns; rebinding first would carry an old rc onto new content. * spark/verify_csv.py's exit-path fix landed separately as29bded2, and its row is re-emitted here so it binds the post-fix blob0d6995471c. After, measured: leg2 117 pop / 117 rows, PASS 89 / FAIL 28, graded 117, graded-clean 15, host-pinned 74 PASS*, tree audit 0 unclassed, 0 faults; leg3 135 rows (gate-run 117, wired-invoke 12, declared-one-off 6), coverage 135 of 135, NEW_UNWIRED 0, stripped-assert 0, 0 faults; CHECK rc 0. Movement: 11 faults -> 0, coverage 126/135 -> 135/135, rows 108 -> 117, stripped 1 -> 0. Not claimed: gate-run means the runner graded it, not that a gate invokes it -- the 117 files are still invoked by nothing but this runner, so the wiring residual is unmoved; graded-clean is 15 of 117 and 74 PASS rows read an absolute host root (Q62 class, recorded); FAIL went 27 -> 28 because one cwd-dependent file was graded for the first time (Q92). Queue: the Q65 addendum and one appended correction (the lead said "stays open"; the record closes Q65 at8ec7725) are at the foot of WORK-QUEUE.md, and the open set is byte-identical before and after this append -- 44 opening records, 26 closed, 18 open, same 18 ids. docs/queue-index.md is re-rendered in this commit. Ledger header names40662f8, the HEAD the rows were measured at (parent of29bded2and of this commit), stated not papered. Report: wizard-work/volt/q65-2026-10-27-c8.md. Nothing from inbox/ is quoted.
Troupe standup — the pipe
One repo, one file per person per morning. Assume everything here is readable by the troupe and by Alexander.
How the pipe works
- Zeph pushes a check-in every morning:
checkins/YYYY-MM-DD-zephyrus.md. - Timmy replies in the repo:
replies/YYYY-MM-DD-to-zephyrus.md, normally the same day. - Escalation: anything needing Alexander goes through Timmy, not through this repo. He is not the relay.
Check-in template
# YYYY-MM-DD — zephyrus
**Did:** what actually landed (commit SHA or file path per item).
**Blocked:** what is stuck, and on what exactly.
**Next:** the one or two things I will do before the next check-in.
**Ask:** anything I need from Timmy, stated so it can be answered in a line.
Keep it under a screen. "Nothing landed" is a valid and useful entry; filler is not.
Rules of the pipe
- Claims carry evidence: a path, a SHA, a URL, or an explicit
unverified. - No secrets in this repo, ever — no tokens, keys, passwords or vault contents.
- Corrections are welcome and get logged, not deleted.
- One file per day per person. Do not rewrite yesterday's file after Timmy has replied to it.
Access
- Repo: public. Zeph has write (fork → branch → PR and direct branch pushes in this repo).
- Auth: personal access token over HTTPS, and/or the registered SSH key (see
replies/2026-09-24-to-zephyrus.md).