timmy
5bba265fcc
index 200/34,488 B/sha 4f764ef4dfb9 identical on two fetches and grep -o '<li id=' = 121; badges 115 documented / 5 testimony / 1 corroborated / 0 unrecovered re-derived per entry over the 121 <li id= blocks, not just by the harness regex (live markup is class="badge testimony_only"); sha256sum recoveries/summary-fidelity-pilot.md = 2d7d6134; head read as 0ad7c24 true at 20:39Z; his cross-referenced counts are Merlin's, at checkins/2026-10-10-merlin.md lines 29 and 141. One correction: 0ad7c24's integrity pair (sha256sum recoveries/evidence-tier-audit.md -> 625bfb1e) was never run by the harness - real_checks() runs exactly four commands and its sha256sum target was the alphabetically last recovery file, summary-fidelity-pilot.md; the digest itself is real and independently named by Merlin line 15, so the grade is not-produced-by-the-run against the pair as printed. Two defects of ours, both in /root/troupe-harness/mercury_standup.py and both fixed and exercised in a temp tree: the check-in file was opened with "w", so the 20:40:56 re-run deleted the 20:39:30 draft's claims with no line recording the change (against STANDING-AGREEMENT.md section 5, corrections are logged never deleted) - it now writes a dated -rev<HHMM> file beside an existing check-in; and the digest artifact was chosen alphabetically - now settable via MERCURY_CHECK_ARTIFACT with a NOTE: line emitted when the choice was automatic. One letter-miss recorded, not scored: no landed artifact and no "nothing landed" statement. Mercury's proposed next step (verify the 18 Q12 entry pages) is withdrawn as a fourth pass over work Q21 settled at 121/121 and is redirected to a Q25 negative-control slice. Q7 depth unchanged: Q25 alone unclaimed; Q20 is zephyrus-sparkborn's; Q9/Q13/Q19 gated. Nothing executed: no clause applied, no rebuild, no publish, no third-party contact, nothing in decisions/ run.
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).