c4f68678ea3cc55e4fa2ca0e8a7e41bb1bbbbde3
105
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 zephyrus-sparkborn
|
0bd57079aa | Q60 census addendum 2026-10-26: reply-100 corrections (self-quotation, occurrence/distinct, 5 external recoveries) + enforcement check runs | ||
|
zephyrus-sparkborn
|
cc47f5e40c | Q60: truncated-identifier census, 16 tokens (Zeph lane) | ||
 Merlin
|
b280105259 |
Q45S12 (Helm lane): Run 40 -- the byte-stability cell corrected by its own artifacts. The control plane's 17:41Z tick returned one correction against this lane: recoveries/helm-pin-hash-convention.md:85 paired one run's bytes with another run's diff ("rc 0 / 195 / 0; the two raw stdouts are 17,027 B each and differ on exactly 4 lines"). VERIFIED AGAINST THE ARTIFACTS, not accepted from the reply: the only raw stdout pair on disk, out/R39-STABILITY-{1,2}.txt, is 17318 B each, BOTH rc 1 / 194 passed / 1 failed (stdout sha256 b93549cf1ef860bcc52fca11556a0c9abde0a86675136abd9d83bfcf6ca8344a / 0dd6922a53a52d207c5a29f8f51be0a841bbd40312590fe0b2c255d4317a2ca8, both equal to out/R39-STABILITY.json), differing on exactly 4 lines (1, 10, 209, 210), all per-run mkdtemp paths; normalised residual 0, normalised digest 49eb85e9a1461769a1ece37401a500590c8bc2a28208918c72937ad5119376ab. The 17027 B / rc 0 / 195 / 0 figures are the five gate_parity* legs of out/RUN39.json -- arm A gate_parity_render1 379cfc4e0317b758, render2 799e3e21836dc5a3, render2_repeat 88fbede428fb68b8, render3 f8df74cc627a1f19, arm B render1 fc26907c39e24619 -- every one 17027 B / rc 0 / 195 / 0 with distinct digests. No verdict, digest, row or count in sections 1-8 of the record moves; section 4 already stated the stability pair's rc 1 / 194 / 1 correctly. ERRATUM FORM per the lane's correction rule: the Run-39 commit message (28ca8e5) and the queue's Run-39 block carry the same sentence; a commit message cannot be edited and the queue is append-only, so both stand with the new section 9 as the correction. CLAIM CHECK RAN FIRST and reproduced 15 opening records / 12 closed / 3 open (Q37, the career-lane Q53, Mercury's Q53) -- none claimable by this lane, so no queue item was opened or closed; the Run-39 verification's own ask was the only executable unit left. All three appends are append-only (numstat 39/0 + 68/0 + 46/0 = 153 insertions, 0 deletions; anchors unique; pre-images asserted: record 12513 B / 2831a9c293e09afac0d0c70f6af064576f4e3ce53555747640aeee256d9ec4d3, check-in 66369 B / 28779a4130dbd3bec09f0f8dd00a9f5fed3e38c21268778cc0401e09603540e7, queue 1198687 B / ac7d32703b7760d9925a7f2b42b16b928bad5c952a660f2feb3bcdc1b822d07b; trailing newline both ways). Post-append: record 15109 B / b84391af977218c8, check-in 70102 B / 44ec91e0e507fdd1, queue 1201550 B / 17662169a9709e45. NOTHING DEPLOYED: no cp into /root/.helm/bin/, no --deploy, no write to the live document root; live state re-censused unchanged (page 9865 B / 427b7b54c69b18d2270288910fc810732463129f48ec4bdd7dbc75cdb22997ce4, snapshot 14039 B / aa842b0fd88037f83115b4a54d617f27666f4de06ef84f9a64c8fd0a5f04656d, held pin 120 B / 5b6d70716153c3f4bd82045d5d71edf88f793a240ce1275c3dfca5759d0ee297, five deployed bin digests ee0b36a82f23 / 5c67473d8928 / 7ed1bca8f9da / 12570786ba70 / 738699986778 unmoved, grep -c HELM_COLLECTOR /root/.helm/bin/helm-selftest.py = 0 so Q40 stands, /tmp/q31-g8-deploy-* 475, disk 40 G free of 154). No another-party file edited, decisions/ and inbox/ untouched, no secret printed. Merlin <merlin@agents.invalid>.
|
||
|
Merlin
|
28ca8e5a5b | Q45S12 (Helm lane): Run 39 -- the pin/hash convention split closed; the green pill ships green. pin_stackchain hashed curl's stdout read as TEXT (13 CRLFs fold, 217163 wire bytes -> 217119 chars, e40308e5) while G13 row 2 hashes the RAW bytes (c34ae2c2), so after a re-pin the page's green "match" was a claim the gate refused (Run 38: rc 1 / 194 / 1). The pin now hashes the wire -- the convention the gate's rows and any outside verifier already use. TWO FILES CHANGE, THE GATE DOES NOT: collector helm-collect-r39.py 31595 B / 5a99364bd4bbca2b5d7f1c4ff13dba5a1488154b6e363f238e2e265a243b9966 / 750 lines (on 4e45021d 29954 / 720) -- one bytes-mode fetch (the old block fetched the body twice, a race between two curl calls), both digests from the same bytes, manifest_match pin-vs-wire, the pin on the wire, live_body_sha256 kept folded because G6 requires both fields to differ; renderer helm-render-r39.py 23523 B / 117001e839dbbac5fb35c3d1c5f11da461c7e5564049b1aeb5d51a35a7bbfdc6 / 522 lines (on a70998c8 22930 / 514) -- the page's "live body sha256" line publishes the WIRE digest because G13 row 1 compares that published hash against the held pin; gate 833d0827 BYTE UNCHANGED (190330 / 3619 / 145) -- its contract was right, the producer was not. REHEARSED ON TWO SANDBOXES, PREDICTIONS WRITTEN FIRST, 13 OF 14 MET. Arm A (the fix, sandbox bin = a copy of /root/.helm/bin + the payload, every live-path literal the gate names redirected in, the real live pin seeded): collect #1 manifest_match false (wire c34ae2c2 vs held f27326e8); render #1 red drift pill 13849 B / 3dd6125f; gate rc 0 / 195 / 0; --pin writes c34ae2c245117ca73ba5720b2c22b6fab689840070ff68cda7bffe3e723986d4; collect #2 manifest_match true; render #2 GREEN pill, published hash c34ae2c245117ca7 == pin[:16]; GATE ON RENDER #2 rc 0 / 195 / 0 -- the leg Run 38 measured 194/1 on. Drift probe: mutated pin -> collect #3 false -> render #3 red -> gate 195/0, pin restored. ARM B (the control: the shipped collector + renderer, the same gate) REPRODUCES THE BUG: --pin writes the folded digest e40308e573d046d7, collect #2 true, render #2 green, gate rc 1 / 194 / 1, sole failure G13 row 2 (live_sha256=c34ae2c2 held_pin_digest=e40308e5 pin_matches_live_now=False) -- the before/after pair, differing only in the collector. THE OUTSIDE VERIFIER, the point of the alignment: curl -sS --max-time 20 https://www.stackchainmagazine.net/ | sha256sum -> c34ae2c245117ca73ba5720b2c22b6fab689840070ff68cda7bffe3e723986d4 (217163 B): == snapshot live_body_sha256_wire, == held pin, != live_body_sha256. THE ONE MISS is the twin's own artifact: the G11-contract twin (194/1) redirects the pre-G14 renderer path to the sandbox bin renderer -- which IS the payload renderer now -- so G14's discriminator negative leg collapses by construction; Run 38 logged the identical artifact on the identical twin. INCIDENTAL CATCH: the byte-stability re-run after the drift probe (page still the red render, pin restored to live) failed on G13 ROW 3 (unqualified_red_pill=True, live == pin), row 3 firing on a real state transition rather than a constructed cell. Byte-stability: the two acceptance-leg stdouts are 17027 B each, differing on exactly 4 lines, all per-run mkdtemp paths; normalised residual 0, digest 49eb85e9a1461769. LIVE DELTA 0 ACROSS EVERY LEG OF BOTH ARMS: page 9865 / 427b7b54, snapshot 14039 / aa842b0f, held pin 120 / 5b6d7071, five deployed bin digests unmoved; grep -c HELM_COLLECTOR = 0 (Q40 stands, nothing of Q31-Run 39 in production); /tmp/q31-g8-deploy-* 475 before and after; sandboxes 0 of 0. THE ADOPTION ASK, MATERIALLY AMENDED: Run 38 had to prescribe cp WITHOUT a --pin first because a green pill could not ship green while the site serves CRLF; that constraint is gone -- arm A measured the full sequence WITH the re-pin (rc 0 / 195 / 0 on a green page). Sequence, four files in one order: adopt renderer 117001e8 -> adopt collector 5a99364b + gate 833d0827 -> re-collect -> re-render -> deploy; the file list must be re-read at adoption time, never copied from an earlier block. Whether to re-pin at all (accepting today's live body as the drift reference) is a policy choice, not a technical one. Old-convention pins remain readable: a folded-digest pin simply fails manifest_match until a re-pin, which is today's state anyway. NO ITEM CLOSED, NONE OPENED -- the Helm executable set was empty at the start of the run by both lanes' measurement. Deliverable recoveries/helm-pin-hash-convention.md (12513 B). Nothing deployed, no another-party file edited, no secret printed. Merlin <merlin@agents.invalid>. | ||
|
Merlin
|
99493604da | Run 38 (Merlin, Helm lane): the adoption rehearsal -- the section-4 cp performed on a copy (collector 4e45021d, renderer a70998c8, gate 833d0827; adoption_identical_to_payload true), every live-path literal in the gate redirected into the sandbox, and the gate reading a page the payload itself rendered. Result: the prescribed adoption (cp + collect + render + deploy, no --pin) is rc 0 / 195 passed / 0 failed on an honest red drift page (13,847 B / f0097cea3b63d2e6, manifest_match False, held f27326e8 vs live e40308e5/c34ae2c2); a --pin first (pinned e40308e5) flips the pill green and G13 row 2 red (194/1), root cause measured on the live URL with both pipelines in one run -- pin_stackchain hashes curl's stdout read as text (13 CRLFs folded, 217163 B -> 217119 chars, e40308e5) while G13 row 2 hashes raw bytes (c34ae2c2), agree False, so a green pill cannot ship green while the site serves CRLF. G7/G10/G11 contract rows pass on the payload renderer; the G11 twin's second failure is this run's own artifact (the G14 discriminator's negative leg renders the path the twin redirected). Live delta 0 across all ten steps (page 427b7b54, snapshot aa842b0f, pin 5b6d7071, five deployed digests unmoved, HELM_COLLECTOR 0, /tmp q31-g8-deploy 475 before and after). Predictions P1-P8 written before any gate ran: P1 P2 P3 P4 P5 P8 met, P6 P7 not met with causes named. Deliverable recoveries/helm-adoption-rehearsal.md (12,914 B / b31466d2e77451f4). No item closed, none opened -- the executable-unclaimed set was empty at the start of the run. Nothing deployed, no another-party file edited, no secret printed. Merlin <merlin@agents.invalid>. | ||
|
zephyrus-sparkborn
|
57542ac128 | Q42 recompute: addendum 2 (reply-69 tokens, 08-21 s3 denominator closed) | ||
 timmy
|
a28d9df8c9 |
queue: Run 37 (Merlin) -- the claim check re-generated on a corrected instrument: 15 opening records, 12 closed, 3 genuinely open, and the executable-unclaimed set this lane can take measured EMPTY. The queue's own hygiene convention (:8020, 2026-10-13T23:18Z) requires a claim check to read the ledger before taking any item whose opening line reads open or unclaimed; that ledger predates Runs 22-36 and the queue grew ~936,379 -> 1,170,483 B since, so the check was re-generated rather than inherited. Deliverable recoveries/queue-hygiene-census.md (10,123 B / sha256 eb0e1b4f5fa8733fb12eba758d9543a60eb85b8f12f5f7fc79b9908300d2405d); instrument /root/crucible/q66/q66_census6.py (4,388 B / sha256 e340b105dd96955f43a27e285a03f8ae, host-local scratch, six generations 21,845 B, every defect logged not deleted). Result: 15 opening records, 80 closure lines indexed, 12 closed / 3 open; validated against eleven answers read by hand from the queue before the run (Q21 Q24 Q25 Q45 Q46 Q47 Q49 Q50 Q51 Q52 closed, Q53 open) -> 11/11 VALIDATION PASS. Method is the finding: opening records are keyed on their SHAPE, which is what catches Q50/Q51/Q52/Q53 -- their opening records are bullet lines nested inside other sections, not ## headers, so a header walk cannot do this job; closures are item-anchored and searched whole-file because this queue is append-only and a closure lands at the tail. Six generations of instrument defect logged first, four erring in the dangerous direction: v1 walked only ## headers and matched the word open (missed Q50-Q53, false-flagged Q5/Q7/Q14); v2 caught Q7 continuation notes as openings; v3 cut its region at a --- rule (false OPEN for Q25 closed :2985 and Q49 closed :6952) and counted "**Done means:**" as a closure word (false CLOSED for Q53); v4 did not anchor closures to the item (Q53 closed off an unrelated G11 block at :8839); v5 scoped the closure search to the region before the next opening record so Q52 read OPEN though "**Q52 -- DONE at 4010b96" sits at :8517. Every defect was the instrument's, not the queue's. The three genuinely open and why none is this lane's: Q53 :8530 Mercury's (R5-a/R5-b in replies/2026-10-14-to-mercury-05.md, the pipe's own tick at :8939 states it open); Q37 :5278 the pipe's tooling ("Q37 stays open there", the residual a per-tick discipline plus a push identity it names an access decision, not a script); the career-lane apply queue :7303 Alexander's ("seven decisions and one rate figure are Alexander's"). Beside those the standing human-gated set: the section 4 adoption cp, the manifest_match pin stale since 2026-10-08, Q13, Q9, Q19, Q42. Q7 measured: no item opened -- an item invented to fill an empty set would be invented work, and the Helm lane's next unit remains the cp, a decision not a task. Two citation defects found in the queue's own record: (a) :7323 reads "**Q51 -- DONE at e4967da9...**" which parses as a commit SHA, but git cat-file -t e4967da9 -> "Not a valid object name" and sha256sum /root/crucible/q51/helm-selftest-q51.py -> e4967da9bdc45378... -- it is the GATE FILE's digest, and the closure commit is 57d8e6b (2026-10-13T13:40:02Z Merlin) which :7384 already carries correctly; (b) grep -c 'Status: open and unclaimed' -> 3 at :2264 :2684 :6847, all closed, reproducing the pipe's own correction at :8018-:8020. Closure revisions verified against git not prose: a9f23a6 de74527 0e65dfb 4c6cd50 57d8e6b 4010b96 eec3ff3, seven of seven resolve. Live state delta 0 (clock 2026-10-15T10:57:48Z): snapshot 14,039 B / aa842b0fd88037f83115b4a5... / mtime_ns 1791479579475780303; held pin 120 B / 5b6d70716153c3f4bd82045d... / mtime_ns 1791478687099553071; deployed /root/.helm/bin/ five digests unmoved (ee0b36a82f23fcf3 5c67473d89283c3d 7ed1bca8f9da624f 12570786ba703787 7386999867789694), grep -c HELM_COLLECTOR = 0 so Q40 stands; /tmp/q31-g8-deploy-* 475 dirs, newest cfkvskma mtime 2026-10-15 08:53:29.994355542Z = Run 36's last gate run, so no new directory since -- a delta-0 reading on the leak corroborating the candidate gate's Edit B; disk 41 G free of 154 G. One correction to my own records logged: the "sandboxes 0" line is off by one -- ls -d /root/crucible/*/sandbox* -> 2, of which q65/sandbox_probe.py is a script and q43z/sandbox-mine is a Run-13 leftover (32 K, data/snapshot.json, mtime 2026-10-12 18:39); harmless, in scratch, and it makes 0 wrong so it is recorded not restated. Append-only asserted structurally on both files: queue 1,170,483 -> 1,175,960 B (+5,477, 9,533 -> 9,602 lines) and check-in 43,489 -> 50,177 B (+6,688, 693 -> 781 lines), each child blob beginning with the parent's exact bytes, so no line citation shifts. Nothing deployed, no cp into /root/.helm/bin/, decisions/ and inbox/ untouched, no another-party file edited, no secret printed. Merlin <merlin@agents.invalid>, author=merlin.
|
||
|
Merlin
|
be55b9542c |
G14 (Helm lane): the live-body-sha line carries its own clock, and the deploy sandbox that never left
Run 36. The unit is the residual Run 35's own record named and left open: the
page's "live body sha256" line is a present-tense label on the frozen pin
f27326e8 (pinned 2026-10-08T16:58:07.100Z) while the live body reads
c34ae2c2 (200 / 217,163 B), and no gate read it. The obvious predicate
(("live body sha256" not in text) or ("as of " in text)) is strictly weaker
than G10 and was falsified before it shipped (q65/probe_r36.py ->
out/R36-PROBE.json); the distinguishing cell is real -- the G11 renderer
306d4bee, the lane's current adoption payload, at the stale clock emits
11819 B / 951a8a7645fe on which G10, G12 and G13 row 1 all PASS while its
hash line is unqualified. Fix: the hash line's own div carries
"as of OBS . AGE ago . not re-checked since" (renderer a70998c8592a03cd,
22930 B); gate helm-selftest-q65.py 190330 B / 3619 lines / 145 check(
registrations / 833d08275977054a on 6a887f42 at five asserted anchors
(+7578 B / +155 lines / +3 registrations). Matrix (run_matrix_r36.py ->
out/R36-GATE.json, prediction stated before the run): shipped rc 1 / 192/3
(G10 deployed-page, G13 row 2 live, G14 row 1), byte-identical on rerun
after sandbox normalisation (07c1c58d, residual 0); twinI (g14-stale) rc 0 /
195/0 ALL GATES PASS; twinJ (g11-stale, the adoption payload) rc 1 / 194/1,
G14 row 1 only; control-g (q64 base, twinJ repoints) rc 0 / 192/0 -- the
hole measured: the adoption payload passes every gate the lane has today.
twinK's miss is a finding: predicted rc 0 / 195/0, measured rc 1 / 194/1
(G13 row 2) -- a fresh clock on the frozen manifest_match is still caught,
so the renderer alone does not make the page passable and re-collect ->
re-render -> deploy is load-bearing. Also fixed in the same build: the
Q31/G8 --deploy leg's mkdtemp was never removed (+1 leaked
/tmp/q31-g8-deploy-* per gate run, 474 on /tmp at the final census); the
cleanup lands after the two G8 checks that read it (the first form, in the
finally, turned both rows red -- measured shipped 190/5, twinI 193/2), and
post-fix delta is 0 on all five q65 legs while control-g still leaks.
Live state delta 0 across all seven legs (page 9865 B / 427b7b54c69b18d2,
snapshot 14039 B / aa842b0fd88037f8, pin 120 B / 5b6d70716153c3f4);
deployed bin untouched, grep -c HELM_COLLECTOR = 0 so Q40 stands and none
of Q31-G14 is in production; disk 41 G free of 154. Adoption, five files in
one order: renderer a70998c8 -> collector 4e45021d + gate 833d0827 ->
re-collect -> re-render -> deploy; acceptance rc 0 / 195 / 0 ALL GATES PASS
(twinI's shape), demonstrated a third time. Reply 60's correction
discharged: pin_stackchain is helm-collect.py:664, not 647-662. Nothing
deployed, no another-party file edited, decisions/ and inbox/ untouched,
no secret printed. No item closed, none opened. Merlin <merlin@agents.invalid>.
|
||
|
Merlin
|
0b783b6770 |
G13 in both directions (Helm lane): row 1's catch demonstrated, and the
false red no row could see Run 34 closed G13 with one stated open limit -- "Row 1 is green on all six cells today, so it has never fired ... not a demonstrated catch" -- and Run 35 discharges it, finding the second limit: the pill's truth was checked in one direction only. Ground truth measured this run: live body (the snapshot's own URL) HTTP 200 / 217,163 B / c34ae2c245117ca7 against a held pin of f27326e8b13d1dec (120 B / 5b6d7071), so pin_matches_live_now is false; the snapshot's live_body_sha256 equals the pin and its observed_at is 2026-10-08T17:12:59.458Z, so the page's line "live body sha256 f27326e8b13d1dec..." is a present-tense claim of a six-day-old frozen value -- the pill's defect class, one line below it, read by no gate. Finding 1 -- row 1's catch is real, and it is the middle of the lane's own adoption sequence: helm-collect.py:647-662 (pin_stackchain) writes the held pin from the live body and exits without rendering, so re-pin -> page not yet re-rendered is reachable by the collector's own --pin. twinE (only _g13_pin repointed at the live body's hash): row 1 FAIL, row 2 PASS -- 190/2 with the failing G13 row moved from row 2 to row 1. Finding 2 -- the hole between the two rows: row 2's predicate passes whenever the green pill is absent, so a "drift" claim is unverifiable by construction. The falsered cell under the shipped gate: control-g rc 0 / 191 passed / 0 failed / ALL GATES PASS. A false drift sails through the gate that exists to check the pill's truth. The fix -- G13 row 3: a red pill must also be confirmed by a fresh fetch (the live body must not match the pin). Offline, measured with a dead proxy: rc 1, 191/1, sole failure row 3, fetch_error=URLError(ConnectionRefusedError(111,...)). The three rows are transitively closed for the pill's class -- page-published vs pin and pin vs live covers page vs live -- so no fourth row is owed. Gate: base 94f9b362 (180,772 B / 3,432 lines / 141 registrations) -> shipped helm-selftest-q64.py 182,752 B / 3,464 lines / 142 registrations / 6a887f42754a8d96a2e28e7f24df072a75c0820776a25a650bf414274ada990d (+1,980 B / +32 lines / +1 registration), four asserted anchors, four twins and one control each one to four asserted lines different. Matrix, prediction stated before the run: shipped rc 1 / 190/2 (G10 deployed-page, G13 row 2 live) twice, byte-identical after normalisation; twinE 190/2; twinF rc 0 / 192/0 / ALL GATES PASS -- the honest remediated end state, and the SECOND configuration this gate has ever passed (twinC was the first); twinG 191/1, row 3 only; twinH 192/0, a true drift claim is not refused; control-g 191/0, the hole. The twinG/control-g pair isolates row 3 and nothing else. Live delta 0 across all seven legs (bytes + sha256 + mtime_ns): page 9,865 B / 427b7b54c69b18d2, snapshot 14,039 B / aa842b0fd88037f8, held pin 120 B / 5b6d70716153c3f4; deployed bin untouched and grep -c HELM_COLLECTOR = 0 so Q40 stands; sandboxes 0/0/0; disk 41 G free of 154. Adoption is four files in one order: renderer 306d4bee -> collector 4e45021d + gate 6a887f42 -> re-collect -> re-render -> deploy, acceptance criterion rc 0 / 192 / 0 / ALL GATES PASS (twinF's shape, demonstrated twice), with the re-collect load-bearing twice: G13's live row stays red until a collect recomputes manifest_match, and Finding 1 shows the re-pin inside a collect can leave the page and the pin disagreeing until the re-render lands. Four defects of mine logged first in the record's section 8: my twinE prediction named two failures while printing 189/3 (the row-level prediction was met exactly); the first cell set left observed_at at the 2026-10-08 stamp so twinF was the stale cell and came back red on G12; the runner's first run died on its own set-in-JSON bug before writing the artifact; and the runner's docstring still carries the original prediction, because a prediction edited after the run is not a prediction. Nothing deployed, no another-party file edited, decisions/ and inbox/ untouched, no secret printed. No queue item closed, none opened. Merlin <merlin@agents.invalid>. |
||
|
Merlin
|
420c826382 |
G13 (Helm lane): the pin pill against ground truth -- G10's predicate had no
fresh cell, and no gate asked whether the pill was true Two findings, measured on six reachable cells of the pill x qualifier pair (q63/make_cells.py -> R34-CELLS.json), five of them real renders of the real renderers on the real snapshot and one constructed and labelled as such: 1. G10's predicate (helm-selftest-q62.py:2782) demands both "not re-checked since" and "as of ", but helm-render-plain.py:329 appends the disclaimer only when site_fresh != "FRESH" -- so the honest fresh generation is refused and the end state of G10's own prescribed remedy (re-collect -> re-render -> deploy) is red exactly like today's unfixed page. A red that cannot tell a fixed page from a broken one is not a remediation signal. The pair is the evidence: base gate with the fresh cell as its subject 187/1 with G10's row FAIL (control-q62-freshcell.py, c05dd15f), new gate on the same body same repoint 190/1 with G10's row PASS (twinD, ef9980cc). The fix splits the predicate into its two halves and reads freshness from the age the page's own qualifier states, against the collector's own 3600 s threshold. 2. No gate asked whether the pill was TRUE, and G11 does not close it: the fresh cells carry an unqualified green "match" beside a fresh-looking clock from BOTH the production renderer and the G11-patched one, while a fresh fetch of the snapshot's own URL returns HTTP 200 / 217,163 B / c34ae2c245117ca7 against a held pin of f27326e8b13d1dec -- so pin_matches_live_now is false. G13 is the guard: offline, the pill's colour must agree with the held pin against the live-body hash the page publishes; live, a fresh fetch must confirm an unqualified green pill (red today, and that red is the finding); plus a read-only row. Row 2 subsumes G12 on one cell and adds three G12 cannot see -- stated in the record, not left for a reader to find. Gate: base 4b18329c (171,979 B / 3,256 lines / 138 registrations) -> shipped helm-selftest-q63.py 180,772 B / 3,432 lines / 141 registrations / 94f9b3625e5791a724afe479315f5a49d3244c5e183cad8001ec6185e1c3f240 (+8,793 B / +176 lines / +3 registrations); four twins and one control each one to three asserted lines different. Subject 4e45021d80395d3f / 29,954 B throughout. Matrix, prediction stated before the run and met exactly: shipped 189/2 twice, twinA 188/3, twinB 190/1, twinD 190/1, control 187/1, and twinC rc 0 / 191/0 / ALL GATES PASS -- the honest remediated state, the only configuration this gate has ever been able to pass, which gives the remediation an acceptance criterion it did not have before. Live delta 0 across all seven legs: page 9,865 B / 427b7b54c69b18d2, snapshot 14,039 B / aa842b0fd88037f8, held pin 120 B / 5b6d70716153c3f4; deployed bin untouched and grep -c HELM_COLLECTOR = 0 so Q40 stands; sandboxes 0/0; disk 41 G free of 154. Nothing deployed, no another-party file edited, decisions/ and inbox/ untouched, no secret printed. Adoption is now four files in one order: renderer 306d4bee -> collector 4e45021d + gate 94f9b362 -> re-collect -> re-render -> deploy, with the re-collect load-bearing because G13's live row stays red until a collect recomputes manifest_match against the live body. Four defects of mine logged first in the record's section 8: the first probe fetched the portfolio instead of the pin's subject; the first normaliser missed this host's TMPDIR-based mkdtemp; the first G13 block referenced four names it had not imported; and twinC's third repoint silently did not apply until an assertion caught it. No queue item opened. Merlin <merlin@agents.invalid>. |
||
|
Merlin
|
63158803e8 |
G12 (Helm lane): the deployed page's pin pill -- the half of the cell no gate read
grep 'held copy' over the shipped gate 125754b270bf (161122 B / 3053 L / 135
regs) returns three hits (:2841 G10's negative literal, :2882 a comment, :2893
G11's constant) and NONE is read off the deployed path, so G11's pill rule was
guarded on scratch renders only. New gate helm-selftest-q62.py 171979 B / 3256 L
/ 138 regs / sha256 4b18329c7437bec4c5c05be86ddd8376a7396eda9c97739410b1ab5952e4d270
on that base, twin 0fc58aabfb8d9345 differing on exactly one asserted line
(3073, _g12_deployed repointed at the production renderer's own stale output).
My first predicate was falsified by measurement before it shipped: the obvious
rule ("held copy" present implies "as of" present) is REDUNDANT with G10, since
G12-fail implies "as of" absent and G10-fail is "not re-checked since absent OR
as of absent", so every body it refused G10 already refused. Corrected rule is a
complement, not a duplicate: G10 owns the MISSING clock (today's page, G10 red,
G12 correctly green); G12 owns the INCOHERENT pair (green pill AND a staleness
disclaimer, which G10 passes because both its strings are present).
The discriminator runs on an artifact production would deploy, not a string I
built: helm-render-plain.py is byte-identical to /root/.helm/bin/helm-render.py
(21766 B / 5c67473d89283c3d) and at --as-of 2026-10-14T16:00:00.000Z emits
11806 B / 3f48643d8e7bac77 carrying the green pill, "as of" x1 and
"not re-checked since" x1 -- G10 passes it, G12 refuses it.
Prediction stated before the run and met exactly: shipped rc 1, 187 passed /
1 failed (sole failure G10's deployed-page row), twice at 16212 B each; twin
rc 1, 186 passed / 2 failed at 16583 B, adding G12 row 1. live_moved {} and
sandboxes [] on all three legs. Byte-stability measured: G12 rows identical
across both shipped runs, stdout identical after sandbox normalisation with
residual 0, normalised sha256 7a080e1616fb20e3.
Two defects of mine logged first: the first predicate's redundancy (measured
before shipping), and the runner's stdout normaliser matching (helm-legs-|
/tmp/tmp) while this host's TMPDIR is /root/.hermes/profiles/merlin/cache/
scratch, so it reported residual 2 with no characterisation -- the two lines
printed, the pattern corrected, the run re-run; no G12 row depended on it.
Live state delta 0 on bytes+sha256+mtime_ns across every leg: page 9865 B /
427b7b54c69b18d2, snapshot 14039 B / aa842b0fd88037f8, held pin 120 B /
5b6d70716153c3f4. Deployed /root/.helm/bin/ untouched (five digests re-read
plus __pycache__), grep -c HELM_COLLECTOR = 0 so Q40 stands and none of
Q31-Q62 is in production. Sandboxes 0. Repo main at
|
||
|
Merlin
|
f6aca8a3de | Run 32 (Helm lane): reply 57's C1 and C2 discharged -- the render digest's clock corrected (three clocks re-rendered: 20:47:46Z -> 27ea2ad2ccf03f18, 20:49:44Z -> f47262f8f7c00f1f, 23:00:28Z -> 7dbf6c5f3586ec06, all 11811 B, both markers true, +1946 B over the live page, so no finding moves), a second defect of my own found by reading my own parenthetical (the "first run" that never existed), the index nit made precise (index 16, an omitted 0, not index 15), and the Run 31 landing numstat template filled in place (51/0 + 92/0 + 144/0 = 287 insertions, 0 deletions, wc -l unchanged at 1476 so no line citation shifts). Record +7 append, check-in Run 32 block + the fill, queue block, reply 57 to the pipe. Nothing deployed: no cp into /root/.helm/bin/, no --deploy, no write to the live document root; decisions/ and inbox/ untouched; no another-party file edited; no secret printed. Live delta 0 on page/snapshot/pin/all six bin entries across all three renders; grep -c HELM_COLLECTOR on the deployed gate = 0, so Q40 stands and nothing of Q31-Q45S11 is in production. No item closed, none opened. Merlin <merlin@agents.invalid>. | ||
|
Merlin
|
7bcd37364d |
Run 31 (Q45S11): the adoption sequence measured as a set -- the three files
(renderer 306d4bee / collector 4e45021d / gate 125754b270bf) match their stated figures as a bundle, stage byte-identically, the gate is 184/1 on the staged collector (the one failure being G10's deployed-page row), the re-render payload carries both missing markers, and live state is delta 0 around all of it. Record recoveries/helm-adoption-sequence-readiness.md, queue block, check-in Run 31. Nothing deployed, no another-party file edited, decisions/ and inbox/ untouched, no secret printed. Merlin <merlin@agents.invalid>. |
||
|
Merlin
|
defe730677 |
queue+record+checkin+reply 56: reply 55's two-locus citation fix discharged
Both loci that cited out/R29-MEASURE.json are fixed -- the record's own :25 (the primary) and the candidate renderer's comment -- while the artifact sits at /root/crucible/q59/R29-MEASURE.json (5382 B / d6f142c0e7a7acca). One comment line, anchor unique, compile() before the write, the reply-55-verified pre-image preserved byte-exact at q59/helm-render-g11-pre30.py; post-fix renderer 22731 B / 306d4befee7c9874 / 512 lines, -4 B. Comment-only proved by the emitted bytes: fixed stale render 11819 B / 951a8a7645fe7ef4 byte-identical to Run 29's check-stale.html, fixed fresh 11624 B / 1eec213e9e363d36 identical to check-fresh.html and to the plain renderer at the same clock, plain stale control 11806 B / 3f48643d8e7bac77 -- so the pill's +13 B one-span difference is unchanged and the G11 gate's rows 1-3 stand by byte identity (the 161 KB gate was not re-run; the inference is labelled). Live delta 0 on bytes/sha256/mtime_ns for all four live objects across all four invocations; sandboxes 0; HELM_COLLECTOR still 0, so Q40 stands and nothing is in production. Adoption object superseded: renderer 306d4bee (22731 B) before the cp of collector 4e45021d + gate 125754b270bf. Reply 54's three corrections re-measured and upheld (496/512 by wc -l; twin line 2889; match_qualifier :327-330). Nothing deployed, no another-party file edited, decisions/ and inbox/ untouched, no secret printed. |
||
|
Merlin
|
e1fbb14065 |
queue+record+checkin: G11 -- the pin pill that outlived its reading
The held pin f27326e8b13d1dec (pinned 2026-10-08T16:58:07.100Z) no longer matches the live body (200 / 217,163 B / c34ae2c245117ca7), yet the renderer's pill reads the frozen manifest_match field and prints a green 'match' beside 'not re-checked since' in a page whose own verdict pill reads '0 green / 6 not green'. One renderer edit conditions the pill on the reading's freshness (stale -> amber 'match (unverified)'; the fresh branch is byte-identical), and gate G11 adds four checks on Q45S10+G10: 161,122 B / 3,053 lines / 135 registrations. Prediction stated before the run and met: shipped 184/1 (G10's deployed-page row), twin 183/2. Live delta 0 on bytes/sha256/mtime_ns/ctime_ns across all four objects; sandboxes 0/0; HELM_COLLECTOR still 0, so nothing is in production. Nothing deployed, no another-party file edited, no secret printed. |
||
|
zephyrus-sparkborn
|
17394d2430 | Q42: reply-65 corroboration addendum (append-only) | ||
|
Merlin
|
7af50b5bcd |
queue+record: G10 -- the deployed Helm page is a stale generation of the renderer, and the self-test cannot see it
The Helm's pinned site now reads HTTP 200 / 217,163 B / sha256 c34ae2c245117ca7...
while the held pin is f27326e8b13d1dec... pinned 2026-10-08T16:58:07.100Z, so
pin_matches_live_now is false. The deployed page /var/www/alexander-whitestone/helm/index.html
is 9,865 B / sha256 427b7b54c69b18d270288910fc810732463129f48ec4bdd7dbc75cdb22997ce4 / mtime
2026-10-11T08:57:14.017Z and renders a green "match" with no "as of" and no "not re-checked
since". The renderer carrying that fix is mtime 2026-10-11T11:12:43.756Z, 8,129.7 s later, and
the real snapshot through it (--out scratch --as-of 2026-10-14T00:00:00.000Z, rc 0) renders
11,798 B / sha256 f32191223931e74b... carrying "as of 2026-10-08T17:12:59.458Z . 5d 6h 47m ago
. not re-checked since". The fix exists, works, and was never deployed.
Why the self-test was green: helm-selftest.py:420-421 runs the qualifier check on a synthetic
fixture at a pinned clock (hr.SNAPSHOT = fp), and :422-425's "build_page() writes nothing"
only proves build_page did not overwrite production. Neither reads the deployed artifact --
the Q34/Q40 law in a new place: a gate that tests the producer cannot vouch for the artifact
in the document root.
The fix is gate G10, four checks, on Q45S10's c56230e5a075... (147,151 / 2,798 / 127):
helm-selftest-q58.py 153,469 B / sha256 3b98b62fa5c7ea626091f6d0f63566de79818ae414bcffe323dd1ddd53956158
/ 2,916 lines / 131 check(" registrations. Shipped (reads the live page): rc 1, 180 passed /
1 failed, stdout 15,055 B / e8304379529c4c83..., the one FAIL being "the deployed page carries
the manifest qualifier". Twin (the same gate with _g10_deployed repointed at a scratch
current-generation render, ast-asserted): rc 0, 181 passed / 0 failed, ALL GATES PASS, stdout
14,824 B / fe8c8c72825962d9.... Prediction stated before the run and met exactly -- a red row
that cannot go green would prove nothing.
Live state delta 0 across all four invocations on bytes + sha256 + mtime_ns: page 9,865 B /
427b7b54c69b18d2... / 1791709034017837233; snapshot 14,039 B / aa842b0fd880... /
1791479579475780303; held pin 120 B / 5b6d7071... / 1791478687099553071. Sandboxes 0/0 both
ways (shallow glob and recursive rglob). No --deploy anywhere in the G10 block. Deployed bin
unchanged, five digests re-read, grep -c HELM_COLLECTOR = 0 so Q40 stands and G10 is not in
production.
Two shipped runs are both 180/1 at 15,055 B while byte_stable_stdout reads false; the
difference is mkdtemp suffixes in the sandbox path the gate prints. The four G10 rows are
byte-identical across both runs, and normalising the four path patterns gives stdout sha256
1958d8212fa60e44... on both with residual differing lines 0.
Six defects of mine are logged first in the record: two claims in one cell (the first G10
check 3 asserted both the predicate's soundness and the finding, which would have made the
twin 180/1 and hidden the discriminator); a report filter written from memory
(startswith("PASS") never matches the two-space rendering -- the lane's own logged class
reproduced on a fresh artifact); a live-path assertion that fired on G5's read-only check and
then on G10's own comment; byte_stable_stdout: false reported as found with the cause
measured; ast.unparse's single quotes; and pathlib.Path in a gate that imports
from pathlib import Path.
No queue item was opened: the Helm executable set was empty at the start of the run (Q49's
"Status: open and unclaimed" at :6847 is stale -- this file's own hygiene ledger at :8026
records Q49 CLOSED), so the unit taken was the one defect the lane had measured and labelled
but never fixed. Owed to Alexander, both decisions rather than tasks: re-render and re-deploy
the Helm page, and the section-4 adoption cp of collector 4e45021d... + gate 3b98b62fa5c7ea62....
Append-only, prefix asserted on bytes before each write, trailing newline asserted on the
written files: queue 1,060,143 -> 1,065,465 B (+5,322, sha256 9f0a02b429eb7ed5...), check-in
58,536 -> 65,984 B (+7,448, sha256 0af2ecd2aaaee0f0...), record 9,953 B / sha256
bdd5fa1c03586c28.... No another-party file edited, decisions/ and inbox/ untouched, no secret
printed.
|
||
|
Merlin
|
121da2ffad |
helm: Run 26 -- reply 48's four citation corrections discharged (recoveries/helm-discovery-channel-seed.md 18527 -> 22650 B + section 9, check-ins/2026-10-14-merlin.md 45119 -> 50668 B + Run 26). The pipe's verification of Run 25 confirmed all four discharges on its own instrument and returned four citation corrections; each verified and fixed by measurement, none a figure and none moving a conclusion. C1: the lengthened test tree holds three files not two -- helm-selftest-q55.py 143389 / cd43284ff009, helm-selftest-q56.py 147151 / c56230e5a075, and Q34-NULL-EVIDENCE.txt 694 B / sha256 f46b2f3b677552d5f1417b9e3d848bba235cda4711cb1f0447efcde160fb788f, mtime 2026-10-14T08:13:32Z, written between the two re-run cells; the writer is the gate itself at helm-selftest-q56.py:2551 (_q34_dump = Path(__file__).resolve().parent / "Q34-NULL-EVIDENCE.txt"), which is the mechanical explanation for the artifact the pipe observed following the lane across q49/q55/q56; the 0-sandbox census is unaffected. C2: every out/ citation was one level off because Run 25's scripts wrote to the tree root while the prose kept Run 24's out/ form -- fixed by moving all eleven artifact files into out/ with every digest asserted unchanged by the move (out/R26-MANIFEST.json), so out/R25-MEASUREMENTS.json 2405 B / 111b949ffb8c, out/R25-C2.json 1274 / 366593fd8149, out/R25-C2-BYTES.json 1735 / 887578d0a2bf, out/R25-READBACK.json 1126 / 39803e50e668 and out/R25-READBACK-FINAL.json 869 B all resolve; no Run-25 figure was wrong, only the paths. C3: the landing block's read clocks are the artifacts' own fields -- 2026-10-14T08:23:20Z at revision 2b834d4 and 2026-10-14T08:31:19Z at 0c8aef5. C4: the one-byte landing figure is the bc95796 erratum, independently confirmed by reply 48's addendum. Live state unchanged and re-measured: snapshot 14039 / aa842b0fd88037f83115b4a54d617f27666f4de06ef84f9a64c8fd0a5f04656d / mtime_ns 1791479579475780303 / ctime_ns 1791957230760646867; held pin 120 / 5b6d70716153c3f4bd82045d5d71edf88f793a240ce1275c3dfca5759d0ee297 / mtime_ns 1791478687099553071 / ctime_ns 1791957230761646950, both ctime values the Run-24 guard-restore pair so nothing has written either object since; deployed /root/.helm/bin/ untouched with HELM_COLLECTOR count 0 so Q40 stands; sandboxes 0; disk 45 G of 154. Defects of mine logged first: the out/ citation regression, the unlisted "nothing else" sentence, and the clock approximation -- none touches a figure, digest, mechanism or verdict, and the section 4 adoption pair (collector 4e45021d + gate c56230e5a075) is untouched. No new item opened -- the Helm executable set is empty and the next unit is the cp decision, not a task. Nothing deployed, no another-party file edited, decisions/ and inbox/ untouched, no secret printed. Merlin <merlin@agents.invalid>, author=merlin = 86.
|
||
|
Merlin
|
2b834d4ce9 |
helm: Run 25 -- reply 47's corrections discharged by measurement (recoveries/helm-discovery-channel-seed.md 13218 B + record section 8, check-ins/2026-10-14-merlin.md + Run 25, WORK-QUEUE.md + Run 25 block). The pipe's Run-24 verification (a87745a) returned three corrections and one provenance defect; each re-measured from the git blobs and the scratch tree (/root/crucible/q57/), none accepted from the reply, all four confirmed. C1: the landing correction's character/byte pair is mispaired -- the queue at 8ba7c8e is 970138 B / 959834 chars (delta 10304) and at 32ad55b 978022 B / 967603 chars (delta 10419), so "978022 bytes = 959834 characters" pairs 32ad55b's bytes with 8ba7c8e's chars; the printed +7769 is the character delta, the byte delta is +7884; the named cause (len() of a decoded string) is right and the check-in's second pair (29217 B = 28840 chars) is correct as written. C2: stdout byte figures are a function of the gate's own directory length, coefficient measured not assumed -- both gates copied byte-identically into a tree whose full path is +16 per occurrence, the two green cells re-run rc 0 with 176/0 and 177/0 and live delta {}, each stdout grown exactly 96 B = 6 x 16, and len(replaced) - len(orig) = 0 after replacing every occurrence, so the tree path fully explains the growth; portable citations are the verdict, rc, suite counts, digest pair and the +210 B armed-vs-shipped delta (210 in both trees); tree-scoped are the raw 14044/14254; "byte-stable across all five" stands as written. C3: the 406212 B reclaimed has no derivation in its artifact -- out/Q56-CENSUS.json records one removed path with no byte count beside "reclaimed_bytes": 406212, so the sum of recorded per-path bytes is 0; restated, the removal is recorded and the figure is Testimony only. P: both Run-24 commits (32ad55b, 50bf350) are authored Timmy <timmy@stackchain.ai>, the clone's configured identity, because Run 24's append scripts carry no commit step; fixed prospectively -- this commit and every later one carries the Merlin identity, asserted by git log --author=merlin = 83 before the push; published history is not rewritten because both revisions are cited by the queue's Run-24 block and reply 47. Live delta 0 on bytes/sha256/mtime_ns/ctime_ns for both live objects (snapshot 14039 / aa842b0f / mtime_ns 1791479579475780303; held pin 120 / 5b6d7071 / mtime_ns 1791478687099553071); deployed /root/.helm/bin/ untouched with HELM_COLLECTOR count 0 so Q40 stands and none of Q31-Q45S10 is in production; sandboxes 0 in the q57 tree; disk 45 G of 154. No mechanism, digest, line count or verdict moves under any of the four corrections; the section 4 adoption pair (collector 4e45021d + gate c56230e5a075) is untouched. Two defects of mine logged first: the C2 coefficient (12 assumed, 16 measured -- the test tree was nested under q57/) and nothing else. No new item opened -- the Helm executable set is empty and the next Helm unit is the cp decision, not a task. Nothing deployed, no another-party file edited, decisions/ and inbox/ untouched, no secret printed.
|
||
|
timmy
|
32ad55b3ed |
helm: Run 24 -- Q45S10, the discovery channel closed by a seeded sandbox with the artifact as the detector (recoveries/helm-discovery-channel-seed.md 13218 B / 83acffe0). The named residual every record since Q45 carries -- resolve every path the subject declares AT RUNTIME -- is discharged: Q48 closed env and argv, Q52 closed Path.home()/expanduser, Q45S9 closed pwd.getpwuid, and the filesystem SEARCH was the remainder, the one channel no redirect can reach because every redirect keys on how the destination is declared and this class declares nothing. Measured on the shipped gate before the change: collector-discover.py (31076 B / 1f3dae9e, the real collector 4e45021d with the held directory resolved at call time -- walk up from the module's own location, then scan the candidate roots, for the held pin) is admitted on the same terms as every other collector (Q39 OK: probe rc=2, sentinel written=False, live delta 0) and the suite is GREEN: 176 passed / 0 failed, ALL GATES PASS, live delta {} -- the Q45 resolved-destination probe prints HELD_DIR=None so check 2 passes vacuously, i.e. the gate is green on a subject whose held directory is the live one. The interpreter's own verdict: run bare, both fixtures read the LIVE held pin (held_body_sha256 = f27326e8b13d1dec9eb158fe40e5091f79dcaf73b47312c4e7d3958ba1d95d18) and a scratch HOME changes nothing. The escape's write path: shipped x discover --q52-witness -> rc 0 and the live held pin MOVES (5b6d7071 -> 4e98bb00), restored byte-exact by the guard, copy_pin_files_anywhere_in_sandbox [] -- nothing inside the gate sees it. The control: the EAGER form IS reported (FAIL Q45, HELM_HOME=/root/.helm, HELD_DIR=/root/.helm/data/held, 175/1) -- the call-time form is the blind one. The fix, two inserts: (1) the SEED -- the sandbox is given its own .helm/data/held/stackchain-home.html.sha256 carrying a DECOY digest (1e0c8aeefeadd3a1af732b94b2b2b342dfc0a38446714f812305416323ee1ce3), so the copy's walk-up finds the sandbox's own tree first; a decoy, never the live bytes; (2) the ARTIFACT CHECK -- one more subject leg writes a snapshot into the sandbox and the artifact must not carry the live held pin's digest, the only instrument that can see a call-time resolution because the probe is vacuous on it by construction. The pair: gate c56230e5a075c5a12fd2f0d336dcac71c1078cb692a9e6c995780098a051f13e (147151 B / 2798 lines / 127 check( registrations -- 126 + 1) on the Q45S9 gate cd43284ff009 (143389 / 2735 / 126): DIFF-vs-q55.txt = 2 hunks, +63 -0 lines, +3762 -0 B, and 143389 + 3762 = 147151 exactly; disarmed twin 820b7afdff6821a092a64d8a5c24d27f33baaa624534e9f1bfe351ef065a6e4a (147074 / 2796 / 127), the seed's write_text statement cut, 3 lines removed 1 added, 77 B smaller. The matrix, 8 cells under the digest-verified guard: shipped x discover 176/0 silent; shipped x witness the live pin moves (restored); armed x discover 177/0 with the artifact carrying the decoy and NOT the live digest; armed x witness live delta {} with the pin INSIDE the sandbox; disarmed x discover 176/1 -- FAIL Q45S10 with live_digest_in_artifact=True, detection without prevention; disarmed x witness the live pin moves again -- the seed is load-bearing; shipped x eager 175/1 reported; armed x eager 177/0. Green pair x5: rc 0, 177/0, 14254 B each (byte-stable), live delta {}; the shipped gate's control on the real collector reproduces its historical baseline to the byte (176/0 at 14044 B); no pre-existing check moved (176 -> 177 is the one new check). Regressions 11/11: n1-n4 and dep-unparseable -> Q39 rc 2; noparse -> Q46 rc 2; undecodable -> Q47 rc 2; broken_dep -> Q35 rc 2; n5 -> rc 2 (its own destination rule on the redirected sandbox dest); latin1 and bom green 177/0 at 14254 B. Live delta 0 on bytes/sha256/mtime across all 25 invocations (snapshot 14039 / aa842b0f / mtime_ns 1791479579475780303; pin 120 / 5b6d7071 / mtime_ns 1791478687099553071; ctime moved on both by the guard restores, disclosed); deployed /root/.helm/bin/ untouched with HELM_COLLECTOR count 0 so Q40 stands and none of Q31-Q45S10 is in production; sandboxes 0 in the q56 tree and 0 across /root/crucible, 406212 B reclaimed; disk 45 G of 154. Adoption: the section 4 cp is collector 4e45021d + gate c56230e5a075, superseding cd43284ff009 / 78b290ecf2d9 / e4967da9 / a951dbe8 -- Alexander's, unchanged. Six defects of mine logged first in the record, the first being that the initial PEP 562 __getattr__ design was wrong twice over (a global name lookup never consults module __getattr__, and the gate refuses a subject with no SNAPSHOT_PATH = assignment), so the fixture was rebuilt to move only the held channel to call time and the class statement moved with it. Landing evidence: queue 84/0 and check-in 116/0 insertions vs 8ba7c8e, zero deletions, measured by git diff --numstat; the append script's own printed byte deltas are superseded by those numstat figures because the working tree moved under the append (recorded in the check-in). Nothing deployed, no another-party file edited, decisions/ and inbox/ untouched, no secret printed. No new item opened -- the Helm executable set is empty and the next Helm unit is a decision, not a task.
|
||
|
Merlin
|
eec3ff38e7 |
helm: Run 23 -- the record's four numbers corrected and the digests re-verified on disk (armed gate 143385 -> 143389 B, twin 143416 -> 143422 B, twin-armed 31 -> 33 B, insertion block +3020 -> +3024 B / +58 lines, and the differing line's identifier _q45S9_pwd_sites -> _q55_pwd_sites at :435/:442/:451 armed and :435/:451 twin; cause: the Q55 -> Q45S9 rename moved the bytes after the figures were taken and before the digests were computed, so the record paired a post-rename digest with pre-rename bytes). Both digests are unchanged -- armed cd43284ff009d1cceb3aaa6a65b701d1076eaf801e32b705672601b4122b746a, twin 8adad99bdc872ecd09ddea88ae55b5fc55a3886571ffaa5f49a053b52430586d, both 2735 lines / 126 registrations -- so the section 4 adoption cp pair (collector 4e45021d + gate cd43284f) is sound and needs no re-cite. Gate re-run once on the real collector: rc 0, 176 passed / 0 failed, ALL GATES PASS, 14044 B stdout / sha256 585e0e4b0508b565a18ca52cde3c464b9f92673b8fad538a12a33fd8a07131c1 / 1216 B stderr / 12.2 s, PASS Q52 present, live delta {} on bytes/sha256/mtime_ns/ctime_ns for both live objects. Reply 45 section 5.1 closed: the c4addca readback is now durable because readback_r23.py reads /raw/commit/<rev>/<path> -- 6 rows across c4addca and b31c727, all 6 served = git, the record byte-identical at both revisions (14808 / d4c381f7). Deliverables append-only with the anchor count and the trailing newline asserted on the written file: recoveries/helm-pwdir-channel-refusal.md 14808 / d4c381f7 -> 20820 / 8d67248f (+6012 B), checkins/2026-10-14-merlin.md 10499 / eae1c6b2 -> 18265 / 45223797 (+7766 B), WORK-QUEUE.md 957453 / d60d6dee -> 962664 / 972efe4a (+5211 B). One defect of mine logged: run23_verify.py's first Q52 filter used startswith("PASS Q52") and never matched the two-space rendering -- the lane's own logged defect, reproduced on a fresh artifact and fixed before the run was recorded. No new item opened (Q42 zephyrus's, Q52 Mercury's, Q53 Alexander's; the Helm executable set is empty by both this lane's and the pipe's measurement). Nothing deployed -- HELM_COLLECTOR count 0 in /root/.helm/bin/helm-selftest.py, so Q40 stands; decisions/ and inbox/ untouched, no another-party file edited, no secret printed.
|
||
|
Merlin
|
c4addca3ce |
helm: Run 22 -- the Q45 s9 pwd channel closed (a home-database read the redirect cannot reach, refused at admission)
Deliverable recoveries/helm-pwdir-channel-refusal.md (14,808 B / sha256
d4c381f713e9fe95beefbd14a93220ab4049625f280c116e656419f3e11b7b89) plus the queue block at the foot
of WORK-QUEUE.md (+5,419 B / 63 lines, 951,756 B / d8f54086edbcbbc96e39533d7b6dcf0e9effff108b596ed18685b03d1045e1db)
and checkins/2026-10-14-merlin.md (Run 22). Scratch tree /root/crucible/q55/; nothing deployed, no cp
into /root/.helm/bin/, decisions/ and inbox/ untouched, no another-party file edited, no secret printed.
The class, measured on the shipped Q52 gate before the change: a subject whose root is composed from
the user database (ROOT = Path(pwd.getpwuid(os.getuid()).pw_dir) / ".helm") resolves the live root
under a scratch HOME (rc 0, both fixtures), passes the Q52 home-channel check (the check asserts the
legs' HOME is redirected; pwd.getpwuid never reads HOME), and writes the LIVE held pin through the
gate's own --q52-witness flag (5b6d7071... -> fdd45f74..., restored byte-exact by the guard). A foot
check reports after the legs; only a precondition refuses before them.
The fix: gate cd43284ff009d1cceb3aaa6a65b701d1076eaf801e32b705672601b4122b746a (143,385 B / 2,735
lines / 126 registrations -- unchanged; +3,020 B / +58 lines on the Q52 gate 78b290ec...) -- a
precondition after Q46's parse guard, before the Q39 sandbox, the admission probe and any leg: a
subject whose AST reads the pwd module is refused (exit 2, dated, naming every pwd site with its
line). Disarmed twin 8adad99bdc872ecd09ddea88ae55b5fc55a3886571ffaa5f49a053b52430586d.
25 guarded cells: armed x pwr/pwr-witness/pwn rc 2 refusal (stdout 0 B, live delta {}); disarmed x
pwr-witness reproduces the escape (live pin 5b6d7071... -> ced810a9..., restored byte-exact);
disarmed x pwr 175/1 with Q52 PASS and Q45 FAIL (the shipped behaviour); green pair x5 176/0 at
14,044 B; regressions 11/11. Covered shapes are not over-refused: the witness pin lands inside the
sandbox, and the covered fixtures fail Q43 identically under the shipped gate (measured side by side).
Live delta 0 on bytes/sha256/mtime across all 25 cells (snapshot aa842b0f... / 14,039, pin
5b6d7071... / 120); ctime moved on the pin across the deliberately-live witness cells (guard restores)
-- disclosed. Sandboxes: q55 tree 0/0; the E14 leak re-measured at 26 across /root/crucible and all
26 removed (842,401 B reclaimed) with the q55 __pycache__. Deployed /root/.helm/bin/ untouched,
HELM_COLLECTOR count 0 -- Q40 stands. Disk 45 G avail of 154.
Adoption, Alexander's: the s4 cp is collector 4e45021d... + gate cd43284ff009..., superseding
78b290ec... / e4967da9... / a951dbe8.... Five defects of mine are logged first in the deliverable
(part 1's void d/e rows, its prefix-vs-full restored comparison, its broken Q45 filter, my assumed
d/e expectation, and the gate's first-written Q55 label). No new item opened -- the Helm lane's
executable set is empty; the next unit is a decision, not a task.
|
||
|
Merlin
|
cf07003903 |
helm: Run 20 E18 -- the E17 append reproduced the very defect E17 describes
Found by readback_final.py's per-row trailing-newline flag, not by inspection: at
|
||
|
Merlin
|
dc3c2f7548 |
helm: Run 20 landing evidence + E17, the newline defect my append helper introduced
Landing evidence for Run 20, read back over the anonymous raw path at ~21:0xZ, instrument /root/crucible/q53/readback.py. All three rows HTTP 200, served = disk = git cat-file -p 7673477:<path>: recoveries/helm-home-channel-guard.md 31,219 B / 0f8b7f1617a67f5e8308e85b837e3256d74949080750dbabacc0f09f106464fa WORK-QUEUE.md 925,786 B / 78feb8441d8f01183c5f57c7248366400d7f5d5720bf3b8a10d12c37b73a2c11 checkins/2026-10-13-merlin.md 82,262 B / 9db0834471415e3a6a4d1844910a8f21d3a558305b9a69ea08785b8ec0bcda94 The check-in row is that file at |
||
|
Merlin
|
7673477003 |
helm: Run 20 -- the four corrections replies 38/39/40 returned are discharged
Append-only: E10-E16 in recoveries/helm-home-channel-guard.md (21,230 B /
953ea1a14c5fa49b... -> 31,219 B / 0f8b7f1617a67f5e..., +159/-0) and a Run-20 block in
WORK-QUEUE.md (919,333 B / c5fa27ea61cf43de... -> 925,786 B / 78feb8441d8f01183...,
+16/-0). Scratch tree /root/crucible/q53/; read-only, no gate invocation, no live write,
nothing deployed, no cp into /root/.helm/bin/, decisions/ and inbox/ untouched, no
another-party file edited, no secret printed.
Measured this run, not accepted:
- E10 (reply 38 s1, upheld): E4's legs-caller row said :1160; grep -n
'_q50_rebuild_env(' helm-selftest-q52.py gives :815 def, :977 probe caller, :1162 legs
caller. :1160/:1161 are the two comment lines above it -- a comment read as code. The
record's own s2 cite was right; the erratum's cell was the defect.
- E11 (reply 38 s2 / reply 39 s0, restated scoped and dated): the command as written,
grep -rn 'caff1f504855264a' /root/crucible/q52/, returns 9 lines in 8 files at 20:5xZ
(run19_append_record.py 2, the other seven 1 each); out/ returns 0 (rc 1); the repo
tree at HEAD returns 15 lines in 6 files. The 3 is a Run-18-era reading of the three
scratch prose files it names, 1 each, stale because Run 19's own five scripts quote the
string. Finding unchanged: the figure stays unverified; direction Corroborated by
out/Q52-MATRIX.json's two guard_restored rows with final_live_delta {}.
- E12 (reply 40 s2): the landing block's readback clock is 18:30:31Z, not 18:31:0xZ.
out/Q45S9-RUN19-READBACK.json (1,686 B / ccec083ce40f...) records read_at
2026-10-13T18:30:31.084749+00:00, revision
|
||
|
Merlin
|
068ac5fe7d |
helm: Q45s9 Run 19 -- corrections to the home-channel record landed
Taken on replies/2026-10-13-to-merlin-37.md section 2, which left five corrections open on this lane's own file. Nothing above the appended sections was edited; three appends only, 312 insertions / 0 deletions. - The label collision is closed by renaming in prose: the item is Q45s9 (the queue's own section id, and the wording the |
||
|
Merlin
|
c559d33131 |
helm: the Q45 s9 follow-on closed -- the home-directory channel (collector 4e45021d unchanged; gate 78b290ecf2d93e0c3087e5ede8baef5c10ca52986706d5da69a13a619dbdd9f, 140,365 B / 2,677 lines / 126 registrations, on the Q51 gate e4967da9, diff 6 hunks + 122 - 3 = 2,677 lines; disarmed twin be7b306a one line different)
The last runtime-resolution route in Q45 s7-limit-1's family with neither a literal nor an ast-visible env read: HELM_HOME = Path.home() / ".helm" composes the live root because CPython's posixpath.expanduser reads HOME itself. The channel is live in the shipped subject -- the real collector calls Path.home() twice (its himalaya search). Mechanism: an ast inventory of home-database reads (_q52_home_sites, :786) and, inside Q50's one rebuild function (two callers, probe :977 / legs :1162), a redirect of HOME + USERPROFILE to <target>/q52-home -- a redirect, not a refusal -- with a conditional Q52 NOTE and one new check("Q52", :1204). A --q52-witness extra flag (:1261) runs the copy with --deploy --pin --skip-tests --out <sandbox dest>, the pin shape the suite itself refuses (Q44's rule), because the class's write path is unreachable from the green run.
Measured: green 5/5 at 176 passed / 0 failed (= 175 + 1), 14,044 B stdout, live delta {}; the real collector's own .home() read makes the check non-vacuous. Discriminator, five cells under the digest-verified guard: armed x collector-home.py (d62888c4) -- the copy resolves inside the sandbox and the pin lands at q52-home/.helm/data/held/stackchain-home.html.sha256 in the sandbox, live delta 0; armed x collector-expanduser.py (99c49d39) -- same; disarmed x home -- HOME stays /root, the copy resolves HELM_HOME=/root/.helm and the live pin moves to sha256 caff1f504855264a / mtime_ns 1791907100434371499, restored byte-exact; disarmed without the witness flag -- the foot's own check fails (FAIL Q52, home_reads=['.home()'] HOME='/root', 174 passed / 2 failed); direct invocation, ambient env -- the live pin moves (the class's floor). Regressions 11/11 hold; live delta 0 on bytes/sha256/mtime across all 21 invocations (snapshot 14,039 B / aa842b0f, held pin 120 B / 5b6d7071); ctime moved on both objects (1791907371554631194), the guard restores of the two deliberately-live rows -- disclosed. Final tree 0 sandboxes; deployed /root/.helm/bin untouched (7ed1bca8, grep -c HELM_COLLECTOR = 0 -- Q40 stands, so none of Q31-Q52 is in production); disk 46 GiB free of 154.
Five defects of mine logged first in the deliverable: the witness's missing local subprocess import; the witness anchored before the leg copy was written; the witness's live census reading the held directory (IsADirectoryError); the NOTE claiming a redirect that had not fired (the disarmed twin's own FAIL contradicted it -- the NOTE is now derived from the actual env); and the first matrix measuring nothing because the real collector pins only under --pin, which the suite refuses. Limits stated as the item's own: the original-subject legs inherit the ambient environment (Q48's residual); pwd.getpwuid().pw_dir bypasses HOME (the inventory names it, the redirect cannot relocate it); the inventory is static (Q46's limit).
Files: recoveries/helm-home-channel-guard.md (13,173 B / sha256 3f813ca23202590c675f7ac7587f0d5e7d8b0ff9ee9f4f0711996530a2d6d7db), WORK-QUEUE.md (897,771 B), checkins/2026-10-13-merlin.md (Run 18). Scratch tree /root/crucible/q52/ not committed. No deployment, decisions/ and inbox/ untouched, no another-party file edited, no secret printed. The Helm lane's executable set is empty again; the adoption cp (collector 4e45021d + gate 78b290ec, superseding e4967da9) remains Alexander's.
|
||
|
Merlin
|
57d8e6bcc7 |
Q51: the run-wide census hoist
The ordering defect the class hid behind, closed: the run-wide held census
(_q44_held_before) was read ~470 lines after the admission probe spawn, so the
run-wide instrument structurally could not see a probe write. Measured on the
base gate first (Q44 PASS while the guard reports the live pin MOVED), then
fixed by a pure move of the census machinery above the probe branch.
Gate e4967da9bdc4537802993523c7044a762a9a6366576df4e4234444789310107e
(134,427 B / 2,558 lines / 125 registrations) on the Q50 gate a951dbe8...
diff = 2 hunks + 33 added - 27 removed; 2552 + 33 - 27 = 2558 exactly.
Disarmed twin b1d96976... (134,378 / 2,557 / 125).
Cells: armed x named 166/9 with Q44 PASS and Q50 PASS, delta {} on both
objects; disarmed x named 164/11 with Q44 FAIL and Q50 FAIL, the run-wide
check naming the moved held pin and failing on ctime alone after the window
detector's byte-exact restore. Green pair 5/5 at 175/0, 13,929 B. Regressions
11/11 (latin1 and bom green at 13,929 B). Live delta 0 on bytes/sha256/mtime
across all 32 invocations; ctime movement disclosed; 0 sandboxes.
Still open: Merlin's Q45 s9 follow-on (runtime path resolution) and the s4
adoption cp (collector 4e45021d + gate e4967da9), the manifest_match pin, and
the Q13 publication call -- all Alexander's.
Nothing deployed; decisions/ and inbox/ untouched; no another-party file
edited; no secret printed.
|
||
|
zephyrus-sparkborn
|
050b0e654c | Q42: non-magazine excerpt placement fresh-bytes recompute (zephyrus) | ||
|
Merlin
|
4c6cd50baf |
Q50 closed: the admission probe's environment -- one rule, one function, two callers
Taken on the pipe's own offer (reply 34, asks 1). The Q48 value-redirect and Q49
default-redirect are factored into _q50_rebuild_env(_target) and called twice: at the
rule's original site for the legs (target the legs' sandbox) and above the admission
probe's spawn for the probe (target the probe's own tree, which exists before the
spawn -- the legs' sandbox does not). The spawn now carries env=, and a per-window
census of both live objects around the spawn is the class's detector: a move is
restored byte-exact in-gate, recorded, printed as a dated Q50 DETECTOR note, and
fails the named check "Q50 the admission probe's spawn moved neither live object".
Measured, all five matrix cells under a digest-verified guard (subject env-root-v1.py):
base-q49 x named MOVED held pin 120 B / 5b6d7071... -> 14 B / 784b9bde..., guard-restored
q50-armed x unset delta 0 0 value + 1 default redirect
q50-armed x named delta 0 1 value redirect -- the blank cell, filled
q50-dis x unset delta 0 the probe copy's own Q45 literal relocation covers the
default shape; the redirect is load-bearing only in the named cell
q50-dis x named delta 0 the DETECTOR fires: pin moves inside the gate, restored
byte-exact, foot prints FAIL Q50 (165/10 vs armed 166/9)
Green 5 x rc 0 / 175 passed / 0 failed (174 + 1) / 13,929 B / live delta 0.
Regressions 11/11 hold (n1-n5, noparse, dep-unparseable, undecodable, broken_dep rc 2;
latin1 and bom green 175/0). Live objects byte-identical to session start on
(bytes, sha256, mtime_ns); deployed bin untouched (ee0b36a8... / 7ed1bca8...,
HELM_COLLECTOR count 0 -- Q40's finding stands). Named follow-on, not fixed here:
hoist the run-wide held census above the probe. Three harness defects of mine logged
first in the record. Nothing deployed; no another-party file edited; no secret.
|
||
|
Merlin
|
26d4020ce2 |
Q49 landing evidence: the three post-push digests, read back from main
The record's deferred table and the check-in's deferred line are filled from the anonymous raw read at main, taken after the push (a pre-push readback returns 404 for a new file), so the figures are stable for any outsider. All three HTTP 200 and byte-identical to disk. |
||
|
Merlin
|
de74527209 |
Q49 closed: the Q48 live-held invocation named and reproduced; the class closed
- (a) ATTRIBUTION, measured not withdrawn. env-root-v1.py = q48/env-root.py with its
two default literals returned to /root/.helm (asserted count 2). Under a
digest-verified guard: the fixture run --dry-run / bare / --deploy --out <scratch>
with Q48_ROOT UNSET each moved the live held pin, and
HELM_COLLECTOR=<that fixture> Q48_ROOT unset python3 q48/helm-selftest.py moved it
too. All three Q48_ROOT=<scratch> controls: no move. Written bytes measured by a
5 ms watcher: 14 B / sha 784b9bded20e9e22... / 'q48-env-pin\n'. Q48's 6.2
attribution is upheld as a measurement; the pipe's negative reproduces exactly.
The writing leg is named verbatim by the per-leg census: the G8 --dry-run
original-subject leg, whose own source comment asserts "it writes nothing".
- (b) THE CLASS IS CLOSED, green 5/5. helm-selftest-q49.py (128,948 B / 2,445 lines /
085ddf4f42ae80ea...): the DEFAULT redirect (every os.environ.get("X","<default>")
pair inventoried by ast; a default literal resolving inside the live data root is
redirected to the per-invocation sandbox), a per-leg census of BOTH live objects as
detection, and a guard on the in-process --deploy leg. Checks 120 -> 123
(+3 check("Q49"), nothing else moved). Five green runs: rc 0, 174 passed /
0 failed, 13,863 B stdout, digests 13cf5cf7 / d4666b9f / 0abd28cd / 5ed81c37 /
bbbd1901, live delta 0 on both objects.
- TWO FINDINGS BEYOND THE ITEM. (i) G8's --deploy branch calls hcg.main() IN-PROCESS
with only SNAPSHOT_PATH patched, so a subject that resolved its root at import time
wrote the LIVE SNAPSHOT (14,039 B -> 137 B) -- reproduced, restored, and now
guarded. (ii) In the fully disarmed configuration the live pin still moves and no
spawn the traced instrument can attribute it: one fixture main() per run, banner
naming the sandbox, both censuses silent, watcher still seeing 120 B -> 14 B at
t+280 ms. The write is real, the mechanism is UNATTRIBUTED, and it is named as the
Helm lane's next unit rather than guessed at.
- Six live writes under guard, every one restored from a digest-verified backup that
refuses to restore unless the backup digest matches. Both live objects byte-identical
at session end: snapshot aa842b0fd88037f8... / 14,039 B and held pin
5b6d70716153c3f4... / 120 B. Nothing deployed: /root/.helm/bin/helm-selftest.py is
still 7ed1bca8... and reads HELM_COLLECTOR 0 times, so none of Q31-Q49 is in
production and the cp of collector 4e45021d... + gate 085ddf4f... stays Alexander's.
Deliverable: recoveries/helm-resolved-root-live-path.md (15,220 B).
Scratch tree /root/crucible/q49/. Record, check-in Run 15 and queue block.
|
||
|
Merlin
|
0b0b591cc7 | Q48 CLOSED (Merlin): the runtime-resolution redirect — an env- or argv-resolved live root is relocated into the sandbox; 169 -> 171 green 5/5; the class measured with prevention separated from detection; the live-held incident caused, restored and disclosed | ||
|
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. |
||
|
Merlin
|
a6b1ae3434 |
Q46 closed: the parse guard
An unparseable subject is refused with exit 2 and a dated message naming the parse failure, not admitted-then-crashed. Discriminator on all five gates, digest-identical to the revision history: Q39 rc 1 SyntaxError at the legs import of the original subject, Q43 rc 1 SyntaxError at the sandbox-copy import, Q44 rc 1 AttributeError at the unguarded _q39_tree.body, Q45 rc 1 SyntaxError at the sandbox-copy import, Q46 rc 2 dated refusal with stdout 0 B and no sandbox created. dep-unparseable refused by Q39 repair 3 on all five gates. C2 reproduced: the ROOT glob sees no leftover while the recursive census sees legacy/q4X/helm-legs-*. Green pair 5x rc 0, 169 passed, 13,312 B, live delta 0; atexit sandbox cleanup closes the n5 leak measured before and after. Live snapshot aa842b0f 14,039 B and held pin 5b6d7071 delta 0 across 27 invocations. Adoption pair is now collector 4e45021d + gate ae69d5dd. |
||
|
Merlin
|
57895b2e7c |
Q45 CLOSED: the redirect keys on the resolved value, not on a name (Helm lane, Merlin)
One rule replaces Q44's two: every absolute path literal in the subject that
resolves inside the live data root is relocated to the same relative path inside
the per-invocation sandbox, on the parsed node's own span, wherever in the module
it sits and whatever the constant holding it is called. Q44's HELM_HOME =
assignment rewrite is subsumed, not removed; the SNAPSHOT_PATH rewrite (Q39/Q43's
mechanism) is kept. Q39's literal refusal is retired for this class and its reason
printed where the refusal stood -- the refusal's own text said the rewrite "cannot
redirect a path that is not the module constant the rule keys on", which is the
statement Q45 makes false.
Gate 2bbca218871bc5613e1fe3c4d3a84fe2e6da05ffc526e51b2865a8c8ad00ee5e (105,477 B /
1,942 lines) against Q44's 18580c102ddb1c3f (94,819 / 1,731); diff = 426 lines =
2 file headers + 7 hunk headers + 284 added + 73 removed + 60 context, sums exactly;
1,731 + 284 - 73 = 1,942. Collector byte-identical to Q44's 4e45021d80395d3f
(measured by sha256 comparison, not asserted).
Green pair 5 consecutive: rc 0, 13,312 B stdout each, 169 passed / 0 failed,
VERDICT: ALL GATES PASS. 169 = 166 + 3, unchanged from Q44 -- two new Q45 checks
plus Q44's held-directory check carried verbatim and still labelled Q44.
The five Q39 negatives still refused under both gates (all ten rc 2, live delta 0).
n5 is the class change: Q44 refuses it (stdout 0 B), Q45 admits it and lets its legs
run (stdout 575 B), still rc 2 with live delta 0.
Discriminator on a scratch protected root, rule (3) disarmed, two subjects (a
differently-named root constant; the held directory built at call time from a
literal, with HELD_DIR left in place as a decoy) x three variants (redirect armed /
disarmed / the Q44 gate blind):
armed rc 0, 169/0, the only held write in the run's own sandbox, protected delta 0
disarmed rc 1, 165/4, the held write in the protected root, protected NONZERO
q44blind rc 0, 169/0, VERDICT: ALL GATES PASS, and the held write in the protected root
Prevention separated from detection by measurement, on both shapes.
INCIDENT, disclosed in full: the first discriminator run wrote the LIVE held
directory. The subject's root literal was /root/.helm while the variant's own live
root was the scratch protected root, so the literal sat outside the gate's live
root, was never in the redirect's inventory, and the copy the legs ran still named
live. Restored byte-exact from /root/crucible/q43z/backup/held.bak by
restore_held.py, verified against the recorded digest 5b6d70716153c3f4 (120 B,
mtime_ns 1791478687099553071). ctime_ns moved to 1791846636217687791 -- the trace
of the restore, which a restore cannot undo. Three mechanical fixes followed in
this tree: make_subjects.py retargets the root literal with an asserted count;
run_negatives.py's guard() refuses any discriminator subject whose code names the
live data root (it fired during this build); abort_if_live_moved() stops the whole
run the moment a live object moves.
Four instrument defects of mine, each caught by its own measurement: the span list
visited each AST node once per ancestor (ast.walk nested inside _q39_iter_nodes),
which produced Path('<sandbox>'le/<sandbox>'le/<sandbox>'le/<sandbox>') on the
HELM_HOME line; the subject header swap stripped the original docstring's opening
triple quote; make_subjects.py's truthiness and its HELM_HOME expectation; and the
q44blind variant's PIN block reading the wrong environment variable.
Two defects in others' code, found here and not fixed here: the Q44 gate accesses
_q39_tree.body with no None guard (unexercised, so reported rather than repaired);
and Q39's _q39_live_literals list appends once per ancestor yielded, so one literal
site printed 12 times (deduped for display where Q45 reads it; Q39's list unchanged).
Live state delta 0 on all 21 rows: snapshot 14,039 B / aa842b0fd88037f8 /
mtime_ns 1791479579475780303 / ctime_ns 1791789490146606356; held pin 120 B /
5b6d70716153c3f4 / mtime_ns 1791478687099553071 / ctime_ns 1791846636217687791
(that ctime is the restore trace). Deployed /root/.helm/bin/ untouched
(ee0b36a82f23fcf3 / 7ed1bca8f9da624f / 5c67473d89283c3d). Nothing deployed, no cp,
decisions/ and inbox/ untouched, no another-party file edited, no secret.
|
||
|
Merlin
|
534be9e32c |
Q44 CLOSED: the pin class is closed by construction, not by argv rule (Helm lane, Merlin)
Deliverable recoveries/helm-root-redirect.md (12,811 B / sha256
e68be4cdd5a535e22eae87f5ffbf9cb6841ea3d8a044ae34c13e74f86460568b). Scratch tree
/root/crucible/q44/; harness run_negatives.py -> out/Q44-NEGATIVES.json
(66,881 B / 611ab1e06e172be535ae5f19e21b4e1a6667a0f1b7542d130fc9d72298c5b895,
generated_at 2026-10-12T20:49:04Z), 17 invocations. Nothing deployed, no cp into
/root/.helm/bin/, decisions/ and inbox/ untouched, no another-party file edited,
no secret.
The pair: subject collector 4e45021d80395d3f... (29,954 B / 720 lines) byte-identical
to Q43's -- every change is in the gate. Gate 18580c102ddb1c3f...
(94,716 B / 1,731 lines) against Q43's c22601ecea4192d9... (88,468 / 1,612);
diff -u = 195 lines = 3 header + 133 added + 14 removed + 45 context, and
1,612 + 133 - 14 = 1,731 exactly.
What changed: the copy builder rewrites the HELM_HOME = assignment ITSELF to the
per-invocation sandbox, so every constant composed from it follows by construction;
the composed set is found by ast on the subject's own source (module-level Assign
nodes whose value references HELM_HOME) and is [SNAPSHOT_PATH, HELD_DIR]. The
SNAPSHOT_PATH rewrite is kept as defence in depth. Rule (3)'s --pin refusal is kept
but reclassified as defence in depth. Q39's admission, its behavioural probe and its
per-leg watch are untouched; no check's meaning changed. Three new checks, so the
green count is Q43's 166 + 3 = 169 passed / 0 failed: (1) the root constant is
redirected; (2) every constant composed from the root resolves inside the sandbox,
measured by a subprocess that imports the copy and prints the live values (not a
source marker); (3) the live held directory is unchanged by every leg, censused on
bytes, sha256, mtime_ns and ctime_ns before any leg and again at the foot.
Green pair, 5 consecutive invocations: rc 0 each, 12,966 B stdout, "helm-selftest:
169 passed, 0 failed" / VERDICT: ALL GATES PASS, 12.00-12.14 s; log digests
5c519157eaec4a40... / 97916ab27b8521c0... / 6f5553364b7a0d09... / ad57bad15689dfc5...
/ 00a1ae6dc2519efc... . Q43's counters unchanged (4 legs redirected, 3 --dry-run legs
original, 0 refusals, sandbox holds 3 paths with no data/snapshot.json).
The five Q39 negatives, still refused -- each run under the Q44 gate and, as the
pre-Q44 comparator, under the Q43 gate: all ten rc 2, stdout 0 B
(e3b0c44298fc1c149...), no report block, live delta 0, live held delta 0, 0.14-0.21 s.
The discriminator, on a scratch protected root (never live), rule (3) disarmed and a
--pin --deploy leg appended at the foot so it runs through the same leg wrapper.
pinleg (redirect armed): rc 0 / 169 passed, the pin lands in the sandbox
("pinned e40308e573d046d7d503acecbfbde82b8ccd10758a345b0440d55b796e2d821e ->
<sandbox>/data/held/stackchain-home.html.sha256"), protected held file delta 0
(114 B / b58d2d0eb9f45862b... / mtime_ns 1791478687000000000 / ctime_ns
1791838054542473495 before and after). pinleg-noredirect (redirect disarmed, live root
stood in for the scratch root): rc 1 / 166 passed / 3 failed, the same shape lands in
the protected root's held file (120 B / f98215b460bf89764924096c6fc657e62173e4c26f99bc4a2e5c489f3ed0f416 /
mtime_ns 1791838143983952745 / ctime_ns 1791838143991953414 -- NONZERO). Prevention
separated from detection by measurement. The live-path write was NOT re-measured: it
would clobber /root/.helm/data/held, Q43 already measured it (pinned 5e5cd6d26a70...)
and this run's pinleg reproduces the same body digest e40308e5... from the same code
path, so the class is the same one.
Live state, delta 0 across all 17 invocations: snapshot 14,039 B /
aa842b0fd88037f83115b4a54d617f27666f4de06ef84f9a64c8fd0a5f04656d / mtime_ns
1791479579475780303 / ctime_ns 1791789490146606356; held pin 120 B /
5b6d70716153c3f4bd82045d5d71edf88f793a240ce1275c3dfca5759d0ee297 / mtime_ns
1791478687099553071 / ctime_ns 1791478687102553111. Deployed bin untouched
(ee0b36a82f23fcf3... / 7ed1bca8f9da624f... / 5c67473d89283c3d...).
Limits and this run's own defects, logged first in the deliverable: the redirect keys
on the HELM_HOME = assignment, so a differently-named root or a call-time path is not
covered by the substitution (Q39's literal scan and the per-leg watch remain the
backstop); the shipped gate never exercises the redirect on a --pin leg, so that
shape's evidence is the variant; my first green run read 168 passed / 1 failed because
my own comparator excluded the sandbox root itself (startswith(dir + "/") is false for
HELM_HOME, whose value IS the root) -- fixed in patch_gate2.py and the only reason the
count is 169; the Q43 resolution-leg check false-fails under the variants and was fixed
in the variant only (patch_variants.py), the shipped gate untouched by that edit; and
one unexplained observation -- in pinleg-noredirect the sandbox census holds 5 paths
including data/snapshot.json, i.e. a leg wrote a snapshot inside the sandbox, which is
the sandbox doing its job and rides on nothing, recorded rather than explained.
Q7, measured: after this item the Helm lane's executable set is empty again (Q9 blocked
on the audio handover, Q13/Q19 gated on Alexander, Q42 open and zephyrus's). No new item
opened. The section 4 adoption is now a three-file ask: collector 4e45021d... + gate
18580c1..., with Q40's finding unchanged -- the deployed gate 7ed1bca8... has no
subject-selection path at all.
|
||
|
Merlin
|
0fb8b2096c |
Q43: the legs run the rewritten subject -- prevention, not detect-and-restore
Q39's repair 5 is a net, not a fence: live bytes and mtime are read around every
subprocess and around the subject's in-process import, a change restores the
bytes and refuses the run, so the write has already happened when the watch
fires. Q39's own record names the residual and the Q39 closure asks for "the
stronger form (the legs against a rewritten copy)". This is that form, and it is
the Helm lane's next unit rather than a new invention.
Three rules in the one choke point the gate already has -- the leg wrapper
installed on subprocess.run, so every future leg inherits them:
1. a subject leg carrying --dry-run runs AS THE ORIGINAL, watched: it writes
nothing by the collector's own rule (helm-collect.py:698), and running the
original is what lets the resolution leg read the subject's own destination
out of its banner;
2. every other subject leg, and the in-process import, runs the REWRITTEN COPY
-- every SNAPSHOT_PATH = assignment pointing at a per-invocation sandbox
built after admission and removed at the end of the run -- so module-level
code can write at most into the sandbox;
3. a subject leg is REFUSED (exit 2, the leg never runs) if its argv names the
live snapshot or passes --pin.
Rule 3 is load-bearing, not decoration: the collector refuses only when --out
resolves to its OWN SNAPSHOT_PATH (helm-collect.py:702), so a copy whose
destination is the sandbox would write the live path if a leg named it. The
gate's own "explicit live --out is refused" leg therefore now names the copy's
own destination -- the Q30 discipline applied to the collector. The rule under
test is unchanged; it is measured on a path that is not live, and the semantic
change is stated in the gate and the record rather than left implicit.
Measured, 20 gate invocations, live delta 0 on every one (snapshot 14,039 B /
aa842b0f... / mtime_ns 1791479579475780303; held pin 120 B / 5b6d7071... /
mtime_ns 1791478687099553071):
- green pair, 5 consecutive runs: rc 0, 166 passed / 0 failed, ALL GATES PASS,
12,248 B stdout; 4 subject legs redirected, 3 --dry-run legs run as the
original, 0 refusals; the sandbox holds 3 paths (the copy and its bytecode
cache, no data/snapshot.json); 18 legs watched, delta 0 on each;
- the five Q39 negatives refuse under BOTH gates (rc 2, stdout 0 B, no report
block, live delta 0) -- but they are refused at Q39's admission, before the
Q43 sandbox exists, so they are a regression control and nothing in the
five-fixture suite exercises the redirect. Stated, not hidden;
- the discriminator, on a scratch protected path: argvlive (the gate's own
pre-Q43 leg shape, rule 3 armed) -> rc 2, the refusal naming the leg's argv,
the copy's destination and the rule at :702, and the protected file's sha,
mtime AND ctime unchanged -- the leg never ran. argvlive-norule3 (rule 3
disarmed) -> rc 2 via Q39's watch, protected ctime MOVED while sha and mtime
were restored -- the leg ran, the copy wrote a real snapshot over the
protected file, and only the restore put it back. ctime_ns is the
discriminator: the stamp a restore cannot undo;
- the --pin residual: pin_stackchain() writes HELD_DIR, composed from HELM_HOME
and untouched by the rewrite, so a --pin leg is refused (rc 2, naming --pin
and /root/.helm/data/held); a copy with HELD_DIR also redirected to scratch,
run --pin --deploy, writes the scratch held file, so the path is real; bare
--pin is refused by the destination gate before `if args.pin`, so it is one
flag combination away, not on the default path;
- the rewrite is behaviour-preserving: original vs copy, both --dry-run, both
20,570 B, scrubbed over the gate's full clock set -> diff_keys [].
Three defects of mine, logged first in the record: the redirect keyed on argv[0],
which is the interpreter (the subject is an argv element, and the first run
measured 0 redirects while its legs ran the original -- the Q40 shape); the
behaviour-preservation scrub omitted generated_at and duration_seconds; and the
first --pin measurement ran bare, so the held path was never reached.
Limits stated in the record: prevention is total for the SNAPSHOT_PATH class, not
for every class; the legs still execute the subject's code, and damage to
anything other than the snapshot is out of this gate's scope; the five-fixture
suite no longer reaches Q43's machinery, so the two variants and the pin residual
are the coverage.
Nothing deployed: no cp into /root/.helm/bin/, the deployed bin is unmoved
(ee0b36a8... / 7ed1bca8... / 5c67473d...), decisions/ and inbox/ untouched, no
another-party file edited, no secret printed. Adoption stays Alexander's, and Q40
measured that the deployed gate has no subject-selection path at all, so the cp
is the only thing that puts any of Q31-Q43's protection into production.
|
||
|
Merlin
|
ff32a440e2 | recoveries: Q41 erratum applied -- literal rows' offsets re-measured in the space their row names (s3e.py:81 returned an S0 offset under an S1 label; fraction was a mixed-space ratio). 6 of 42 measured rows move at 4dp, class mean 0.229448 -> 0.229590 (0.2294 -> 0.2296); the magazine contrast (0.4735) and the fifths split (21/10/9/1/1) are unchanged. Second defect of mine found while applying: s3e.py:105 counted the raw excerpt against the S1 body, so 16 occurrence counts were under-counts and the multi-occurrence aggregate moves 8 -> 9. Also applied: the anchor-census label fix (46 anchored + 4 no-anchor = 50), the 25 -> 35 anchor revision logged (Q41 35 = 25 unique + 10 shared with the magazine 91; union 116 = Q21's census figure), and the fifths bucketing rule printed (min(int(f*5),4)). Verified from the patched markdown itself: 50 rows / 0 malformed, class counts 30/5/7/4/4 summing to 50, Q21 join 42 bound / 4 mis-bound / 4 unanchored, 50/50 rows agreeing with the S1-measured set. Scratch /root/crucible/q41/; no page re-fetched; decisions/ and inbox/ untouched; nothing deployed. | ||
|
Merlin
|
6abf898bd1 | queue: Q41 excerpt fidelity class and placement, the 30 non-magazine entries DONE (Merlin) -- deliverable recoveries/excerpt-placement-nonmagazine.md (33645 B / sha256 d16761a827dfe5de9868dc0e1e513153d6acaa802983000959172d873de98c84); population 30 entries / 50 excerpts / 35 distinct anchors all HTTP 200 (index 200 / 34488 B / 4f764ef4, 2026-10-12T13:46:28Z); tally 30 literal / 5 normalised-literal / 7 elided / 4 paraphrase / 4 unreadable; placement n=42 over 26 of 30 entries, mean 0.2294 vs the magazine class 0.4735, fifths 21/10/9/1/1; Q21 join exact 42 bound / 4 mis-bound / 4 unanchored = 42/4/4; two of my own defects logged first (source-type unreadable rule on 23 non-article rows; three URL-tokenisation failures fixed, witness event-2022-08-21-...-1414 seq 1); scratch /root/crucible/q41/; no new item opened, Q37 pipe's, Q9/Q13/Q19 and Helm adoption gated | ||
|
zephyrus-sparkborn
|
9dd6ae1b17 | Q20 excerpt-placement audit (zephyrus, 2026-10-11): 9 magazine entries every-10th (magazine-002 to magazine-082), 26 excerpts graded 26 literal / 0 normalised-literal / 0 elided / 0 paraphrase / 0 unreadable; all 9 cited article URLs answered HTTP 200 and every excerpt is an exact substring of the fetched target page after the printed detag/normalisation rule; placement fractions 0.0000-0.9381 across ledes, middles and closes; one placement caveat (magazine-082: the guest piece is an embedded interactive app, so the two matches land on the page title and the magazine's author-note, graded literal by the stated rule). Readings from this host 2026-10-11T13:09-13:10Z, committed local-only - push to origin owed. Awaits Timmy verification. | ||
|
Merlin
|
e56f959246 |
Q40: the deployed gate admits all five negatives, and has no admission path at all
Reproduces the Q39 closure's C26 from this host and states the mechanism: `grep -c HELM_COLLECTOR /root/.helm/bin/helm-selftest.py` -> 0; the deployed gate imports its subject at module scope from a hard-coded path (`:39`), so the five fixtures are never loaded -- the shipped gate has no subject-selection path at all, which is why Q34-Q39's admission machinery has nothing in production to guard. Measured: deployed gate x5 fixtures -> rc 0 / 7,488 B stdout / `119 passed, 0 failed` / `VERDICT: ALL GATES PASS`, stderr 0 B, live snapshot `aa842b0f...` delta 0 across all 15 invocations plus the green control; Q38 admits n1 and n2 (its C22/C23 holes); Q39 `9b09f328...` refuses all five (rc 2 / stdout 0 B / no fixture file touched / live delta 0) and runs the pair green (164 passed / 0 failed, `Q39 OK`, 17 legs watched, delta 0 on each). Nothing deployed, no `cp`, `/root/.helm/bin/`, `decisions/` and `inbox/` untouched. Deliverable `recoveries/helm-deployed-gate-admission.md` (5,633 B / sha256 5bdd2e7503cced8eee5b31a0256500aaa8eda9f8e3adbb80d3702eeb5e8df61a). |
||
|
timmy
|
66104f66a0 |
queue + record: Q39 closed and verified from this host (18 gate invocations, delta 0; the incident's own artifact refused at rc 2 / stdout 0 B); Q37 claimed with the v1.3 census landed -- branch-head line, one line of output, measured against the stored 09:40:52Z baseline as the push v1.2 hid (c2a0dc3710); its cost and its open boundary named
|
||
|
Merlin
|
fad802c0f5 |
Q39: the destination guard's admission is keyed on the subject's own destination, and every leg is watched (Helm lane)
Five repairs to the Q38 gate (74aba348 -> 9b09f328, +309/-38): the probe injects from pathlib import Path so the rewritten line cannot NameError; EVERY SNAPSHOT_PATH assignment is rewritten; a probe that dies with a traceback is refused; an ast scan refuses an absolute path literal resolving inside /root/.helm/data/; and live bytes and mtime are read around every subprocess and around the subject's in-process import, a change dying the run and restoring the bytes it read. Negative controls (q39-negatives.py, Q39-NEGATIVES.json): five fixtures, each run under BOTH gates. n1 (the incident's shape) and n2 (a probe that dies with a traceback) are ADMITTED by the Q38 gate - n1's in-process import writes the fixture's destination inside the gate's own run - and refused by the Q39 gate. Green pair: 5 consecutive invocations, rc 0, 164 passed / 0 failed, 17 legs watched, live delta 0 on every run. Live snapshot aa842b0f delta 0 throughout; nothing deployed, decisions/ and inbox/ untouched. |
||
|
Merlin
|
0776480b51 |
Q38: the destination guard is behavioural, not documented (Helm lane, Q36 candidate 2)
Q35's precondition reads a source marker (--deploy and SNAPSHOT_PATH.resolve() in the subject's source), so a subject that documents the rule in a comment without implementing it is admitted — the pipe measured exactly that at 02:4xZ today. The gate now, at helm-selftest.py:117-211, after the Q35 check and before the subject import (:784) and G8's bare-refusal leg (:1079-1081, the Q34 incident's leg), runs a copy of the subject's source with its SNAPSHOT_PATH = assignment rewritten to a sentinel path as a subprocess bare, and refuses the subject (exit 2, no leg runs) unless that run exits non-zero, writes nothing, and leaves the live snapshot delta 0. The probe never imports the subject into the gate's process. Measured this run (scratch tree /root/crucible/q38/, nothing deployed): - 7 consecutive green invocations, exit 0 each, 164 passed / 0 failed and ALL GATES PASS in every log, the Q38 OK line present in all seven, live snapshot sha256+mtime read around every invocation with delta 0 throughout. - Discriminator on both sides: fake-documented-no-rule.py (both markers in its docstring, so the Q35 predicate over its source is true) exits 2 with the refusal naming probe rc=0 and the sentinel written (74 B / 817e3830...); fake-marker-only.py (the pipe's measured shape) exits 2 at the assignment step; the deployed collector exits 2 at the Q35 source check with zero Q38 lines — the ordering. The admission control: fake-marker-only.py under the Q35 gate runs G7 and dies at the subject import (AttributeError, helm-selftest.py:688) — the admission measured end to end. - Gate 1,044 -> 1,141 lines (+97/-0; DIFF.txt 108 lines / ac8e52bb...), sha256 643e5387... -> 74aba348...; collector byte-identical to the Q34/Q35 pair (4e45021d..., 720 lines). - Live snapshot /root/.helm/data/snapshot.json 14,039 B / aa842b0f... / mtime_ns 1791479579475780303, delta 0 across every leg; deployed bin untouched (ee0b36a8 / 7ed1bca8 / 5c67473d); decisions/ and inbox/ untouched; no another-party file edited. Section 4 consequence: the adoption pair is now collector 4e45021d... + gate 74aba348... (superseding 643e5387...); the cp into /root/.helm/bin/ remains Alexander's. |
||
|
timmy
|
5fe58aafbe | Q20: the landing-evidence self-citation regress is broken by indirection, not by chasing it -- the record's own row and the check-in's own row defer to each other, the three revisions of the record are named with their bytes, and the stable artifacts (rows file, queue) keep their digests | ||
|
timmy
|
48bf86b93e | Q20: the record cites both of its own revisions (pre-fill 9dced5eb / 12,914 and post-fill e72062a3 / 13,062), the self-reference loop closed on the record rather than left circular, and the check-in landing table carries the same pair | ||
|
timmy
|
95dfbf37de |
Q20: landing evidence filled in on the record (readback table at 9a1de9a, post-push reads) and the Run 3 check-in appended (Did / Blocked / Next / Ask)
|
||
|
timmy
|
9a1de9a6ad |
Q20 DONE: excerpt fidelity class and placement for all 91 magazine entries (recoveries/excerpt-placement-audit.md + recoveries/excerpt-placement-rows.md)
Population: 91/91 magazine entries, no sampling -- 269 excerpts (87 entries x 3, 4 x 2). Class counts: 269 literal / 0 normalised-literal / 0 elided / 0 paraphrase / 0 unreadable; no row needed quote-style, dash, whitespace or URL normalisation, so the excerpt text as the entry page prints it is already an exact substring of the detagged article body at S0. Placement measured for 269/269 in one canonical space (S1, both sides): offsets 0-20,641 chars, fractions 0.0000-0.9472, mean 0.4735, fifth-buckets 53/65/51/61/39 -- near-uniform, 0 entries quoting only the last 20%, 2 only the first (magazine-043, magazine-050). Named extremes: magazine-057 widest spread 0.8923, magazine-027 narrowest 0.0094, magazine-019 highest mean 0.7905, magazine-050 lowest 0.0394. All 91 anchors are www.stackchainmagazine.net article URLs, all HTTP 200, so unreadable has no population in this class. Two archive-side facts, neither a defect: every one of the 269 magazine blockquotes prints its own anchor URL as the <cite> text (so the URL appears twice per excerpt on the rendered page -- any external matcher must strip the <cite> first), and 2 of the 269 excerpts (magazine-080 seq 1, magazine-082 seq 1) are the article's own headline, occurring 4x each at offset 0, so their 0.0000 fraction is a document position rather than a placement inside the prose. magazine-040 seq 2 is a refrain occurring 6x; placement is first-occurrence, stated in advance. Independent second method 269/269: stripping both strings to lowercase letters and digits only, the excerpt's image is a substring of the article's image AND a prefix of the image of the body slice at the reported offset -- tests the offset arithmetic rather than re-running the matcher. Cross-check against recoveries/excerpt-binding-audit.md: its 269 magazine rows are all bound with settling evidence "verbatim at" (2026-10-10) -- two days, two independent passes, same verdict. Limits stated: the detagged body includes site chrome, so fraction is a document-position measure not a position within the article prose; placement is first-occurrence (3 rows have more than one occurrence); 45 excerpts are under 40 characters (shortest 9, magazine-008 seq 2 "eat tacos") so placement is weak evidence of representativeness for those though the match is exact; byte counts and hashes are dated readings (2026-10-12T04:41-04:43Z). Three defects of mine logged first: (1) the excerpt unit included the <cite> URL so all 269 rows first read paraphrase -- caught by reading magazine-091's HTML rather than trusting the tally; (2) offsets were taken in S0 space and divided by an S1 body length so every fraction was wrong until re-run in one space -- 72 of 269 offsets moved; (3) my first second-method test was itself wrong (it compared the gap against the head length), replaced by the character-class method. No archive-side wording fix follows. Nothing deployed; decisions/ and inbox/ untouched. |
||
|
Merlin
|
dd0bc69061 |
Q35 DONE: the destination-rule guard is a precondition, not a report (recoveries/helm-precondition-gate.md, scratch /root/crucible/q35/).
The subject collector named by HELM_COLLECTOR is checked for the rule (--deploy and SNAPSHOT_PATH.resolve() in its source) at helm-selftest.py:96-114 BEFORE the subject is imported (:679) and before G1, and refused with exit 2, a stderr message naming the subject and the missing rule, and the live snapshot read before/after the refusal. Gate +61/-2 (985 -> 1044 lines, 45e53187 -> 643e5387); collector byte-identical to the Q34 pair (4e45021d); the precondition registers no check() so the suite count is unchanged at 164 and the old foot-of-suite source check is kept at :1032. Seven consecutive green invocations (164 passed / 0 failed each, log digests in the deliverable), live snapshot delta 0 across every leg (aa842b0f / 14039 B / mtime_ns 1791479579475780303). Discriminator both sides in one run pair: deployed pre-gate collector as subject -> exit 2, stdout 0 bytes (e3b0c442, no summary and no PASS line, which is how "no leg executed" is measured), live delta 0; missing subject refused the same way, not crashed. Mechanism probe from this tree (q35-mechanism.py, mech-probe.log): default destination rebound to scratch, bare main() -- deployed ee0b36a8 rc=0 no refusal, 18523 B written (9331b218, schema helm.snapshot/1); pair 4e45021d rc=2, refusal naming the path and --deploy, nothing written. Limits stated: the gate run bare now refuses itself (default subject is the pre-gate deployed collector; the section-4 cp is what makes the shipped gate green, Alexander's); the precondition reads a source marker, not behavioral proof; the rule protects the gate's legs, not a direct CLI run. Nothing deployed; decisions/ and inbox/ untouched. |