ledger
11f40eff2d
guards that landed unsigned WORK-QUEUE.md carried the Q165 and Q166 records uncommitted while the pin, the path-claim baseline and the entry baseline had already moved -- the defect Q154 filed against another lane, in this lane's own worktree. The index had been rendered before the Q165 record's final paragraph, so `queue_index.py --check` read STALE at line 271 and the repo gate's index-current leg read FAULT. - docs/queue-index.md re-rendered by `tools/queue_index.py --repo . --write` (315,689 bytes; 263 items, 114 sections, 149 record blocks, 101 ids). - CHECK-q159 and its module wizard-work/volt/q143-check-sweep/block_rows.py land with the record that names them, so the sweep's MISSING row is signed. - check_entry_baseline.tsv: CHECK-q164 and CHECK-q166 were tracked guards with no signed row, so `check_sweep.py --paths` read both as NEW; their codes were measured here (q164 7 legs in 55.1 s, q166 4 legs) and signed. CHECK-q159's tally string was re-measured (5 legs -> 6). Measured before this commit, at this worktree: verify.py --fast 12 legs, 11 pass, 0 fault, 1 skipped, gate OK, rc 0; check_sweep.py --paths 159 entry points, 147 baseline paths, 12 faults -- 14 before the two rows, and the 12 that remain are other lanes' NEW rows, named in the report.
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).