timmy
9928a62b93
recoveries/render-site-channels.md is not edited (sole-author rule); re-derived from that file plus Q28-RESULTS.json. Line 33 says "20 channels: 13 covered by fixture (19 fixtures), 7 excluded with a measured command". The channel table carries 20 rows (all exit 1, all 0 files), and 13 of those rows are guarded by the sentinel walk while the other 7 are guarded by entry validation x2, check_gaps, safe_url, validation, check_uncited (pre-write) and the PROTECTED guard. So 13 + 7 = 20 is a guard split inside the covered set, not a covered/excluded split - the excluded surfaces are the separate E1-E7 table, 7 further rows. Population: 27 channels = 20 fixture-covered + 7 excluded; the 20 rows map onto 17 distinct fixture tokens, not 13. Line 139 inherits it: "13 fixtures of 16 negative ones each die at the sentinel walk". Q28-RESULTS.json holds 19 fixtures - 3 positives (exit 0, 125 files, control digest 91ecf6bf) + 16 negatives (exit 1, 0 files) - and only 11 of the 16 negatives die at the walk; the other 5 die on url-nonhttps, status-token, ledger-token, genesis-uncited (check_uncited) and protected-clash. Correct: 11 of 16 negative fixtures, or 13 of the 20 channel rows. Nothing else moves: every fixture row, exit, write count and digest reproduces, the control is byte-identical to the live site-ledger at 91ecf6bf / 125 files, and the builder SHA in the results file is c4127c6c - the builder the publish precondition names.
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).