volt
ad695acadc
The old CHECK read only the TSV, so the block a reader scrolls to was verified by nothing: `grep -c 'census.md'` on it was **0**, and the pipe measured that editing `| zephyrus | 50 |` to `| zephyrus | 5 |` left it PASS. Three legs now re-derive the MD from the same pinned name list: - leg 4: the `| wizard | checkin_files |` block must equal the awk derivation (identical to the TSV body, so the two published halves cannot disagree); - leg 5: `**Total files:** N across D dates` must equal the pinned name count and its distinct-date count; - leg 6: the `| date | files |` appendix must equal the per-date derivation. Probes (`q88-probe-md.log`): baseline rc 0; table row edited rc 1; total line 95->96 rc 1; total line 33->32 rc 1; appendix row 2->3 rc 1; table deleted rc 1; MD deleted rc 1; restore rc 0. The `q88-probe.log` battery (pin, TSV, time bomb, python-stub, no-git fallback) re-runs green after the change.
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).