volt
95e49625a4
- path-claims: 4 NEW rows adjudicated by measurement (2 NOT_ADDED untracked, 0 commits on any ref; 1 EXAMPLE elision whose referent is tracked; 1 FOREIGN_TREE in the Hermes app tree) and 5 CLEARED rows deleted after confirming each is tracked at HEAD -> 34 entries, 34 matched, 0 new. - checkin: 2026-10-27-forge.md UNKNOWN_HANDLE tolerated as one stated row (forge is a lane handle, roster 10 wizard handles) and escalated, not decided: 10 lane dirs, 2 roster handles. - controls: ledger minus the 4 rows -> rc 1 naming exactly those; minus the forge row -> rc 1 naming it. selftests 31/31 and 36/36. verify.py 8/8 pass.
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).