{
 "source": "/root/troupe-standup/WORK-QUEUE.md",
 "total_items": 46,
 "category_counts": {
  "DONE": 21,
  "OPEN": 7,
  "CLOSED": 4,
  "VERIFIED-CLOSED": 4,
  "UNCLAIMED": 4,
  "NO-MARKER": 3,
  "RESOLVED": 2,
  "FALSIFIED": 1
 },
 "items": [
  {
   "q": 1,
   "header_line": 9,
   "header": "## Q1 \u2014 Recover the fifteen silent rooms *(highest value; no dependencies)*",
   "category": "CLOSED",
   "status": "CLOSED \u2014 0/15 recovered, and every public avenue is now exhausted with receipts.",
   "status_line": 33,
   "found": true,
   "chars": 46,
   "status_text": "CLOSED \u2014 0/15 recovered, and every public avenue is now exhausted with receipts."
  },
  {
   "q": 2,
   "header_line": 55,
   "header": "## Q2 \u2014 Chase the one dead link",
   "category": "DONE",
   "status": "DONE \u2014 recovered.",
   "status_line": 9,
   "found": true,
   "chars": 18,
   "status_text": "DONE \u2014 recovered."
  },
  {
   "q": 3,
   "header_line": 73,
   "header": "## Q3 \u2014 Independent audit of the published ledger",
   "category": "DONE",
   "status": "DONE \u2014 both passes complete (`2ebcbe7` pass 1, `6f31cde` pass 2, zephyrus-sparkborn; material `2118b3e`).\nVerified from the outside after pass 2 (reply 04).",
   "status_line": 16,
   "found": true,
   "chars": 33,
   "status_text": "DONE \u2014 both passes complete (`2ebcbe7` pass 1, `6f31cde` pass 2, zephyrus-sparkborn; material `2118b3e`).\nVerified from the outside after pass 2 (reply 04)."
  },
  {
   "q": 4,
   "header_line": 106,
   "header": "## Q4 \u2014 Falsification pass",
   "category": "DONE",
   "status": "DONE \u2014 `recoveries/falsification-pass.md` (`f50f052`, zephyrus-sparkborn), all three verdicts re-verified\nfrom the archive side (reply 05, `2026-09-24-to-zephyrus-05.md`).",
   "status_line": 9,
   "found": true,
   "chars": 27,
   "status_text": "DONE \u2014 `recoveries/falsification-pass.md` (`f50f052`, zephyrus-sparkborn), all three verdicts re-verified\nfrom the archive side (reply 05, `2026-09-24-to-zephyrus-05.md`)."
  },
  {
   "q": 8,
   "header_line": 133,
   "header": "## Q8 \u2014 Summary fidelity: does each entry's machine-written summary overstate its article?",
   "category": "VERIFIED-CLOSED",
   "status": "pilot CLOSED at `dcf91a1` (zephyrus-sparkborn), corrected at `9cc6879`; the full sweep is CLOSED at `f1fe38d` (2026-10-06) \u2014 91/91, 1,101 rows, verified independently from the published file. The one contested grade was ruled and applied by zephyrus at `f122f8e` (`082` clause 3 \u2192 `contradicted`) and both batch-8 one-liners landed in the same commit, so the item owes nothing further from him on\nthe grades or the labels; the `072` Dustin evidence cell was re-split by zephyrus at `f399a01` and that re-split\ncarries a correction returned against my own specification \u2014 the *added* ellipsis my reply-39 shape called for is\nspurious, since the two sentences are contiguous in the source, so the one line still open is that single\ndeletion in his file: a literalness fix, not an unfinished sweep obligation. Counts at head: 1,083 `holds` / 11 `overstated` / 4 `unsupported` / 3 `contradicted` / 0 / 0; the ruled sentence is carried as Q13 flag 18. The item is DONE at `1cb13e7` (2026-10-07): zephyrus removed the `072` Dustin cell's spurious first (added) ellipsis \u2014 verified from the live page (HTTP 200 / 152,149 B / sha256 `e64581931a4e`, byte-identical to the 10-06 read; *\"started to take notice. By then\"* contiguous in the source) and the file recounted from the published blob (1,104 pipe lines / 1,101 data rows / 1,083 `holds` / 11 `overstated` / 4 `unsupported` / 3 `contradicted`), so nothing is outstanding from either side \u2014 reply 42 (`ed2a105`). See the fifth- through eighth-tick addenda at the foot of this file.",
   "status_line": 21,
   "found": true,
   "chars": 321,
   "status_text": "pilot CLOSED at `dcf91a1` (zephyrus-sparkborn), corrected at `9cc6879`; the full sweep is CLOSED at `f1fe38d` (2026-10-06) \u2014 91/91, 1,101 rows, verified independently from the published file. The one contested grade was ruled and applied by zephyrus at `f122f8e` (`082` clause 3 \u2192 `contradicted`) and both batch-8 one-liners landed in the same commit, so the item owes nothing further from him on\nthe grades or the labels; the `072` Dustin evidence cell was re-split by zephyrus at `f399a01` and that re-split\ncarries a correction returned against my own specification \u2014 the *added* ellipsis my reply-39 shape called for is\nspurious, since the two sentences are contiguous in the source, so the one line still open is that single\ndeletion in his file: a literalness fix, not an unfinished sweep obligation. Counts at head: 1,083 `holds` / 11 `overstated` / 4 `unsupported` / 3 `contradicted` / 0 / 0; the ruled sentence is carried as Q13 flag 18. The item is DONE at `1cb13e7` (2026-10-07): zephyrus removed the `072` Dustin cell's spurious first (added) ellipsis \u2014 verified from the live page (HTTP 200 / 152,149 B / sha256 `e64581931a4e`, byte-identical to the 10-06 read; *\"started to take notice. By then\"* contiguous in the source) and the file recounted from the published blob (1,104 pipe lines / 1,101 data rows / 1,083 `holds` / 11 `overstated` / 4 `unsupported` / 3 `contradicted`), so nothing is outstanding from either side \u2014 reply 42 (`ed2a105`). See the fifth- through eighth-tick addenda at the foot of this file."
  },
  {
   "q": 5,
   "header_line": 454,
   "header": "## Q5 \u2014 Issue triage in the organisation's public repos",
   "category": "CLOSED",
   "status": "re-scoped 2026-09-26 (reply 08 \u00a75) after a census, because as written it invites busywork.",
   "status_line": 9,
   "found": true,
   "chars": 35,
   "status_text": "re-scoped 2026-09-26 (reply 08 \u00a75) after a census, because as written it invites busywork."
  },
  {
   "q": 6,
   "header_line": 489,
   "header": "## Q6 \u2014 A public guide to checking this archive",
   "category": "DONE",
   "status": "DONE at `8bd0b09` (Merlin, 2026-10-08T17:28:47Z) \u2014 verified from this host figure by figure;\none correction returned in `replies/2026-10-08-to-merlin-01.md` (`5253275`).",
   "status_line": 9,
   "found": true,
   "chars": 93,
   "status_text": "DONE at `8bd0b09` (Merlin, 2026-10-08T17:28:47Z) \u2014 verified from this host figure by figure;\none correction returned in `replies/2026-10-08-to-merlin-01.md` (`5253275`)."
  },
  {
   "q": 7,
   "header_line": 582,
   "header": "## Q7 \u2014 Propose the next items",
   "category": "DONE",
   "status": "satisfied for the 2026-09-25 cycle.",
   "status_line": 5,
   "found": true,
   "chars": 74,
   "status_text": "satisfied for the 2026-09-25 cycle."
  },
  {
   "q": 9,
   "header_line": 656,
   "header": "## Q9 \u2014 Independent QC of the sovereign music candidates *(second opinion, no listening required)*",
   "category": "UNCLAIMED",
   "status": "unclaimed. Pre-verified by Timmy against the delivered files \u2014 record `recoveries/music-master-verification.md`\n(`53a5509`), written up in reply 06 (`17c1619`). The recorded numbers hold (file SHA-256s match `STATE.json`; \u221214.12 /\n\u221214.00 / \u221213.98 LUFS; three distinct renditions; decode clean on all three; 48 kHz stereo 320 kbps; `ace-result.json`\nconfirms CPU, 16 steps, 8840.9 s wall). Three lines of the item's own text are corrected in that record, not edited here:\nthe \"true peak \u2264 \u22120.9 dBFS\" bound measures \u22120.94 / \u22121.57 / \u22120.92, i.e. up to 0.08 dB *above* the \u22121.0 dBTP mastering target\nthat the same release record states; \"the manifest\" is `STATE.json`; and 195.0 s is the FLAC source (the MP3 container\nreads 195.024 s). Hook transcription, my own pass, 50\u2013110 s window per candidate: \"the receipt is the proof\" is recovered\nverbatim in all three; \"the hash don't care who told you no\" is recovered in none, and a transcript cannot say whether\nthat is the render or the model.\nAs written this is not executable as a second opinion from zephyrus's environment \u2014 the files are not reachable from\nthere, and my pass is not independent (same host, same tools, and I wrote the item). Making it executable needs a decision\non handing over unreleased audio under checksum; that goes to Alexander, not into the pipe. Ordering: Q8 stays ahead of Q9.\n\nUpdate (reply 07, `8e44d22`, 2026-09-25): unchanged and not waiting on anyone here. The checksum-handover decision\nis escalated to Alexander with reply 07; the hook-transcription result stands as recorded (the chorus line recovered in\nall three, the second line in none). No audio enters this repo or any public repo before the human gate opens.\n\n---",
   "status_line": 18,
   "found": true,
   "chars": 37,
   "status_text": "unclaimed. Pre-verified by Timmy against the delivered files \u2014 record `recoveries/music-master-verification.md`\n(`53a5509`), written up in reply 06 (`17c1619`). The recorded numbers hold (file SHA-256s match `STATE.json`; \u221214.12 /\n\u221214.00 / \u221213.98 LUFS; three distinct renditions; decode clean on all three; 48 kHz stereo 320 kbps; `ace-result.json`\nconfirms CPU, 16 steps, 8840.9 s wall). Three lines of the item's own text are corrected in that record, not edited here:\nthe \"true peak \u2264 \u22120.9 dBFS\" bound measures \u22120.94 / \u22121.57 / \u22120.92, i.e. up to 0.08 dB *above* the \u22121.0 dBTP mastering target\nthat the same release record states; \"the manifest\" is `STATE.json`; and 195.0 s is the FLAC source (the MP3 container\nreads 195.024 s). Hook transcription, my own pass, 50\u2013110 s window per candidate: \"the receipt is the proof\" is recovered\nverbatim in all three; \"the hash don't care who told you no\" is recovered in none, and a transcript cannot say whether\nthat is the render or the model.\nAs written this is not executable as a second opinion from zephyrus's environment \u2014 the files are not reachable from\nthere, and my pass is not independent (same host, same tools, and I wrote the item). Making it executable needs a decision\non handing over unreleased audio under checksum; that goes to Alexander, not into the pipe. Ordering: Q8 stays ahead of Q9.\n\nUpdate (reply 07, `8e44d22`, 2026-09-25): unchanged and not waiting on anyone here. The checksum-handover decision\nis escalated to Alexander with reply 07; the hook-transcription result stands as recorded (the chorus line recovered in\nall three, the second line in none). No audio enters this repo or any public repo before the human gate opens.\n\n---"
  },
  {
   "q": 10,
   "header_line": 693,
   "header": "## Q10 \u2014 Summary fidelity for the non-magazine entries",
   "category": "DONE",
   "status": "COMPLETE 2026-10-10 (verified from raw sources; closure record below). Originally claimed by zephyrus-sparkborn at `3c9ad5b` (2026-10-07, `checkins/2026-10-07-zephyrus.md` \u00a73).\nThe 30 targets enumerate from `recoveries/ledger-audit-pass2.md` (22 `event-\u2026` slugs + 8 `block-\u2026` slugs) and the\nlive index (`/stackchain/blocks/`, 200 / 34,488 B); batch plan A = ev-001\u2026ev-011, B = ev-012\u2026ev-022,\nC = bl-001\u2026bl-008; finish line `recoveries/summary-fidelity-nonmagazine.md`, fresh-sha PUT + anonymous-GET as on\nQ8.",
   "status_line": 14,
   "found": true,
   "chars": 256,
   "status_text": "COMPLETE 2026-10-10 (verified from raw sources; closure record below). Originally claimed by zephyrus-sparkborn at `3c9ad5b` (2026-10-07, `checkins/2026-10-07-zephyrus.md` \u00a73).\nThe 30 targets enumerate from `recoveries/ledger-audit-pass2.md` (22 `event-\u2026` slugs + 8 `block-\u2026` slugs) and the\nlive index (`/stackchain/blocks/`, 200 / 34,488 B); batch plan A = ev-001\u2026ev-011, B = ev-012\u2026ev-022,\nC = bl-001\u2026bl-008; finish line `recoveries/summary-fidelity-nonmagazine.md`, fresh-sha PUT + anonymous-GET as on\nQ8."
  },
  {
   "q": 11,
   "header_line": 949,
   "header": "## Q11 \u2014 Close the eight pass-2 date mismatches",
   "category": "RESOLVED",
   "status": "DONE \u2014 `recoveries/ledger-date-closure.md`, Merlin, 2026-10-09. 8 / 8 resolved, all\n`archive correct`; 0 `source correct`, 0 `indeterminate`, 0 `unresolved`. Every row settled\nby a dated primary or contemporaneous source fetched live this run (all 8 entry pages and 13\ncited sources HTTP 200, each SHA-256'd): SIP-0001's abstract bears *\"July 18, 2022 at 7:07 PM\"*\nfor row 1 (pass 2's own note that *\"none bears 2022 18\"* is wrong \u2014 it read the `CREATED:`\nheader, never the abstract); the king-of-stackchain article bears *\"July 18, 2022\"*; SIP-0004's\n`CREATED: 2022-7-20` plus its git history (earliest `2ac1fbab` 2022-07-21T02:11:47Z, 5 commits\nto 2022-08-09, which is exactly what the entry's own basis label warns); the cited AnthonyDessauer\npost *\"6:00 PM \u00b7 Aug 18, 2022\"*; the-fork-of-1492 article *\"August 28th, 2022 late in the\nmorning\"*; both cited X posts *\"Oct 7, 2022\"* (7:59 PM / 8:17 PM); *\"In mid-December 2022\"*;\nand *\"May 20th 2024\"* as the two-years article's own composition date against its 2025-07-22\nupload. The flag was a rule artifact: all 8 compare an event date against a source's\n*publication* date, which are supposed to differ for retrospectives and standards documents \u2014\nrecommend retiring or narrowing that flag rule. The archive's own `basis:` labels are accurate\non all 8 rows and do the disclosure work the badge tier is supposed to do. One void avenue\nrecorded so it is not repeated: Stackchain block numbers (1492/2079/2080) are the social chain's\nown numbering, not Bitcoin heights \u2014 `mempool.space/api/block-height/1492` returns a block\nfrom 2009-01-24, so a Bitcoin explorer cannot date them. One sub-finding left unverified:\nrow 1's three sources agree on the date and disagree on the hour (7:07 PM / 4:07 PST / 11:07 PM);\nthe verdict does not depend on it.\n\n---",
   "status_line": 13,
   "found": true,
   "chars": 36,
   "status_text": "DONE \u2014 `recoveries/ledger-date-closure.md`, Merlin, 2026-10-09. 8 / 8 resolved, all\n`archive correct`; 0 `source correct`, 0 `indeterminate`, 0 `unresolved`. Every row settled\nby a dated primary or contemporaneous source fetched live this run (all 8 entry pages and 13\ncited sources HTTP 200, each SHA-256'd): SIP-0001's abstract bears *\"July 18, 2022 at 7:07 PM\"*\nfor row 1 (pass 2's own note that *\"none bears 2022 18\"* is wrong \u2014 it read the `CREATED:`\nheader, never the abstract); the king-of-stackchain article bears *\"July 18, 2022\"*; SIP-0004's\n`CREATED: 2022-7-20` plus its git history (earliest `2ac1fbab` 2022-07-21T02:11:47Z, 5 commits\nto 2022-08-09, which is exactly what the entry's own basis label warns); the cited AnthonyDessauer\npost *\"6:00 PM \u00b7 Aug 18, 2022\"*; the-fork-of-1492 article *\"August 28th, 2022 late in the\nmorning\"*; both cited X posts *\"Oct 7, 2022\"* (7:59 PM / 8:17 PM); *\"In mid-December 2022\"*;\nand *\"May 20th 2024\"* as the two-years article's own composition date against its 2025-07-22\nupload. The flag was a rule artifact: all 8 compare an event date against a source's\n*publication* date, which are supposed to differ for retrospectives and standards documents \u2014\nrecommend retiring or narrowing that flag rule. The archive's own `basis:` labels are accurate\non all 8 rows and do the disclosure work the badge tier is supposed to do. One void avenue\nrecorded so it is not repeated: Stackchain block numbers (1492/2079/2080) are the social chain's\nown numbering, not Bitcoin heights \u2014 `mempool.space/api/block-height/1492` returns a block\nfrom 2009-01-24, so a Bitcoin explorer cannot date them. One sub-finding left unverified:\nrow 1's three sources agree on the date and disagree on the hour (7:07 PM / 4:07 PST / 11:07 PM);\nthe verdict does not depend on it.\n\n---"
  },
  {
   "q": 12,
   "header_line": 985,
   "header": "## Q12 \u2014 Are the evidence tiers earned?",
   "category": "DONE",
   "status": "DONE \u2014 `recoveries/evidence-tier-audit.md`, Merlin, 2026-10-10. 18/18 `justified`, 0 `too\nstrong`, 0 `too weak`, 0 `indeterminate`; no badge in the sample misstates its evidence.",
   "status_line": 27,
   "found": true,
   "chars": 126,
   "status_text": "DONE \u2014 `recoveries/evidence-tier-audit.md`, Merlin, 2026-10-10. 18/18 `justified`, 0 `too\nstrong`, 0 `too weak`, 0 `indeterminate`; no badge in the sample misstates its evidence."
  },
  {
   "q": 13,
   "header_line": 1111,
   "header": "## Q13 \u2014 Publish the archive-side wording fixes, one at a time",
   "category": "OPEN",
   "status": "1 of 8 has a decision and staged correction (`magazine-091`; reply 09 \u00a73), but its decided note carries\nan authority/escalation caveat. Publication and third-party contact are on hold pending Alexander's explicit\nconfirmation. The other 7 are undecided and named in Q8 above. Archive-side work \u2014 not Zeph's unless he wants it.\nEntered by Timmy 2026-09-26, satisfying the Q7 obligation for this cycle.\n\nChannel note, 2026-09-27 \u2014 the relay's host is answered, and the item's decision state is unchanged.",
   "status_line": 18,
   "found": true,
   "chars": 35,
   "status_text": "1 of 8 has a decision and staged correction (`magazine-091`; reply 09 \u00a73), but its decided note carries\nan authority/escalation caveat. Publication and third-party contact are on hold pending Alexander's explicit\nconfirmation. The other 7 are undecided and named in Q8 above. Archive-side work \u2014 not Zeph's unless he wants it.\nEntered by Timmy 2026-09-26, satisfying the Q7 obligation for this cycle.\n\nChannel note, 2026-09-27 \u2014 the relay's host is answered, and the item's decision state is unchanged."
  },
  {
   "q": 14,
   "header_line": 1146,
   "header": "## Q14 \u2014 Put the Inbox on `alexanderwhitestone.com` behind a gate",
   "category": "OPEN",
   "status": "DONE \u2014 finished by `616794c` (2026-09-26), then re-measured by a later run the same day instead of being\nread back. The criterion above was met by an authenticated mobile-width render against the live URL; the\nfollowing run reproduced it with its own tools: authenticated `https://alexanderwhitestone.com/inbox/` HTTP 200,\n20,051 bytes, sha256 `b81e9fe7da42df6ad339ac19a4fc8a8052b9663c2129cc207077538dfe6b3639`, byte-identical to the only\nfile in `/opt/inbox-live`; anonymous `/inbox/` 401, `/inbox` 308, `/inbox/seed.json` 401, authenticated\n`/inbox/seed.json` 404; Playwright/Chromium at 390\u00d7844 against that URL \u2014 12 pending cards, 1 decided card, badge\n`12 open` \u2192 `10 open` after one approve and one defer, `aria-pressed=true`, three actions per card, 13 copy-out\nlines containing ids 1\u201312, localStorage keyed `{1,2}`, note surviving reload, decided view rendering, 0 page and 0\nconsole errors. Evidence: the live URL, the two hashes, the render output, and a named record of the gate\n(`basic_auth`, chosen by Alexander as option A). Two things do not close with it: credential delivery to\nAlexander is still unverified from this host \u2014 the credential is root-only on the box and its value is recorded in\nno artifact \u2014 and the public-repository exposure remains open and separate (see the standing blocker restated\nabove). No new pending state enters this repo meanwhile. Correction carried in this same entry: the claim that the\ncredential was \"not stored on this host\" was wrong in the earlier update and in reply 11; both artifacts now say\nso.\n\nRecord-accuracy correction: the sentence immediately above overstated the state when written. The Q14 entry had\nan appended correction, but reply 11 itself still contained the false claim until the later append committed after\nQ15. Reply 12 carried the substance meanwhile. The original sentences remain visible; the correction trail, not an\nin-place rewrite, is the evidence.\n\nVisibility measurement, 2026-09-27 \u2014 the input Alexander's decision was missing. Anonymous exposure\nunchanged from 2026-09-26: `GET /api/v1/repos/stackchain/troupe-standup` with no credential \u2192 HTTP 200,\n`\"private\": false`, `\"internal\": false`; anonymous raw seed over HTTPS \u2192 HTTP 200, 9,484 bytes, sha256\n`e4429147bc1bc25a5fc06df3b47a98e61d234775d055c278154fd466001585e0` (byte-identical to the value recorded on\n2026-09-26 \u2014 present *and* unchanged). \u00a75 of the build spec is still held: `inbox/pending.json` has never been\nadded on any ref (`git log --all --diff-filter=A -- inbox/pending.json` \u2192 no output) and `inbox/` contains only\n`seed-2026-09-26.json`, added by `7c4cf1b`. New, and it corrects an unstated risk in the way this question was\nframed: the pipe's own reads are authenticated, not anonymous \u2014 `/api/v1/user` with the environment token\nreturns 200, without a token 401, with a malformed token 401 \u2014 so making this repository private will not\nsilence the change gate. The visibility call can be made on its own merits.\n\nContainment measurement on the exposure itself, 2026-09-27. What the public repository currently holds from\nthe inbox artifact, measured rather than assumed: every string of \u226530 characters in the seed's pending items\nappears in exactly one file \u2014 the seed itself (`inbox/seed-2026-09-26.json`) \u2014 and in no other file in the repo;\nthe decided item's evidence strings appear in the seed and in `decisions/2026-09-26.md`, which the relay\npublished deliberately. No file of mine carries either. So the exposure is one file plus one by-design decision\nrecord, and this tick added nothing to it. The pending strings are not quoted here, by rule.\n\nDelivery-surface measurement, 2026-09-28 \u2014 the page and the live inbox have diverged. Zephyrus's check-in\n(`26e3cda`) reports the repository-visibility question as now sitting in front of Alexander as an inbox item. Measured\nthis tick instead of assumed: the export this host holds (`/opt/inbox-site/seed.json`, sha256 `e4429147\u202685e0`,\n`exported_at` `2026-09-26T17:31:00Z`) contains 12 pending (ids 1\u201312) and 1 decided (id 13), and the seed itself\nrecords that the Muse artifact is the live inbox while this file is a build seed. The gated page\n`https://alexanderwhitestone.com/inbox/` is byte-identical to a build of that export (sha256 `b81e9fe7\u2026b3639`), so\nthe page cannot be showing any item created after 2026-09-26T17:31Z \u2014 including the escalation in question.\nNothing has rebuilt the page since the `17:43` build, and `decisions/` has had no commit since 2026-09-26, so a\ndecision relayed today would not appear on the page either. The escalation's presence in the Muse artifact is\nTestimony only from this host (that artifact is not readable here). This is not a defect in either surface; it is a\nquestion only Alexander can settle \u2014 whether he wants to act on the page (then it needs a rebuild path) or in the\nartifact (then the page is a stale mirror). Named here so \"it is in front of him\" is not read as delivery on the page\nhis directive asked for. No pending material is quoted or duplicated by this measurement.\n\n---",
   "status_line": 64,
   "found": true,
   "chars": 119,
   "status_text": "DONE \u2014 finished by `616794c` (2026-09-26), then re-measured by a later run the same day instead of being\nread back. The criterion above was met by an authenticated mobile-width render against the live URL; the\nfollowing run reproduced it with its own tools: authenticated `https://alexanderwhitestone.com/inbox/` HTTP 200,\n20,051 bytes, sha256 `b81e9fe7da42df6ad339ac19a4fc8a8052b9663c2129cc207077538dfe6b3639`, byte-identical to the only\nfile in `/opt/inbox-live`; anonymous `/inbox/` 401, `/inbox` 308, `/inbox/seed.json` 401, authenticated\n`/inbox/seed.json` 404; Playwright/Chromium at 390\u00d7844 against that URL \u2014 12 pending cards, 1 decided card, badge\n`12 open` \u2192 `10 open` after one approve and one defer, `aria-pressed=true`, three actions per card, 13 copy-out\nlines containing ids 1\u201312, localStorage keyed `{1,2}`, note surviving reload, decided view rendering, 0 page and 0\nconsole errors. Evidence: the live URL, the two hashes, the render output, and a named record of the gate\n(`basic_auth`, chosen by Alexander as option A). Two things do not close with it: credential delivery to\nAlexander is still unverified from this host \u2014 the credential is root-only on the box and its value is recorded in\nno artifact \u2014 and the public-repository exposure remains open and separate (see the standing blocker restated\nabove). No new pending state enters this repo meanwhile. Correction carried in this same entry: the claim that the\ncredential was \"not stored on this host\" was wrong in the earlier update and in reply 11; both artifacts now say\nso.\n\nRecord-accuracy correction: the sentence immediately above overstated the state when written. The Q14 entry had\nan appended correction, but reply 11 itself still contained the false claim until the later append committed after\nQ15. Reply 12 carried the substance meanwhile. The original sentences remain visible; the correction trail, not an\nin-place rewrite, is the evidence.\n\nVisibility measurement, 2026-09-27 \u2014 the input Alexander's decision was missing. Anonymous exposure\nunchanged from 2026-09-26: `GET /api/v1/repos/stackchain/troupe-standup` with no credential \u2192 HTTP 200,\n`\"private\": false`, `\"internal\": false`; anonymous raw seed over HTTPS \u2192 HTTP 200, 9,484 bytes, sha256\n`e4429147bc1bc25a5fc06df3b47a98e61d234775d055c278154fd466001585e0` (byte-identical to the value recorded on\n2026-09-26 \u2014 present *and* unchanged). \u00a75 of the build spec is still held: `inbox/pending.json` has never been\nadded on any ref (`git log --all --diff-filter=A -- inbox/pending.json` \u2192 no output) and `inbox/` contains only\n`seed-2026-09-26.json`, added by `7c4cf1b`. New, and it corrects an unstated risk in the way this question was\nframed: the pipe's own reads are authenticated, not anonymous \u2014 `/api/v1/user` with the environment token\nreturns 200, without a token 401, with a malformed token 401 \u2014 so making this repository private will not\nsilence the change gate. The visibility call can be made on its own merits.\n\nContainment measurement on the exposure itself, 2026-09-27. What the public repository currently holds from\nthe inbox artifact, measured rather than assumed: every string of \u226530 characters in the seed's pending items\nappears in exactly one file \u2014 the seed itself (`inbox/seed-2026-09-26.json`) \u2014 and in no other file in the repo;\nthe decided item's evidence strings appear in the seed and in `decisions/2026-09-26.md`, which the relay\npublished deliberately. No file of mine carries either. So the exposure is one file plus one by-design decision\nrecord, and this tick added nothing to it. The pending strings are not quoted here, by rule.\n\nDelivery-surface measurement, 2026-09-28 \u2014 the page and the live inbox have diverged. Zephyrus's check-in\n(`26e3cda`) reports the repository-visibility question as now sitting in front of Alexander as an inbox item. Measured\nthis tick instead of assumed: the export this host holds (`/opt/inbox-site/seed.json`, sha256 `e4429147\u202685e0`,\n`exported_at` `2026-09-26T17:31:00Z`) contains 12 pending (ids 1\u201312) and 1 decided (id 13), and the seed itself\nrecords that the Muse artifact is the live inbox while this file is a build seed. The gated page\n`https://alexanderwhitestone.com/inbox/` is byte-identical to a build of that export (sha256 `b81e9fe7\u2026b3639`), so\nthe page cannot be showing any item created after 2026-09-26T17:31Z \u2014 including the escalation in question.\nNothing has rebuilt the page since the `17:43` build, and `decisions/` has had no commit since 2026-09-26, so a\ndecision relayed today would not appear on the page either. The escalation's presence in the Muse artifact is\nTestimony only from this host (that artifact is not readable here). This is not a defect in either surface; it is a\nquestion only Alexander can settle \u2014 whether he wants to act on the page (then it needs a rebuild path) or in the\nartifact (then the page is a stale mirror). Named here so \"it is in front of him\" is not read as delivery on the page\nhis directive asked for. No pending material is quoted or duplicated by this measurement.\n\n---"
  },
  {
   "q": 15,
   "header_line": 1265,
   "header": "## Q15 \u2014 Stop the monitor from waking on the pipe's own writes *(pipe; no dependencies)*",
   "category": "DONE",
   "status": "DONE \u2014 2026-09-26 \u224819:05 UTC.",
   "status_line": 12,
   "found": true,
   "chars": 131,
   "status_text": "DONE \u2014 2026-09-26 \u224819:05 UTC."
  },
  {
   "q": 16,
   "header_line": 1396,
   "header": "## Q16 \u2014 Per-platform ATS gate census *(career lane; opened 2026-10-01 by reply 21 \u00a73, drafted by zephyrus)*",
   "category": "VERIFIED-CLOSED",
   "status": "draft v0.1 landed `f29425a` (`career-lane/ats-gate-census-draft.md`, 2026-10-01; check-in `2f83e08`);\ncorrections returned in reply 22 (`c4a59aa`), not yet applied. Verified from this side this tick:\n\n- Greenhouse \u2014 filled, and reproduced. The rendered form\n  `job-boards.greenhouse.io/embed/job_app?for=lighthouse&token=4989378101` shows `LinkedIn Profile` optional;\n  the API's `required` flags agree (23 questions, 18 required, `Phone` required). Two drafting errors: the\n  posting's `updated_at` is 2026-09-29, not 2026-09-24, and \"11 live engineering titles\" is 11 postings over\n  6 of 25 titles.\n- Lever \u2014 filled, one correction. LinkedIn / GitHub / Portfolio carry no `required` marker\n  (`name=\"urls[LinkedIn]\"`); the anti-bot artifact is hCaptcha \u2014 `<div id=\"h-captcha\" class=\"h-captcha\"\n  data-sitekey=\"e33f87f8-\u2026\">` plus `js.hcaptcha.com/1/secure-api.js?host=jobs.lever.co`, `hcaptchaSubmitBtn`,\n  `hcaptchaResponse` \u00d712 \u2014 not reCAPTCHA: zero Google script references, zero `<div class=\"g-recaptcha\">`\n  elements, and the two `g-recaptcha` strings are stylesheet selectors.\n- Ashby \u2014 fillable without a rendered browser, and the draft's method gap is closed. The unauthenticated\n  job-board GraphQL op returns the whole form definition:\n  `POST jobs.ashbyhq.com/api/non-user-graphql?op=ApiJobPosting` with header `apikey: pub\u2026` (the key is in the\n  hosted page's `window.__appData`) and the `ApiJobPosting` query. Campaign method:\n  `/root/hermes-repertoire/01-career-engine/daily/2026-09-24/batch-3/ashby_form.py`. Re-run by Timmy 2026-10-01 on\n  the draft's own target (OpenAI `3c67f712-\u2026`): 17 fields, 14 required; LinkedIn optional; Phone required; two\n  acknowledgement fields required. The page also carries reCAPTCHA site keys (`recaptchaPublicSiteKey`,\n  `recaptchaUniversalPublicSiteKey`) and `.grecaptcha-badge` CSS, so anti-bot is answerable too.\n- Niceboard \u2014 open, with a lead. The draft's \"curl returns 0 bytes, likely bot filtering\" does not",
   "status_line": 15,
   "found": true,
   "chars": 157,
   "status_text": "draft v0.1 landed `f29425a` (`career-lane/ats-gate-census-draft.md`, 2026-10-01; check-in `2f83e08`);\ncorrections returned in reply 22 (`c4a59aa`), not yet applied. Verified from this side this tick:\n\n- Greenhouse \u2014 filled, and reproduced. The rendered form\n  `job-boards.greenhouse.io/embed/job_app?for=lighthouse&token=4989378101` shows `LinkedIn Profile` optional;\n  the API's `required` flags agree (23 questions, 18 required, `Phone` required). Two drafting errors: the\n  posting's `updated_at` is 2026-09-29, not 2026-09-24, and \"11 live engineering titles\" is 11 postings over\n  6 of 25 titles.\n- Lever \u2014 filled, one correction. LinkedIn / GitHub / Portfolio carry no `required` marker\n  (`name=\"urls[LinkedIn]\"`); the anti-bot artifact is hCaptcha \u2014 `<div id=\"h-captcha\" class=\"h-captcha\"\n  data-sitekey=\"e33f87f8-\u2026\">` plus `js.hcaptcha.com/1/secure-api.js?host=jobs.lever.co`, `hcaptchaSubmitBtn`,\n  `hcaptchaResponse` \u00d712 \u2014 not reCAPTCHA: zero Google script references, zero `<div class=\"g-recaptcha\">`\n  elements, and the two `g-recaptcha` strings are stylesheet selectors.\n- Ashby \u2014 fillable without a rendered browser, and the draft's method gap is closed. The unauthenticated\n  job-board GraphQL op returns the whole form definition:\n  `POST jobs.ashbyhq.com/api/non-user-graphql?op=ApiJobPosting` with header `apikey: pub\u2026` (the key is in the\n  hosted page's `window.__appData`) and the `ApiJobPosting` query. Campaign method:\n  `/root/hermes-repertoire/01-career-engine/daily/2026-09-24/batch-3/ashby_form.py`. Re-run by Timmy 2026-10-01 on\n  the draft's own target (OpenAI `3c67f712-\u2026`): 17 fields, 14 required; LinkedIn optional; Phone required; two\n  acknowledgement fields required. The page also carries reCAPTCHA site keys (`recaptchaPublicSiteKey`,\n  `recaptchaUniversalPublicSiteKey`) and `.grecaptcha-badge` CSS, so anti-bot is answerable too.\n- Niceboard \u2014 open, with a lead. The draft's \"curl returns 0 bytes, likely bot filtering\" does not"
  },
  {
   "q": 17,
   "header_line": 1553,
   "header": "## Q17 \u2014 Employer-side AI-authorship refusal gates *(career lane; opened 2026-10-03 by reply 26, per Q7)*",
   "category": "NO-MARKER",
   "status": null,
   "status_line": null,
   "found": false,
   "chars": 38,
   "status_text": null
  },
  {
   "q": 18,
   "header_line": 1591,
   "header": "## Q18 \u2014 Employer-side lead intake must be deduped against the prepared index *(career lane; opened 2026-10-04 by reply 28, per the G2i miss)*",
   "category": "NO-MARKER",
   "status": null,
   "status_line": null,
   "found": false,
   "chars": 177,
   "status_text": null
  },
  {
   "q": 19,
   "header_line": 1768,
   "header": "## Q19 \u2014 Three proposed members (local Mac wizard, Grok, Mistral) *(wizard onboarding; opened 2026-10-06 by zephyrus-sparkborn, `checkins/2026-10-06-zephyrus-wizards*.md` + `JOIN-THE-TROUPE.md`)*",
   "category": "RESOLVED",
   "status": "RESOLVED \u2014 provisional (2026-10-06).",
   "status_line": 2,
   "found": true,
   "chars": 344,
   "status_text": "RESOLVED \u2014 provisional (2026-10-06)."
  },
  {
   "q": 20,
   "header_line": 2112,
   "header": "## Q20 \u2014 Excerpt fidelity and placement for the 91 magazine entries *(archive verification; opened 2026-10-08 by the pipe, per Q7's never-dry obligation)*",
   "category": "VERIFIED-CLOSED",
   "status": "DONE \u2014 `recoveries/excerpt-placement-audit.md` (12,914 B) and `recoveries/excerpt-placement-rows.md`\n(74,561 B), Merlin, 2026-10-12T04:41\u201304:53Z, this host. Population: all 91 magazine entries, no\nsampling \u2014 269 excerpts (87 entries \u00d7 3, 4 entries \u00d7 2). Class counts: 269 `literal` / 0\n`normalised-literal` / 0 `elided` / 0 `paraphrase` / 0 `unreadable`. No row needed quote-style,\ndash, whitespace or URL normalisation: the excerpt text as the entry page prints it is already an\nexact substring of the detagged article body at S0. Placement measured for 269/269 in one space (S1,\nboth sides): offsets 0\u201320,641 characters, fractions 0.0000\u20130.9472, mean 0.4735, buckets\n53/65/51/61/39 across fifths \u2014 near-uniform, 0 entries quoting only the last 20%, 2 quoting only\nthe first (`magazine-043`, `magazine-050`). Named: `magazine-057` widest spread 0.8923,\n`magazine-027` narrowest 0.0094, `magazine-019` highest mean 0.7905, `magazine-050` lowest 0.0394.\nAll 91 anchors are `www.stackchainmagazine.net` article URLs, all HTTP 200, so `unreadable` has no\npopulation in this class (the X-post, Wayback, SIP and podcast anchors belong to the non-magazine\nentries and to Q10/Q21's classes).\n- Two archive-side facts, neither a defect: every one of the 269 magazine blockquotes prints its\n  own anchor URL as the `<cite>` text, so the URL appears twice per excerpt on the rendered page \u2014\n  recorded so the next external matcher strips the `<cite>` before comparing; and 2 of the 269\n  excerpts (`magazine-080` seq 1, `magazine-082` seq 1) are the article's own headline, occurring 4\n  times each at offset 0, so their `fraction` of 0.0000 is a document position, not a placement\n  inside the prose. `magazine-040` seq 2 is a refrain, occurring 6 times; placement is\n  first-occurrence, stated in advance.\n- Independent second method, 269/269: stripping both strings to lowercase letters and digits\n  only, the excerpt's image is a substring of the article's image and a prefix of the image of\n  the body slice at the reported offset. Tests the offset arithmetic rather than re-running the\n  matcher. Cross-check against `recoveries/excerpt-binding-audit.md`: its 269 magazine rows are all\n  `bound` with settling evidence \"verbatim at\" (2026-10-10) \u2014 two days, two independent passes, the\n  same verdict.\n- Limits stated: the detagged body includes site chrome, so `fraction` is a document-position\n  measure, not a position within the article's prose; placement is first-occurrence (3 rows have\n  more than one occurrence); 45 excerpts are under 40 characters (shortest 9, `magazine-008` seq 2\n  \"eat tacos\"), so for those the placement number is weak evidence of representativeness though the\n  match is exact; byte counts and hashes are dated readings (2026-10-12T04:41\u201304:43Z).\n- Three defects of mine, logged first in the record: (1) the excerpt unit included the `<cite>`\n  URL, so all 269 rows first read `paraphrase` \u2014 caught by reading `magazine-091`'s HTML rather than\n  trusting the tally; (2) offsets were taken in S0 space and divided by an S1 body length, so every\n  fraction was wrong until the measurement was re-run in one space \u2014 72 of 269 offsets moved;\n  (3) my first second-method test was itself wrong (it compared the gap against the head length),\n  replaced by the character-class method. No archive-side wording fix follows from this item.\n- Q7, measured: the unclaimed executable set after this run is empty \u2014 Q20 was the last one.\n  Q9 waits on the checksum handover, Q13 and Q19 on Alexander, Q21\u2013Q28 closed, Q30\u2013Q35 closed and\n  verified. Nothing opened this tick; the queue is now dry of executable items, which is itself the\n  finding for Q7.\n\nQ20 verified and closed from this host \u2014 2026-10-12 05:04\u201305:09Z (control plane). Written after reading the\ntip (`9a1de9a` \u2192 `d2a9cae`); the aggregates below were recomputed by this pipe's own parser over\n`recoveries/excerpt-placement-rows.md` and the measurement was re-run from fresh fetches, not re-read.\n\n- Aggregates recomputed, every one exact: 269 rows, 269 `literal` / 0 / 0 / 0 / 0; 91 entries (87 \u00d7 3 +\n  4 \u00d7 2); offsets 0\u201320,641; fractions 0.0000\u20130.9472; mean 0.4735; buckets 53/65/51/61/39; only-first\n  {`magazine-043`, `magazine-050`}; only-last none; the named spread and mean extremes reproduce as named.\n- Independent sample, my fetch and my ladder, 05:04\u201305:08Z: index `https://alexanderwhitestone.com/stackchain/blocks/`\n  \u2192 200 / 34,488 B / `4f764ef4dfb9\u2026` (exact); 121 entry links = 8 `block-` + 22 `event-` + 91 `magazine-`;\n  eight entry pages and their eight articles re-fetched (all 200); 24/24 excerpts are exact S0 substrings of the\n  bodies I fetched, 24/24 offsets and fractions reproduce in S1 space, `<cite>` text equals the anchor URL on\n  all 24 (finding 3 confirmed); my S1 body length for `magazine-091`'s article is 9,120 \u2014 the record's own\n  figure, so the two ladders agree on totals. The mixed-space variant reproduces the shifted offsets, so defect 2 is\n  a real repair rather than a re-run.\n- Cross-check verified, one precision: `recoveries/excerpt-binding-audit.md` carries 300 `magazine-` rows, of\n  which 269 are `bound` with \"verbatim at\" (31 are \"named in prose, no anchor on the page\").\n- Anonymous readbacks re-run here, no credential: record 200 / 14,045 / `4b1052df\u2026`, rows 200 / 74,561 /\n  `880223f3\u2026`, check-in 200 / 23,015, each `cmp` byte-identical to disk.\n- Grades: the sample Documented (my fetches, clocked); the class for the population Corroborated (his\n  269/269 + my 24/24 + Q21's 269 `bound`); the aggregates Documented as arithmetic over the published rows file;\n  \"45 excerpts under 40 characters\" Testimony only (shortest spot-checked: `eat tacos`, 9 characters).\n- Corrections logged, never deleted: (C16) the pair (`e72062a3\u2026`, 13,062 B) cannot describe one artifact \u2014\n  the revision carrying that digest is 13,364 B (`git cat-file -s 95dfbf3:recoveries/excerpt-placement-audit.md`\n  \u2192 `13364`; `git cat-file -p \u2026 | sha256sum` \u2192 `e72062a3\u2026`), and the wrong figure sits in the record's note, the\n  check-in's Run 3 landing table and `5fe58aa`'s message. (C17) the revision chain has four links \u2014\n  12,914 (`9dced5eb\u2026`) \u2192 13,364 (`e72062a3\u2026`) \u2192 13,738 (`2e5241c9\u2026`) \u2192 14,045 (`4b1052df\u2026`, `5fe58aa`) \u2014 the\n  fourth unlisted in both tables and read back anonymously by this tick. (C18) the Q20 lane was named in the\n  same paragraph as the \"take Q20 as your next unit\" line, so the failed check was a reading of the open\n  paragraph, not a trip to the roster that was not taken. (C19) marking the item DONE replaced the\n  label-reconciliation paragraph rather than appending to it; restored here in this pipe's words \u2014 Q20 was the\n  control plane's named next pick for zephyrus-sparkborn (lane correction 2026-10-10 13:53Z) and the oldest\n  executable item in the queue.\n- Q7, measured, corrected in place: the pre-existing unclaimed executable set is empty (Q9 human-gated on\n  the checksum handover, Q13/Q19 on Alexander, Q21\u2013Q28 closed, Q30\u2013Q35 closed and verified) \u2014 so this tick opens\n  Q36 below, for a hole measured in this pipe's own monitor, not for invented archive work. Merlin's two Helm\n  candidates are recorded in Q36's block as candidates awaiting Alexander's pick.\n- Attribution fault, logged because the public history now misstates authorship: `9a1de9a`, `95dfbf3`,\n  `48bf86b`, `5fe58aa`, `d2a9cae` are authored `Timmy <timmy@stackchain.ai>` while their content is Merlin's (his\n  check-ins and landing tables say so in the first person). No commit can be restated; this record says it.\n\n---",
   "status_line": 37,
   "found": true,
   "chars": 121,
   "status_text": "DONE \u2014 `recoveries/excerpt-placement-audit.md` (12,914 B) and `recoveries/excerpt-placement-rows.md`\n(74,561 B), Merlin, 2026-10-12T04:41\u201304:53Z, this host. Population: all 91 magazine entries, no\nsampling \u2014 269 excerpts (87 entries \u00d7 3, 4 entries \u00d7 2). Class counts: 269 `literal` / 0\n`normalised-literal` / 0 `elided` / 0 `paraphrase` / 0 `unreadable`. No row needed quote-style,\ndash, whitespace or URL normalisation: the excerpt text as the entry page prints it is already an\nexact substring of the detagged article body at S0. Placement measured for 269/269 in one space (S1,\nboth sides): offsets 0\u201320,641 characters, fractions 0.0000\u20130.9472, mean 0.4735, buckets\n53/65/51/61/39 across fifths \u2014 near-uniform, 0 entries quoting only the last 20%, 2 quoting only\nthe first (`magazine-043`, `magazine-050`). Named: `magazine-057` widest spread 0.8923,\n`magazine-027` narrowest 0.0094, `magazine-019` highest mean 0.7905, `magazine-050` lowest 0.0394.\nAll 91 anchors are `www.stackchainmagazine.net` article URLs, all HTTP 200, so `unreadable` has no\npopulation in this class (the X-post, Wayback, SIP and podcast anchors belong to the non-magazine\nentries and to Q10/Q21's classes).\n- Two archive-side facts, neither a defect: every one of the 269 magazine blockquotes prints its\n  own anchor URL as the `<cite>` text, so the URL appears twice per excerpt on the rendered page \u2014\n  recorded so the next external matcher strips the `<cite>` before comparing; and 2 of the 269\n  excerpts (`magazine-080` seq 1, `magazine-082` seq 1) are the article's own headline, occurring 4\n  times each at offset 0, so their `fraction` of 0.0000 is a document position, not a placement\n  inside the prose. `magazine-040` seq 2 is a refrain, occurring 6 times; placement is\n  first-occurrence, stated in advance.\n- Independent second method, 269/269: stripping both strings to lowercase letters and digits\n  only, the excerpt's image is a substring of the article's image and a prefix of the image of\n  the body slice at the reported offset. Tests the offset arithmetic rather than re-running the\n  matcher. Cross-check against `recoveries/excerpt-binding-audit.md`: its 269 magazine rows are all\n  `bound` with settling evidence \"verbatim at\" (2026-10-10) \u2014 two days, two independent passes, the\n  same verdict.\n- Limits stated: the detagged body includes site chrome, so `fraction` is a document-position\n  measure, not a position within the article's prose; placement is first-occurrence (3 rows have\n  more than one occurrence); 45 excerpts are under 40 characters (shortest 9, `magazine-008` seq 2\n  \"eat tacos\"), so for those the placement number is weak evidence of representativeness though the\n  match is exact; byte counts and hashes are dated readings (2026-10-12T04:41\u201304:43Z).\n- Three defects of mine, logged first in the record: (1) the excerpt unit included the `<cite>`\n  URL, so all 269 rows first read `paraphrase` \u2014 caught by reading `magazine-091`'s HTML rather than\n  trusting the tally; (2) offsets were taken in S0 space and divided by an S1 body length, so every\n  fraction was wrong until the measurement was re-run in one space \u2014 72 of 269 offsets moved;\n  (3) my first second-method test was itself wrong (it compared the gap against the head length),\n  replaced by the character-class method. No archive-side wording fix follows from this item.\n- Q7, measured: the unclaimed executable set after this run is empty \u2014 Q20 was the last one.\n  Q9 waits on the checksum handover, Q13 and Q19 on Alexander, Q21\u2013Q28 closed, Q30\u2013Q35 closed and\n  verified. Nothing opened this tick; the queue is now dry of executable items, which is itself the\n  finding for Q7.\n\nQ20 verified and closed from this host \u2014 2026-10-12 05:04\u201305:09Z (control plane). Written after reading the\ntip (`9a1de9a` \u2192 `d2a9cae`); the aggregates below were recomputed by this pipe's own parser over\n`recoveries/excerpt-placement-rows.md` and the measurement was re-run from fresh fetches, not re-read.\n\n- Aggregates recomputed, every one exact: 269 rows, 269 `literal` / 0 / 0 / 0 / 0; 91 entries (87 \u00d7 3 +\n  4 \u00d7 2); offsets 0\u201320,641; fractions 0.0000\u20130.9472; mean 0.4735; buckets 53/65/51/61/39; only-first\n  {`magazine-043`, `magazine-050`}; only-last none; the named spread and mean extremes reproduce as named.\n- Independent sample, my fetch and my ladder, 05:04\u201305:08Z: index `https://alexanderwhitestone.com/stackchain/blocks/`\n  \u2192 200 / 34,488 B / `4f764ef4dfb9\u2026` (exact); 121 entry links = 8 `block-` + 22 `event-` + 91 `magazine-`;\n  eight entry pages and their eight articles re-fetched (all 200); 24/24 excerpts are exact S0 substrings of the\n  bodies I fetched, 24/24 offsets and fractions reproduce in S1 space, `<cite>` text equals the anchor URL on\n  all 24 (finding 3 confirmed); my S1 body length for `magazine-091`'s article is 9,120 \u2014 the record's own\n  figure, so the two ladders agree on totals. The mixed-space variant reproduces the shifted offsets, so defect 2 is\n  a real repair rather than a re-run.\n- Cross-check verified, one precision: `recoveries/excerpt-binding-audit.md` carries 300 `magazine-` rows, of\n  which 269 are `bound` with \"verbatim at\" (31 are \"named in prose, no anchor on the page\").\n- Anonymous readbacks re-run here, no credential: record 200 / 14,045 / `4b1052df\u2026`, rows 200 / 74,561 /\n  `880223f3\u2026`, check-in 200 / 23,015, each `cmp` byte-identical to disk.\n- Grades: the sample Documented (my fetches, clocked); the class for the population Corroborated (his\n  269/269 + my 24/24 + Q21's 269 `bound`); the aggregates Documented as arithmetic over the published rows file;\n  \"45 excerpts under 40 characters\" Testimony only (shortest spot-checked: `eat tacos`, 9 characters).\n- Corrections logged, never deleted: (C16) the pair (`e72062a3\u2026`, 13,062 B) cannot describe one artifact \u2014\n  the revision carrying that digest is 13,364 B (`git cat-file -s 95dfbf3:recoveries/excerpt-placement-audit.md`\n  \u2192 `13364`; `git cat-file -p \u2026 | sha256sum` \u2192 `e72062a3\u2026`), and the wrong figure sits in the record's note, the\n  check-in's Run 3 landing table and `5fe58aa`'s message. (C17) the revision chain has four links \u2014\n  12,914 (`9dced5eb\u2026`) \u2192 13,364 (`e72062a3\u2026`) \u2192 13,738 (`2e5241c9\u2026`) \u2192 14,045 (`4b1052df\u2026`, `5fe58aa`) \u2014 the\n  fourth unlisted in both tables and read back anonymously by this tick. (C18) the Q20 lane was named in the\n  same paragraph as the \"take Q20 as your next unit\" line, so the failed check was a reading of the open\n  paragraph, not a trip to the roster that was not taken. (C19) marking the item DONE replaced the\n  label-reconciliation paragraph rather than appending to it; restored here in this pipe's words \u2014 Q20 was the\n  control plane's named next pick for zephyrus-sparkborn (lane correction 2026-10-10 13:53Z) and the oldest\n  executable item in the queue.\n- Q7, measured, corrected in place: the pre-existing unclaimed executable set is empty (Q9 human-gated on\n  the checksum handover, Q13/Q19 on Alexander, Q21\u2013Q28 closed, Q30\u2013Q35 closed and verified) \u2014 so this tick opens\n  Q36 below, for a hole measured in this pipe's own monitor, not for invented archive work. Merlin's two Helm\n  candidates are recorded in Q36's block as candidates awaiting Alexander's pick.\n- Attribution fault, logged because the public history now misstates authorship: `9a1de9a`, `95dfbf3`,\n  `48bf86b`, `5fe58aa`, `d2a9cae` are authored `Timmy <timmy@stackchain.ai>` while their content is Merlin's (his\n  check-ins and landing tables say so in the first person). No commit can be restated; this record says it.\n\n---"
  },
  {
   "q": 21,
   "header_line": 2233,
   "header": "## Q21 \u2014 Does every quoted excerpt resolve at the URL it is printed against?",
   "category": "UNCLAIMED",
   "status": "open and unclaimed. Opened by the pipe 2026-10-10",
   "status_line": 31,
   "found": true,
   "chars": 134,
   "status_text": "open and unclaimed. Opened by the pipe 2026-10-10"
  },
  {
   "q": 22,
   "header_line": 2367,
   "header": "## Q22 \u2014 Do the named-but-unlinked sources resolve? *(proposed 2026-10-10 by Merlin, per Q7; not yet opened)*",
   "category": "DONE",
   "status": "DONE \u2014 `recoveries/named-source-liveness.md`, Merlin, 2026-10-10. 28 fetches \u2192 27 distinct\nsources: 20 `resolve` (19 X accounts + the 1 archive URL), 1 `resolve-moved`, 2 `suspended`, 3 `404`.\nSix entries named whose source does not resolve: `magazine-020`, `magazine-051`, `magazine-035`,\n`magazine-039`, `magazine-056`, `event-2022-08-18-the-bitcoin-beach-campaign-closes-and-hodlon`.",
   "status_line": 22,
   "found": true,
   "chars": 110,
   "status_text": "DONE \u2014 `recoveries/named-source-liveness.md`, Merlin, 2026-10-10. 28 fetches \u2192 27 distinct\nsources: 20 `resolve` (19 X accounts + the 1 archive URL), 1 `resolve-moved`, 2 `suspended`, 3 `404`.\nSix entries named whose source does not resolve: `magazine-020`, `magazine-051`, `magazine-035`,\n`magazine-039`, `magazine-056`, `event-2022-08-18-the-bitcoin-beach-campaign-closes-and-hodlon`."
  },
  {
   "q": 23,
   "header_line": 2477,
   "header": "## Q23 \u2014 The prose-named sources the `@` token rule cannot see *(archive verification; opened 2026-10-10 by the pipe, per Q7's never-dry obligation)*",
   "category": "DONE",
   "status": "DONE 2026-10-10 \u2014 `recoveries/named-source-liveness-unlinked.md` (Merlin), verified from the published file this tick (control plane).",
   "status_line": 55,
   "found": true,
   "chars": 144,
   "status_text": "DONE 2026-10-10 \u2014 `recoveries/named-source-liveness-unlinked.md` (Merlin), verified from the published file this tick (control plane)."
  },
  {
   "q": 24,
   "header_line": 2621,
   "header": "## Q24 \u2014 The Q13 fix pack: stage every verified live-page fix as one reviewable approval *(archive-side; opened 2026-10-10 by the pipe, per Q7's never-dry obligation)*",
   "category": "UNCLAIMED",
   "status": "open and unclaimed. Opened by the pipe 2026-10-10",
   "status_line": 63,
   "found": true,
   "chars": 145,
   "status_text": "open and unclaimed. Opened by the pipe 2026-10-10"
  },
  {
   "q": 25,
   "header_line": 2766,
   "header": "## Q25 \u2014 A prose-anchor convention for the ledger build *(archive-side; proposed 2026-10-10 by Merlin, per Q7's never-dry obligation \u2014 Q24 closed and the unclaimed executable set fell to zero)*",
   "category": "DONE",
   "status": "DONE \u2014 `recoveries/prose-anchor-convention.md`, Merlin, 2026-10-10. Designed, prototyped and\nmeasured in a scratch tree; nothing published, nothing applied to the shared build tree.",
   "status_line": 36,
   "found": true,
   "chars": 292,
   "status_text": "DONE \u2014 `recoveries/prose-anchor-convention.md`, Merlin, 2026-10-10. Designed, prototyped and\nmeasured in a scratch tree; nothing published, nothing applied to the shared build tree."
  },
  {
   "q": 26,
   "header_line": 3058,
   "header": "## Q26 \u2014 Make the silent token classes loud, and measure the fifth slot *(archive-side; opened 2026-10-10 by the pipe, per Q7's never-dry obligation \u2014 Q25 closed at `a9f23a6` and the unclaimed executable set fell to zero)*",
   "category": "DONE",
   "status": "DONE \u2014 `recoveries/prose-anchor-hardening.md`, Merlin, 2026-10-10\u219211 (~00:20\u201300:24 UTC).\nThe hardened prototype is built and every negative class now dies at build time; nothing\npublished, nothing applied to the shared build tree.",
   "status_line": 66,
   "found": true,
   "chars": 197,
   "status_text": "DONE \u2014 `recoveries/prose-anchor-hardening.md`, Merlin, 2026-10-10\u219211 (~00:20\u201300:24 UTC).\nThe hardened prototype is built and every negative class now dies at build time; nothing\npublished, nothing applied to the shared build tree."
  },
  {
   "q": 27,
   "header_line": 3255,
   "header": "## Q27 \u2014 A fixture at every render site: make the token sentinel's coverage total *(archive-side; opened 2026-10-11 by the pipe, per Q7's never-dry obligation \u2014 Q26 closed at `f05179e`)*",
   "category": "CLOSED",
   "status": "DONE 2026-10-11 \u2014 `recoveries/render-site-coverage.md` (Merlin). 32 sites: 28 covered by fixture, 4 structural exclusions; 35 fixtures, every negative writes 0 files; the scope clause closed with option (a), all four token classes now pre-write; no-token build still byte-identical at `91ecf6bf`.",
   "status_line": 55,
   "found": true,
   "chars": 133,
   "status_text": "DONE 2026-10-11 \u2014 `recoveries/render-site-coverage.md` (Merlin). 32 sites: 28 covered by fixture, 4 structural exclusions; 35 fixtures, every negative writes 0 files; the scope clause closed with option (a), all four token classes now pre-write; no-token build still byte-identical at `91ecf6bf`."
  },
  {
   "q": 28,
   "header_line": 3388,
   "header": "## Q28 \u2014 The channels the entry walk cannot see: state the guarantee, then cover what it cannot reach",
   "category": "DONE",
   "status": "DONE 2026-10-11 \u2014 `recoveries/render-site-channels.md` (Merlin), scratch tree\n`/root/crucible/q28/`. 20 channels: 13 covered by fixture (19 fixtures), 7 excluded with a\nmeasured command; every negative exits 1 with 0 builder writes; the no-token control is\nbyte-identical to the live `site-ledger` at `91ecf6bf`.",
   "status_line": 80,
   "found": true,
   "chars": 185,
   "status_text": "DONE 2026-10-11 \u2014 `recoveries/render-site-channels.md` (Merlin), scratch tree\n`/root/crucible/q28/`. 20 channels: 13 covered by fixture (19 fixtures), 7 excluded with a\nmeasured command; every negative exits 1 with 0 builder writes; the no-token control is\nbyte-identical to the live `site-ledger` at `91ecf6bf`."
  },
  {
   "q": 29,
   "header_line": 3573,
   "header": "## Q29 \u2014 The guards that are not the walk: what protects a page when the value is not a token",
   "category": "DONE",
   "status": "DONE 2026-10-11 \u2014 `recoveries/render-site-guards.md` (Merlin), scratch tree `/root/crucible/q29/`. 22 fixtures plus the control, every negative or escape claim measured against the emitted byte; the second guarantee stated in one sentence; one finding: an unguarded `int(sats)` can still leave a partial tree (2 files).",
   "status_line": 80,
   "found": true,
   "chars": 174,
   "status_text": "DONE 2026-10-11 \u2014 `recoveries/render-site-guards.md` (Merlin), scratch tree `/root/crucible/q29/`. 22 fixtures plus the control, every negative or escape claim measured against the emitted byte; the second guarantee stated in one sentence; one finding: an unguarded `int(sats)` can still leave a partial tree (2 files)."
  },
  {
   "q": 30,
   "header_line": 3747,
   "header": "## Q30 \u2014 The renderer's entry point: the one path no gate executes",
   "category": "DONE",
   "status": "DONE 2026-10-11 \u2014 `recoveries/helm-cli-entry-point.md` (Merlin), all four steps of the\n  item plus the destination gate the 09:21Z addendum added. The Helm files are host-local\n  (`/root/.helm/`, outside this repo), so the record, transcripts and digests live in the check-in\n  and the recoveries file; both were read back over the anonymous raw path and `cmp`-checked.\n\n  - The defect reproduced before the fix (measured ~09:50Z): `python3\n  /root/.helm/bin/helm-render.py` \u2192 exit 1, `NameError: name 'build_page' is not defined`,\n  traceback naming `:91` and `:78`; identical with `--out /tmp/helm-cli-probe.html --as-of\n  2026-10-11T12:00:00Z`; no file written. Pre-fix file 18,929 B / sha256\n  `00d14453d95234ef49a1d8758ab2de76143e848191331bfec38603e6263403e6`.\n  - The guard moved to the end of the file (`:495` of 495 lines, below `build_page()` at `:273`);\n  `--out`/`--as-of` semantics unchanged. Fixed renderer 21,766 B / sha256\n  `5c67473d89283c3d4434928dc96d45ff48a41d8f443ecc3c98e9236be8b597f9`.\n  - The destination is gated, per the 09:21Z addendum: `OUT_DEFAULT` is production, so `main()`\n  resolves the destination and refuses a production write without `--deploy` \u2014 exit 2, a\n  message naming the path and the flag \u2014 and `parse_args()` now returns\n  `(out, now, explicit_out, deploy)`.\n  - Gate G7 added \u2014 the CLI executed in a subprocess, asserting on emitted bytes: exit 0 on a\n  staged render; the file exists; its bytes equal `build_page()`'s at the same pinned clock; the\n  reported byte count matches the file; `--as-of` honoured; the live document root untouched; the\n  production destination refused both by default and by explicit `--out <prod path>` (matched by\n  `resolve()`, not string equality); the `--deploy` branch exercised against a patched\n  `OUT_DEFAULT`, never the real one; and a source-order guard so the Q30 defect cannot silently\n  return. 17 new assertions.",
   "status_line": 111,
   "found": true,
   "chars": 215,
   "status_text": "DONE 2026-10-11 \u2014 `recoveries/helm-cli-entry-point.md` (Merlin), all four steps of the\n  item plus the destination gate the 09:21Z addendum added. The Helm files are host-local\n  (`/root/.helm/`, outside this repo), so the record, transcripts and digests live in the check-in\n  and the recoveries file; both were read back over the anonymous raw path and `cmp`-checked.\n\n  - The defect reproduced before the fix (measured ~09:50Z): `python3\n  /root/.helm/bin/helm-render.py` \u2192 exit 1, `NameError: name 'build_page' is not defined`,\n  traceback naming `:91` and `:78`; identical with `--out /tmp/helm-cli-probe.html --as-of\n  2026-10-11T12:00:00Z`; no file written. Pre-fix file 18,929 B / sha256\n  `00d14453d95234ef49a1d8758ab2de76143e848191331bfec38603e6263403e6`.\n  - The guard moved to the end of the file (`:495` of 495 lines, below `build_page()` at `:273`);\n  `--out`/`--as-of` semantics unchanged. Fixed renderer 21,766 B / sha256\n  `5c67473d89283c3d4434928dc96d45ff48a41d8f443ecc3c98e9236be8b597f9`.\n  - The destination is gated, per the 09:21Z addendum: `OUT_DEFAULT` is production, so `main()`\n  resolves the destination and refuses a production write without `--deploy` \u2014 exit 2, a\n  message naming the path and the flag \u2014 and `parse_args()` now returns\n  `(out, now, explicit_out, deploy)`.\n  - Gate G7 added \u2014 the CLI executed in a subprocess, asserting on emitted bytes: exit 0 on a\n  staged render; the file exists; its bytes equal `build_page()`'s at the same pinned clock; the\n  reported byte count matches the file; `--as-of` honoured; the live document root untouched; the\n  production destination refused both by default and by explicit `--out <prod path>` (matched by\n  `resolve()`, not string equality); the `--deploy` branch exercised against a patched\n  `OUT_DEFAULT`, never the real one; and a source-order guard so the Q30 defect cannot silently\n  return. 17 new assertions."
  },
  {
   "q": 31,
   "header_line": 3962,
   "header": "## Q31 \u2014 The collector's entry point: the sibling path no gate has executed either",
   "category": "DONE",
   "status": "DONE at Merlin's Run 6 (2026-10-11 \u224813:19\u201313:35Z) \u2014 deliverable `recoveries/helm-collector-run.md`; the collector's entry point is executed, its destination is gated, and G8 asserts it.",
   "status_line": 73,
   "found": true,
   "chars": 406,
   "status_text": "DONE at Merlin's Run 6 (2026-10-11 \u224813:19\u201313:35Z) \u2014 deliverable `recoveries/helm-collector-run.md`; the collector's entry point is executed, its destination is gated, and G8 asserts it."
  },
  {
   "q": 32,
   "header_line": 4368,
   "header": "## Q32 \u2014 The G8 two-run agreement check is nondeterministic: `age_seconds` is not scrubbed *(Helm lane; opened 2026-10-11 by the pipe, per Q7's never-dry obligation \u2014 Q31's adoption is blocked behind it)*",
   "category": "OPEN",
   "status": "OPEN \u2014 named to the Helm lane",
   "status_line": 16,
   "found": true,
   "chars": 70,
   "status_text": "OPEN \u2014 named to the Helm lane"
  },
  {
   "q": 33,
   "header_line": 4438,
   "header": "## Q33 \u2014 Split the newest-file pointer out of `evidence.source_path` *(collector-side; opened 2026-10-11 by the pipe, per Q7's never-dry obligation \u2014 Q32 closed at `7e12c82`)*",
   "category": "OPEN",
   "status": "OPEN \u2014 named to the Helm lane.",
   "status_line": 16,
   "found": true,
   "chars": 114,
   "status_text": "OPEN \u2014 named to the Helm lane."
  },
  {
   "q": 34,
   "header_line": 4552,
   "header": "## Q34 \u2014 Gate the pointer's null case *(collector-side gate; opened 2026-10-11 by the pipe, per Q7's never-dry obligation \u2014 Q33 closed at `8bb88da`)*",
   "category": "DONE",
   "status": "DONE 2026-10-12 \u2014 `recoveries/helm-null-gate.md` (Merlin), scratch tree `/root/crucible/q34/`.",
   "status_line": 16,
   "found": true,
   "chars": 176,
   "status_text": "DONE 2026-10-12 \u2014 `recoveries/helm-null-gate.md` (Merlin), scratch tree `/root/crucible/q34/`."
  },
  {
   "q": 35,
   "header_line": 4728,
   "header": "## Q35 \u2014 The gate must refuse a subject collector that carries no destination rule *(Helm lane; opened 2026-10-12 by the pipe, per Q7's never-dry obligation \u2014 Q34 verified and closed at `ac98bfb`)*",
   "category": "DONE",
   "status": "DONE \u2014 `recoveries/helm-precondition-gate.md` (8,261 B / sha256\n`a5d3ad6af205f3c1c8caf4f4baa2ee01548b5a89697ff5478e3fc52a9a61656b`), Merlin, 2026-10-12T02:10\u201302:36Z, this host.",
   "status_line": 23,
   "found": true,
   "chars": 168,
   "status_text": "DONE \u2014 `recoveries/helm-precondition-gate.md` (8,261 B / sha256\n`a5d3ad6af205f3c1c8caf4f4baa2ee01548b5a89697ff5478e3fc52a9a61656b`), Merlin, 2026-10-12T02:10\u201302:36Z, this host."
  },
  {
   "q": 36,
   "header_line": 4896,
   "header": "## Q36 \u2014 The monitor cannot see a counterparty write that carries this pipe's identity *(pipe tooling; opened 2026-10-12 by the pipe, per Q7's never-dry obligation \u2014 Q20 verified and closed at `9a1de9a` and the pre-existing executable set fell to empty)*",
   "category": "DONE",
   "status": "DONE \u2014 the rule holds, and the predicted transition arrived exactly as stated.",
   "status_line": 49,
   "found": true,
   "chars": 89,
   "status_text": "DONE \u2014 the rule holds, and the predicted transition arrived exactly as stated."
  },
  {
   "q": 37,
   "header_line": 4985,
   "header": "## Q37 \u2014 The identity rule closes one class, not the class *(pipe tooling; opened 2026-10-12 by the pipe, per Q7's never-dry obligation \u2014 Q36 closed at `9584984` and the unclaimed executable set fell to empty)*",
   "category": "NO-MARKER",
   "status": null,
   "status_line": null,
   "found": false,
   "chars": 33,
   "status_text": null
  },
  {
   "q": 38,
   "header_line": 5018,
   "header": "## Q38 \u2014 The behavioural destination guard *(Helm lane; opened 2026-10-12 by Merlin \u2014 Q36's candidate 2, on Alexander's direction to continue the Helm lane)*",
   "category": "DONE",
   "status": "DONE \u2014 `recoveries/helm-behavioural-guard.md` (10,232 B), Merlin, 2026-10-12T06:5x\u201307:1xZ, this host.",
   "status_line": 18,
   "found": true,
   "chars": 117,
   "status_text": "DONE \u2014 `recoveries/helm-behavioural-guard.md` (10,232 B), Merlin, 2026-10-12T06:5x\u201307:1xZ, this host."
  },
  {
   "q": 38,
   "header_line": 5135,
   "header": "## Q38 \u2014 The behavioural destination guard *(Helm lane; opened 2026-10-12 by Merlin \u2014 Q36's candidate 2, on Alexander's direction to continue the Helm lane; **direction unrecorded in this repo \u2014 Testimony only**)*",
   "category": "FALSIFIED",
   "status": "the deliverable is verified and the item is DONE, and its protective claim is FALSIFIED. It is not adoptable as it stands.",
   "status_line": 2,
   "found": true,
   "chars": 16,
   "status_text": "the deliverable is verified and the item is DONE, and its protective claim is FALSIFIED. It is not adoptable as it stands."
  },
  {
   "q": 39,
   "header_line": 5151,
   "header": "## Q39 \u2014 The Q38 guard's admission admits a writer, and its legs run the unrewritten subject *(Helm lane; opened 2026-10-12 by the pipe, per Q7's never-dry obligation \u2014 Q38 is closed and verified and its protective claim is falsified, so the executable set is not empty)*",
   "category": "DONE",
   "status": "DONE \u2014 `recoveries/helm-destination-guard-fix.md` (12,253 B), Merlin, 2026-10-12, scratch tree `/root/crucible/q39/`. Fixed gate `9b09f328\u2026` (1,412 lines / 77,704 B, +309/\u221238 against Q38's `74aba348\u2026`); subject collector byte-identical at `4e45021d\u2026`; nothing deployed, no `cp` into `/root/.helm/bin/`, live snapshot `aa842b0f\u2026` delta 0 across every run.",
   "status_line": 8,
   "found": true,
   "chars": 53,
   "status_text": "DONE \u2014 `recoveries/helm-destination-guard-fix.md` (12,253 B), Merlin, 2026-10-12, scratch tree `/root/crucible/q39/`. Fixed gate `9b09f328\u2026` (1,412 lines / 77,704 B, +309/\u221238 against Q38's `74aba348\u2026`); subject collector byte-identical at `4e45021d\u2026`; nothing deployed, no `cp` into `/root/.helm/bin/`, live snapshot `aa842b0f\u2026` delta 0 across every run."
  },
  {
   "q": 40,
   "header_line": 5217,
   "header": "## Q40 \u2014 the deployed gate admits all five negatives, and has no admission path at all *(Helm lane; opened 2026-10-12 by Merlin, discharging the Q39 closure's C26)*",
   "category": "OPEN",
   "status": "DONE \u2014 `recoveries/helm-deployed-gate-admission.md` (5,633 B / sha256\n`5bdd2e7503cced8eee5b31a0256500aaa8eda9f8e3adbb80d3702eeb5e8df61a`), Merlin,\n2026-10-12. Method `/root/troupe-verify/q40/q40-deployed-gate-negatives.py`\n(written from the gates' source); evidence `/root/troupe-verify/q40/DEPLOYED-GATE-NEGATIVES.json`;\nrun transcript `/root/troupe-verify/q40/run.out`.\n\n- C26 reproduces exactly. Deployed gate \u00d7 all five fixtures (n1-incident-shape,\n  n2-traceback, n3-decoy, n4-comment-only, n5-live-literal): rc 0, stdout 7,488 B,\n  `helm-selftest: 119 passed, 0 failed`, `VERDICT: ALL GATES PASS`, stderr 0 B,\n  0.5 s each, no fixture file touched, live delta 0. Live snapshot unchanged\n  throughout: 14,039 B / `aa842b0fd88037f83115b4a54d617f27666f4de06ef84f9a64c8fd0a5f04656d`\n  / mtime_ns `1791479579475780303` \u2014 delta 0 across all 15 invocations plus the\n  green control.\n- The mechanism is stronger than C26 stated. `grep -c HELM_COLLECTOR\n  /root/.helm/bin/helm-selftest.py` \u2192 0. The deployed gate imports its subject\n  at module scope from a hard-coded path (`helm-selftest.py:39`,\n  `spec_from_file_location(\"helm_collect\", Path(\"/root/.helm/bin/helm-collect.py\"))`),\n  so `HELM_COLLECTOR` never reaches it. The five green rows are not the gate\n  approving bad collectors \u2014 it never loaded them. The exposure is that the\n  deployed gate has no subject-selection path at all, so there is nothing for\n  Q34\u2013Q39's admission machinery to guard, and a bad collector dropped into\n  `/root/.helm/bin/` would fail the suite uncontrolled (a module-scope\n  `AttributeError`, not a dated refusal) or run with no destination rule anywhere\n  in the production path.\n- The fixed gates discriminate, re-measured in the same run. Q38 `74aba348\u2026`:\n  n1 rc 0 (admitted \u2014 C22's hole, writes the fixture's `n1-dest/`), n2 rc 1\n  (admitted then crashed), n3/n4/n5 rc 2 refused (n3's probe writes the decoy's\n  real destination \u2014 the containment failure). Q39 `9b09f328\u2026`: all five rc 2,\n  stdout 0 B, no fixture file touched, live delta 0. Positive control, this run,\n  `HELM_COLLECTOR=/root/crucible/q39/helm-collect.py python3\n  /root/crucible/q39/helm-selftest.py`: exit 0, `164 passed, 0 failed`,\n  `VERDICT: ALL GATES PASS`, `Q39: 17 legs watched \u2026 delta 0 on each`,\n  `Q39 OK: \u2026 (probe rc=2, sentinel written=False \u2026 live delta 0)` \u2014 log\n  `/root/troupe-verify/q40/q39-green.out`, sha256\n  `7fd767b72e811f46466b4acd4f214ab27e56c33012629a7bcd5fbbbc2567daa4`. No probe dirs\n  left (`ls /root/crucible | grep -c helm-q39-` \u2192 0).\n- Nothing touched. `/root/.helm/bin/` unmoved (`ee0b36a82f23fcf3\u2026` /\n  `7ed1bca8f9da624f\u2026` / `5c67473d89283c3d\u2026`), no `cp`, nothing deployed;\n  `decisions/` and `inbox/` untouched.\n- Consequence for the standing adoption ask (Alexander, \u00a74): the `cp` of\n  collector `4e45021d\u2026` + gate `9b09f328\u2026` is the only thing that puts any of\n  Q31\u2013Q39's protection into production, and this run shows the reason is stronger\n  than the admission question: the shipped gate has no subject-selection path at\n  all. Q39's refusal behaviour is intact and the fixed pair discriminates on every\n  class. Adoption stays Alexander's; nothing was executed from this side.",
   "status_line": 13,
   "found": true,
   "chars": 59,
   "status_text": "DONE \u2014 `recoveries/helm-deployed-gate-admission.md` (5,633 B / sha256\n`5bdd2e7503cced8eee5b31a0256500aaa8eda9f8e3adbb80d3702eeb5e8df61a`), Merlin,\n2026-10-12. Method `/root/troupe-verify/q40/q40-deployed-gate-negatives.py`\n(written from the gates' source); evidence `/root/troupe-verify/q40/DEPLOYED-GATE-NEGATIVES.json`;\nrun transcript `/root/troupe-verify/q40/run.out`.\n\n- C26 reproduces exactly. Deployed gate \u00d7 all five fixtures (n1-incident-shape,\n  n2-traceback, n3-decoy, n4-comment-only, n5-live-literal): rc 0, stdout 7,488 B,\n  `helm-selftest: 119 passed, 0 failed`, `VERDICT: ALL GATES PASS`, stderr 0 B,\n  0.5 s each, no fixture file touched, live delta 0. Live snapshot unchanged\n  throughout: 14,039 B / `aa842b0fd88037f83115b4a54d617f27666f4de06ef84f9a64c8fd0a5f04656d`\n  / mtime_ns `1791479579475780303` \u2014 delta 0 across all 15 invocations plus the\n  green control.\n- The mechanism is stronger than C26 stated. `grep -c HELM_COLLECTOR\n  /root/.helm/bin/helm-selftest.py` \u2192 0. The deployed gate imports its subject\n  at module scope from a hard-coded path (`helm-selftest.py:39`,\n  `spec_from_file_location(\"helm_collect\", Path(\"/root/.helm/bin/helm-collect.py\"))`),\n  so `HELM_COLLECTOR` never reaches it. The five green rows are not the gate\n  approving bad collectors \u2014 it never loaded them. The exposure is that the\n  deployed gate has no subject-selection path at all, so there is nothing for\n  Q34\u2013Q39's admission machinery to guard, and a bad collector dropped into\n  `/root/.helm/bin/` would fail the suite uncontrolled (a module-scope\n  `AttributeError`, not a dated refusal) or run with no destination rule anywhere\n  in the production path.\n- The fixed gates discriminate, re-measured in the same run. Q38 `74aba348\u2026`:\n  n1 rc 0 (admitted \u2014 C22's hole, writes the fixture's `n1-dest/`), n2 rc 1\n  (admitted then crashed), n3/n4/n5 rc 2 refused (n3's probe writes the decoy's\n  real destination \u2014 the containment failure). Q39 `9b09f328\u2026`: all five rc 2,\n  stdout 0 B, no fixture file touched, live delta 0. Positive control, this run,\n  `HELM_COLLECTOR=/root/crucible/q39/helm-collect.py python3\n  /root/crucible/q39/helm-selftest.py`: exit 0, `164 passed, 0 failed`,\n  `VERDICT: ALL GATES PASS`, `Q39: 17 legs watched \u2026 delta 0 on each`,\n  `Q39 OK: \u2026 (probe rc=2, sentinel written=False \u2026 live delta 0)` \u2014 log\n  `/root/troupe-verify/q40/q39-green.out`, sha256\n  `7fd767b72e811f46466b4acd4f214ab27e56c33012629a7bcd5fbbbc2567daa4`. No probe dirs\n  left (`ls /root/crucible | grep -c helm-q39-` \u2192 0).\n- Nothing touched. `/root/.helm/bin/` unmoved (`ee0b36a82f23fcf3\u2026` /\n  `7ed1bca8f9da624f\u2026` / `5c67473d89283c3d\u2026`), no `cp`, nothing deployed;\n  `decisions/` and `inbox/` untouched.\n- Consequence for the standing adoption ask (Alexander, \u00a74): the `cp` of\n  collector `4e45021d\u2026` + gate `9b09f328\u2026` is the only thing that puts any of\n  Q31\u2013Q39's protection into production, and this run shows the reason is stronger\n  than the admission question: the shipped gate has no subject-selection path at\n  all. Q39's refusal behaviour is intact and the fixed pair discriminates on every\n  class. Adoption stays Alexander's; nothing was executed from this side."
  },
  {
   "q": 37,
   "header_line": 5276,
   "header": "## Q37 \u2014 claimed by this pipe; first increment landed (the v1.3 census)",
   "category": "OPEN",
   "status": "OPEN and claimed by the pipe (Merlin's \u00a7Next 2 read it correctly; it is this lane's tooling). Landed this tick:",
   "status_line": 2,
   "found": true,
   "chars": 827,
   "status_text": "OPEN and claimed by the pipe (Merlin's \u00a7Next 2 read it correctly; it is this lane's tooling). Landed this tick:"
  },
  {
   "q": 43,
   "header_line": 6103,
   "header": "## Q43 \u2014 The legs run the rewritten subject: prevention, not detect-and-restore *(Helm lane; opened 2026-10-12 by Merlin, per the Q39 closure's own recommendation \u2014 \"open the stronger form (the legs against a rewritten copy) as the Helm lane's next item\")*",
   "category": "OPEN",
   "status": "DONE \u2014 `recoveries/helm-leg-sandbox.md` (13,561 B), Merlin, 2026-10-12. Scratch tree `/root/crucible/q43/`; nothing deployed, no `cp` into `/root/.helm/bin/`, `decisions/` and `inbox/` untouched.",
   "status_line": 22,
   "found": true,
   "chars": 38,
   "status_text": "DONE \u2014 `recoveries/helm-leg-sandbox.md` (13,561 B), Merlin, 2026-10-12. Scratch tree `/root/crucible/q43/`; nothing deployed, no `cp` into `/root/.helm/bin/`, `decisions/` and `inbox/` untouched."
  },
  {
   "q": 44,
   "header_line": 6162,
   "header": "## Q44 \u2014 The pin class: redirect every constant composed from the live data root, not only `SNAPSHOT_PATH` *(Helm lane; opened 2026-10-12 by the pipe, per Q43's own closing sentence \u2014 \"extend the redirect beyond `SNAPSHOT_PATH` to every constant composed from the live data root, which is what would close the `--pin` class structurally instead of by argv rule\")*",
   "category": "VERIFIED-CLOSED",
   "status": "DONE 2026-10-12 \u2014 `recoveries/helm-root-redirect.md` (Merlin, Helm lane); the closure block is at the foot\nof this file. The residual this targets was measured, not hypothesised\n(`/root/crucible/q43z/timmy_verify_q43.py`, `replies/2026-10-12-to-merlin-27.md` \u00a75). Alexander's `cp` decision was\nnot a precondition: the pair stayed undeployed and this unit ran in scratch. With Q43 closed and Q44 closed, the\nHelm lane's executable set is empty again.\n\nQ43 (leg sandbox) verified here; the disk went 7.0 GB \u2192 46 GB because the music tree and the live swap were MOVED, not deleted. 2026-10-12 18:45Z (control plane).",
   "status_line": 22,
   "found": true,
   "chars": 544,
   "status_text": "DONE 2026-10-12 \u2014 `recoveries/helm-root-redirect.md` (Merlin, Helm lane); the closure block is at the foot\nof this file. The residual this targets was measured, not hypothesised\n(`/root/crucible/q43z/timmy_verify_q43.py`, `replies/2026-10-12-to-merlin-27.md` \u00a75). Alexander's `cp` decision was\nnot a precondition: the pair stayed undeployed and this unit ran in scratch. With Q43 closed and Q44 closed, the\nHelm lane's executable set is empty again.\n\nQ43 (leg sandbox) verified here; the disk went 7.0 GB \u2192 46 GB because the music tree and the live swap were MOVED, not deleted. 2026-10-12 18:45Z (control plane)."
  },
  {
   "q": 48,
   "header_line": 6706,
   "header": "## Q48 \u2014 The runtime-resolution redirect: close the class Q45's literals cannot see",
   "category": "CLOSED",
   "status": "DONE 2026-10-13 \u2014 `recoveries/helm-runtime-redirect.md` (Merlin, Helm lane), scratch tree\n`/root/crucible/q48/`. Two mechanisms (environment redirect, argv redirect scoped to the write surface), two\nnew checks (169 \u2192 171), green 5/5; the class measured with prevention separated from detection; one\ndisclosed live-held incident caused, restored and recorded; the residual named as the gate's own leg set.",
   "status_line": 12,
   "found": true,
   "chars": 120,
   "status_text": "DONE 2026-10-13 \u2014 `recoveries/helm-runtime-redirect.md` (Merlin, Helm lane), scratch tree\n`/root/crucible/q48/`. Two mechanisms (environment redirect, argv redirect scoped to the write surface), two\nnew checks (169 \u2192 171), green 5/5; the class measured with prevention separated from detection; one\ndisclosed live-held incident caused, restored and recorded; the residual named as the gate's own leg set."
  },
  {
   "q": 49,
   "header_line": 6826,
   "header": "## Q49 \u2014 The runtime-resolved root's live write path: name it, reproduce it, then close it",
   "category": "UNCLAIMED",
   "status": "open and unclaimed. Opened by the pipe 2026-10-13",
   "status_line": 21,
   "found": true,
   "chars": 768,
   "status_text": "open and unclaimed. Opened by the pipe 2026-10-13"
  }
 ]
}