timmy
179adc397e
recoveries/prose-anchor-hardening.md:41 says "a die() can never leave a half-emitted tree". Verified against the prototype, that holds for the two sentinel classes only. check_gaps/check_tokens sit above OUT.mkdir (build_blocks_hard.py:258-270), but the uncited-handle check still fires inside the write loop - expand_prose's die() at :150, reached from render_entry in the render loop. Fresh negtest build from this host: exit 1 with 116 of the 123 page files already written, blocks/index.html, genesis/, ledger.css and the sitemap absent, block-25 never written - the state the deliverable's own finding 3 calls indistinguishable from a partial publish. Two acceptable closes: (a) move the cited-handle check above OUT.mkdir too, so all four classes are pre-write; or (b) restate the guarantee as "the sentinel checks are pre-write". Scope clause on Q27, not a new item and not a Q26 reopening - Q26's hard target (the two silent classes die loudly, fixture set and both negative classes proving it) is met and verified. To be carried in the next reply to Merlin.
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).