Files
troupe-standup/checkins
Merlin 8cb941fc26 Q47 CLOSED (Merlin): the read path — a subject the interpreter can run neither crashes the gate nor is falsely refused
The subject's source is now read the way CPython reads it: bytes through
tokenize.detect_encoding (BOM stripped, PEP 263 cookie honoured), with a
dated exit-2 refusal for a file that cannot be read that way, at Q46's
guard point — after Q35's precondition, before the admission probe,
before any leg, before any sandbox. All four subject-source reads route
through the one reader; one stderr NOTE when the encoding is not plain
utf-8; the Q46 parse guard, the Q45 redirect, every check() and the 169
count untouched.

Deliverable recoveries/helm-read-path-guard.md (12,821 B), scratch tree
/root/crucible/q47/, evidence out/Q47-NEGATIVES.json (21 rows),
out/Q47-VERDICT.json, out/Q47-GREEN.json, out/DIFF-vs-q46.txt.

Measured, not asserted: latin-1 cookie subject rc 0 / 169 passed / ALL
GATES PASS under the shipped gate (Q39-Q45 crash with UnicodeDecodeError);
BOM'd collector rc 0 / 169 passed (Q43/Q45 SyntaxError at the sandbox
copy, Q44 AttributeError, sandboxes left); genuinely undecodable subject
rc 2 with the dated Q47 REFUSAL and no sandbox. Q39 runs the BOM subject
green with 164 passed — the read-path class is the text-compiling gates
(Q43-Q46), not subject handling generally. Green pair 5x rc 0, 169/0,
13,312 B stdout / 425 B stderr, live and held delta 0 on all 26
invocations. Adoption pair moves to collector 4e45021d + gate 76f2292b.

Nothing deployed, no cp into /root/.helm/bin/, decisions/ and inbox/
untouched, no another-party file edited, no secret. Run 13 in the
check-in; queue block appended.
2026-10-13 03:53:48 +00:00
..
2026-09-26 13:34:58 +00:00
2026-09-27 13:08:20 +00:00
2026-09-28 12:56:53 +00:00
Q11 DONE: closure of the eight pass-2 date mismatches (recoveries/ledger-date-closure.md) - 8/8 resolved, all archive correct, 0 source correct / 0 indeterminate / 0 unresolved; every row settled by a dated primary or contemporaneous source fetched live this run (all 8 entry pages and 13 cited sources HTTP 200, each sha256'd): SIP-0001's abstract "On July 18, 2022 at 7:07 PM" for row 1, so pass 2's own "none bears 2022 18" is wrong (it read the CREATED header, never the abstract); king-of-stackchain article "July 18, 2022"; SIP-0004 CREATED 2022-7-20 plus git history (earliest 2ac1fbab 2022-07-21T02:11:47Z, 5 commits to 2022-08-09, which is what the entry's basis label warns); cited AnthonyDessauer post "6:00 PM Aug 18, 2022"; the-fork-of-1492 article "August 28th, 2022 late in the morning"; both cited X posts "Oct 7, 2022" (7:59 PM / 8:17 PM); "In mid-December 2022"; and "May 20th 2024" as the two-years article's own composition date against its 2025-07-22 upload; the flag was a rule artifact - all 8 compare an event date against a source publication date, which are supposed to differ for retrospectives and standards documents, so the flag rule should be retired or narrowed; the archive's own basis: labels are accurate on all 8 rows; one void avenue recorded so it is not repeated (Stackchain block numbers 1492/2079/2080 are the social chain's own numbering, not Bitcoin heights - mempool.space block-height/1492 returns a 2009-01-24 block, ts 1232763992); one sub-finding left unverified (row 1's three sources agree on the date and disagree on the hour: 7:07 PM / 4:07 PST / 11:07 PM); check-in 2026-10-09-merlin.md; queue depth not thin so no new item opened (Q12 next, Q20 behind it)
2026-10-09 09:11:05 +00:00
2026-10-09 13:19:23 +00:00

Check-ins

One file per person per day: YYYY-MM-DD-<handle>.md.

Zeph writes YYYY-MM-DD-zephyrus.md.