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.
This commit is contained in:
Merlin committed
1 parent
b31c727f77
commit
eec3ff38e7
3 files changed
+252
No files matched your search
@@ -8153,3 +8153,64 @@ load-bearing by measurement from both sides**, which reading the artifacts canno
|
||||
set is empty and a task invented to fill it would be invented work.
|
||||
|
||||
— Timmy (the pipe)
|
||||
|
||||
|
||||
---
|
||||
|
||||
**Q45 §9 (Helm lane) — Run 23: the record's four numbers corrected and the digests re-verified on disk.
|
||||
2026-10-14 (Merlin).** No new item was opened and no queue item was taken: Q42 is zephyrus-sparkborn's, Q52
|
||||
is Mercury's, Q53 is the career lane held for Alexander, and the Helm executable set is empty — measured by
|
||||
this lane in Run 22 and independently by the pipe in reply 45 §6, so the next Helm unit remains a decision,
|
||||
not a task. The unit taken is the one reply 44 (`0f9ac82`) and reply 45 (`1ccf944`) handed back: four byte
|
||||
figures and one identifier in `recoveries/helm-pwdir-channel-refusal.md` were wrong, and the wrong pairing
|
||||
sat behind the §4 adoption `cp` cite.
|
||||
|
||||
- **Cause, mine:** `rename_q55.py` renames `Q55` → `Q45S9` (+2 chars per occurrence) and changed the gate's
|
||||
bytes **after** the byte figures were taken and **before** the digests were computed, so the record
|
||||
published a **post-rename digest beside pre-rename bytes**. Measured this run from disk and the
|
||||
interpreter, not from either reply: `/root/crucible/q55/run23_verify.py` →
|
||||
`out/R23-VERIFY.json` (2,685 B / sha256 `1bb9cd78e394d25ccea46a5d38c67b598d694c49462269911f357c3e858fc0c5`,
|
||||
`generated_at 2026-10-14T03:36:23.456605839Z`).
|
||||
- **The corrections, all in the record's own append (nothing above the anchor edited):** armed gate
|
||||
**143,385 → 143,389 B**; twin **143,416 → 143,422 B**; twin − armed **31 → 33 B**; insertion block
|
||||
**+3,020 → +3,024 B / +58 lines**; the differing line's identifier **`if _q45S9_pwd_sites:` →
|
||||
`if _q55_pwd_sites:`** (line 442; `_q45S9_pwd_sites` occurs **0** times in both gates, `_q55_pwd_sites` at
|
||||
**:435, :442, :451** armed and **:435, :451** twin). Both gates **2,735 lines / 126 `check("` registrations**;
|
||||
`Q55` (upper) **0** in both, `Q45S9` **2** / **3**. The reply's *"3,043 minus 23"* derivation is **wrong in
|
||||
kind**, not by arithmetic: the anchor is the insertion point, so the block is 3,024 B post-rename and
|
||||
3,020 B pre-rename.
|
||||
- **The digests hold, which is the load-bearing half:** armed
|
||||
`cd43284ff009d1cceb3aaa6a65b701d1076eaf801e32b705672601b4122b746a` and twin
|
||||
`8adad99bdc872ecd09ddea88ae55b5fc55a3886571ffaa5f49a053b52430586d` are unchanged by the correction, so
|
||||
**the §4 `cp` pair — collector `4e45021d…` + gate `cd43284ff009…` — is sound and needs no re-cite**. It was
|
||||
never at risk: only the byte figures travelled with the pre-rename file.
|
||||
- **Gate re-run once on the real collector** (`HELM_COLLECTOR=/root/crucible/q48/helm-collect.py`,
|
||||
`4e45021d80395d3f…` / 29,954 B): **rc 0, `helm-selftest: 176 passed, 0 failed`, `ALL GATES PASS`, 14,044 B
|
||||
stdout / sha256 `585e0e4b0508b565a18ca52cde3c464b9f92673b8fad538a12a33fd8a07131c1` / 1,216 B stderr,
|
||||
12.2 s**, ` PASS Q52 …` present. **Live delta `{}` on bytes, sha256, mtime_ns AND ctime_ns** for both
|
||||
live objects (snapshot 14,039 B / `aa842b0fd88037f8…` / `1791479579475780303`; held pin 120 B /
|
||||
`5b6d70716153c3f4…` / `1791478687099553071`; ctime `1791941985122465693` / `1791941985123465776`, unmoved —
|
||||
Run 22's witness-restore trace, disclosed there).
|
||||
- **Reply 45 §5.1's finding closed:** the `c4addca` readback is no longer hostage to a later overwrite. New
|
||||
instrument `/root/crucible/q55/readback_r23.py` reads **`/raw/commit/<rev>/<path>`**, so the served body is
|
||||
the body *at that revision*; artifact `out/R23-READBACK.json`. **6 rows (`c4addca`, `b31c727`), 6 × served
|
||||
= git**: record 14,808 / `d4c381f7…` at both revisions (byte-identical), queue `c4addca` 951,756 /
|
||||
`d8f54086…` vs `b31c727` 957,453 / `d60d6dee…`, check-in 9,279 / `2d815c65…` vs 10,499 / `eae1c6b2…` —
|
||||
the two `served = disk false` rows at `c4addca` are the pipe's own three appends since, named and dated.
|
||||
`head_at_read` = `b31c727f77d1c50cdb9019b915170a47684351c8`.
|
||||
- **Deliverable:** `recoveries/helm-pwdir-channel-refusal.md` **14,808 B / `d4c381f7…` → 20,820 B /
|
||||
`8d67248fd9acb73cb5cb0c39a5fb774232c02730f97e998a5f3292d54efbbcc1`** (+6,012 B, append-only, anchor count
|
||||
asserted `== 1`, trailing newline asserted before and after on the written file). Check-in
|
||||
`checkins/2026-10-14-merlin.md` 10,499 / `eae1c6b2…` → 18,265 / `45223797da62ae9c…` (+7,766 B, Run 23
|
||||
section). This block does not cite the queue's own post-append digest; the readback artifact carries the
|
||||
durable rows and names its revision.
|
||||
- **One defect of mine, logged here:** the first `run23_verify.py` extracted the Q52 line with
|
||||
`startswith("PASS Q52")`, which never matches the two-space rendering — the lane's own logged defect,
|
||||
reproduced by its author on a fresh artifact and corrected to a regex before the run was recorded.
|
||||
- Nothing deployed (`HELM_COLLECTOR` count 0 in `/root/.helm/bin/helm-selftest.py` — Q40 stands, so none of
|
||||
Q31–Q45 §9 is in production), `decisions/` and `inbox/` untouched, no another-party file edited, no secret
|
||||
printed. Standing human gates unchanged: the §4 `cp` (collector `4e45021d…` + gate `cd43284ff009…`), the
|
||||
`manifest_match` pin stale since 2026-10-08, Q13's publication call, Q9's checksum handover, Q19's
|
||||
onboarding. **No new item opened.**
|
||||
|
||||
— Merlin (Run 23)
|
||||
@@ -149,3 +149,119 @@ agree by construction rather than by one chasing the other. Live state re-read a
|
||||
avail of 154; the q55 tree holds 0 sandboxes.
|
||||
|
||||
— Merlin (Run 22, landing fill)
|
||||
|
||||
|
||||
---
|
||||
|
||||
## Run 23 — record correction: the four numbers, and a readback that survives its own overwrite
|
||||
|
||||
### Did
|
||||
|
||||
No unclaimed queue item was executable this run, and I did not invent one: **Q42 is zephyrus-sparkborn's,
|
||||
Q52 is Mercury's, Q53 is the career lane held for Alexander**, and both this lane (Run 22) and the pipe
|
||||
(`1ccf944`, reply 45 §6) have independently measured the Helm executable set empty — the next Helm unit is
|
||||
a decision, not a task. So the unit is the one reply 44 (`0f9ac82`) and reply 45 (`1ccf944`) handed back:
|
||||
**four byte figures and one identifier in my own Run 22 record are wrong**, and the wrong pairing sits
|
||||
behind the §4 adoption `cp` cite, which is the one thing standing between Q31–Q45 §9 and production.
|
||||
|
||||
**Deliverable:** `recoveries/helm-pwdir-channel-refusal.md` **14,808 B → 20,820 B / sha256
|
||||
`8d67248fd9acb73cb5cb0c39a5fb774232c02730f97e998a5f3292d54efbbcc1`** (+6,012 B, **append-only** — nothing
|
||||
above the anchor edited, anchor count asserted `== 1` before the write, trailing newline asserted before
|
||||
and after **on the written file**).
|
||||
|
||||
**Cause, and it is mine.** `rename_q55.py` renames `Q55` → `Q45S9` (+2 chars per occurrence) and changed the
|
||||
gate's bytes **after** the byte figures were taken and **before** the digests were computed, so the record
|
||||
published a **post-rename digest beside pre-rename bytes**. Measured this run from disk and the interpreter,
|
||||
not from either reply: instrument `/root/crucible/q55/run23_verify.py`, artifact `out/R23-VERIFY.json`
|
||||
(**2,685 B / sha256 `1bb9cd78e394d25ccea46a5d38c67b598d694c49462269911f357c3e858fc0c5`**,
|
||||
`generated_at 2026-10-14T03:36:23.456605839Z`).
|
||||
|
||||
$ cd /root/crucible/q55 && python3 run23_verify.py
|
||||
armed 143389 cd43284ff009d1cceb3aaa6a65b701d1076eaf801e32b705672601b4122b746a 2735 126
|
||||
twin 143422 8adad99bdc872ecd09ddea88ae55b5fc55a3886571ffaa5f49a053b52430586d 2735 126
|
||||
twin-armed 33
|
||||
sites [435, 442, 451] [435, 451] q45S9: 0 0
|
||||
differing [{"line": 442, "armed": "if _q55_pwd_sites:",
|
||||
"twin": "if False: # Q45S9 disarmed: the pwd refusal is cut"}]
|
||||
rc 0 stdout 14044 stderr 1216 12.2s
|
||||
verdict ['helm-selftest: 176 passed, 0 failed']
|
||||
q52 [" PASS Q52 the subject's home-directory reads resolve inside the sandbox when the subject reads the home database"]
|
||||
live_moved [] ctime_moved []
|
||||
|
||||
| figure | Run 22 said | measured | status |
|
||||
|---|---|---|---|
|
||||
| armed gate bytes | 143,385 | **143,389** | **corrected** |
|
||||
| armed gate sha256 | `cd43284ff009…b746a` | **identical** | **holds — the §4 `cp` cite is sound** |
|
||||
| twin bytes | 143,416 | **143,422** | **corrected** |
|
||||
| twin sha256 | `8adad99bdc87…86d` | **identical** | holds |
|
||||
| twin − armed | 31 B | **33 B** | **corrected** |
|
||||
| insertion block | +3,020 B / +58 lines | **+3,024 B / +58 lines** | **corrected** |
|
||||
| differing line's identifier | `if _q45S9_pwd_sites:` | **`if _q55_pwd_sites:`** (line 442) | **corrected** |
|
||||
|
||||
Both gates: **2,735 lines / 126 `check("` registrations / trailing newline true**; `Q55` (upper) occurs **0**
|
||||
times in both and `Q45S9` **2** (armed) / **3** (twin — the third is the twin's own cut comment), so the
|
||||
rename is total. `_q45S9_pwd_sites` **0** in both; `_q55_pwd_sites` at **:435, :442, :451** armed and
|
||||
**:435, :451** twin — 3 vs 2 sites, which *is* the single cut line and nothing else. The reply's
|
||||
*"3,043 minus 23"* derivation is **wrong in kind**, not wrong by arithmetic: the anchor is the insertion
|
||||
point, so the block is 3,024 B post-rename and 3,020 B pre-rename, and the subtraction only appears to
|
||||
explain it.
|
||||
|
||||
**The gate re-run once on the real collector** (`HELM_COLLECTOR=/root/crucible/q48/helm-collect.py`, subject
|
||||
sha256 `4e45021d80395d3f03fc58d7e99610e3c1c0d2fcf9c85f1db50b16cfd2043c6c`, 29,954 B): **rc 0,
|
||||
`helm-selftest: 176 passed, 0 failed`, `ALL GATES PASS`, 14,044 B stdout / sha256
|
||||
`585e0e4b0508b565a18ca52cde3c464b9f92673b8fad538a12a33fd8a07131c1` / 1,216 B stderr, 12.2 s**. **Live delta
|
||||
`{}` on bytes, sha256, mtime_ns AND ctime_ns** for both live objects — snapshot 14,039 B /
|
||||
`aa842b0fd88037f8…` / mtime_ns `1791479579475780303`; held pin 120 B / `5b6d70716153c3f4…` / mtime_ns
|
||||
`1791478687099553071`; ctime `1791941985122465693` / `1791941985123465776`, **unmoved** this run (it is Run
|
||||
22's witness-restore trace, disclosed there and not re-created here).
|
||||
|
||||
**The readback now survives its own overwrite — reply 45 §5.1's finding, closed.** `out/Q55-READBACK.txt`
|
||||
on disk is the `8d105e9` read, so the `c4addca` read it was written to hold could not be re-derived from its
|
||||
own artifact. New instrument `/root/crucible/q55/readback_r23.py`, artifact `out/R23-READBACK.json`, reading
|
||||
**`/raw/commit/<rev>/<path>`** so the served body is the body *at that revision*, permanently:
|
||||
|
||||
$ cd /root/crucible/q55 && python3 readback_r23.py c4addca b31c727
|
||||
c4addca recoveries/helm-pwdir-channel-refusal.md 200 14808 d4c381f713e9fe95 git=True disk=True
|
||||
c4addca WORK-QUEUE.md 200 951756 d8f54086edbcbbc9 git=True disk=False
|
||||
c4addca checkins/2026-10-14-merlin.md 200 9279 2d815c65542f7ea2 git=True disk=False
|
||||
b31c727 recoveries/helm-pwdir-channel-refusal.md 200 14808 d4c381f713e9fe95 git=True disk=True
|
||||
b31c727 WORK-QUEUE.md 200 957453 d60d6dee32376ef2 git=True disk=True
|
||||
b31c727 checkins/2026-10-14-merlin.md 200 10499 eae1c6b2c62983f0 git=True disk=True
|
||||
head_at_read b31c727f77d1c50cdb9019b915170a47684351c8
|
||||
|
||||
**6 rows, 6 × served = git.** The two `served = disk false` rows at `c4addca` are the pipe's own three
|
||||
appends since that revision (queue 951,756 → 957,453 B / `d8f54086…` → `d60d6dee…`; check-in 9,279 →
|
||||
10,499 B / `2d815c65…` → `eae1c6b2…`) — named and dated, not a serve failure. The record is
|
||||
**byte-identical at both revisions** (`d4c381f7…`), which is what makes today's corrected figures the first
|
||||
change to this file since Run 22 landed.
|
||||
|
||||
**A defect of mine, hit inside this run and logged here rather than in a reply:** the first version of
|
||||
`run23_verify.py` extracted the Q52 line with `startswith("PASS Q52")`, which never matches the two-space
|
||||
rendering — the lane's own logged defect, reproduced by its author on a fresh artifact, corrected to a regex
|
||||
before the run was recorded. The measured line is quoted above.
|
||||
|
||||
### Blocked
|
||||
|
||||
Nothing blocks the lane. The standing human gates are unchanged and none is new: the **§4 adoption `cp` —
|
||||
now collector `4e45021d…` + gate `cd43284ff009…`, whose digests this run re-verified against the files on
|
||||
disk**, the **`manifest_match` pin** (stale since 2026-10-08), **Q13's publication call** (item 13's decided
|
||||
note controls over its `proposed_action`), **Q9's checksum handover**, **Q19's onboarding**. Q42 is
|
||||
zephyrus-sparkborn's, Q52 is Mercury's, Q53 is the career lane's. Nothing deployed this run: `grep -c
|
||||
HELM_COLLECTOR /root/.helm/bin/helm-selftest.py` = **0**, so Q40 stands and none of Q31–Q45 §9 is in
|
||||
production.
|
||||
|
||||
### Next
|
||||
|
||||
1. Nothing is owed to the pipe from this run: reply 45 asks nothing of me, and both replies' corrections are
|
||||
now applied to the artifact they correct.
|
||||
2. **No new item opened.** The Helm executable set is empty and the queue's genuinely open items belong to
|
||||
other lanes or to Alexander; the next Helm unit is the `cp` decision.
|
||||
|
||||
### Ask
|
||||
|
||||
Alexander's, unchanged: **(a)** the §4 adoption `cp` — collector `4e45021d…` + gate
|
||||
`cd43284ff009d1cceb3aaa6a65b701d1076eaf801e32b705672601b4122b746a` (143,389 B / 2,735 lines / 126
|
||||
registrations), re-verified on disk this run; **(b)** the `manifest_match` pin, stale since 2026-10-08;
|
||||
**(c)** the Q13 publication call. No ask of the pipe.
|
||||
|
||||
— Merlin (Run 23)
|
||||
@@ -203,3 +203,78 @@ Nothing from any counterparty. The next Helm unit remains a decision, not a task
|
||||
above, the `manifest_match` pin (stale since 2026-10-08), Q13's publication call, Q9's checksum
|
||||
handover, Q19's onboarding — all Alexander's. Q42 is zephyrus's; Q52 is Mercury's; Q53 is the career
|
||||
lane, held for Alexander. A task invented to fill the lane would be invented work.
|
||||
|
||||
|
||||
---
|
||||
|
||||
## Run 23 -- the four numbers corrected, and the readback made durable (2026-10-14)
|
||||
|
||||
**Why this append exists.** reply 44 (`0f9ac82`) and reply 45 (`1ccf944`) returned four byte figures in
|
||||
this record that are wrong, and one identifier. The cause is mechanical and it is mine: the `Q55` ->
|
||||
`Q45S9` rename (`rename_q55.py`, `t.replace("Q55", "Q45S9")`, **+2 chars per occurrence**) changed the
|
||||
gate's bytes **after** the byte figures above were taken and **before** the digests were computed, so the
|
||||
pair published above is a **post-rename digest beside pre-rename bytes**. The pipe already carried the
|
||||
correction into `WORK-QUEUE.md`; this file, which is the artifact Alexander would `cp` from, did not have
|
||||
it. Measured this run from disk and the interpreter, not from either reply: instrument
|
||||
`/root/crucible/q55/run23_verify.py`, artifact `out/R23-VERIFY.json` (**2,685 B / sha256
|
||||
`1bb9cd78e394d25ccea46a5d38c67b598d694c49462269911f357c3e858fc0c5`**, `generated_at
|
||||
2026-10-14T03:36:23.456605839Z`).
|
||||
|
||||
| figure | this record said | measured (`out/R23-VERIFY.json`) | status |
|
||||
|---|---|---|---|
|
||||
| armed gate `helm-selftest-q55.py` bytes | 143,385 | **143,389** | **corrected** |
|
||||
| armed gate sha256 | `cd43284ff009d1cceb3aaa6a65b701d1076eaf801e32b705672601b4122b746a` | **identical** | **holds -- the §4 `cp` cite is sound** |
|
||||
| disarmed twin bytes | 143,416 | **143,422** | **corrected** |
|
||||
| twin sha256 | `8adad99bdc872ecd09ddea88ae55b5fc55a3886571ffaa5f49a053b52430586d` | **identical** | holds |
|
||||
| twin - armed | 31 B | **33 B** | **corrected** |
|
||||
| insertion block | +3,020 B / +58 lines | **+3,024 B / +58 lines** (`armed_delta_bytes_vs_base_126`) | **corrected** |
|
||||
| the differing line's identifier | `if _q45S9_pwd_sites:` | **`if _q55_pwd_sites:`** (line 442) | **corrected** |
|
||||
|
||||
Both gates: **2,735 lines / 126 `check("` registrations / trailing newline true**, and the rename is total
|
||||
in the only sense that matters here -- `Q55` (upper) occurs **0** times in both, `Q45S9` occurs **2** in the
|
||||
armed gate and **3** in the twin (the third is the twin's own cut comment). `_q45S9_pwd_sites` occurs **0**
|
||||
times in both; `_q55_pwd_sites` sits at **:435, :442, :451** in the armed gate and **:435, :451** in the
|
||||
twin -- 3 vs 2 sites, which is the twin's single cut line and nothing else. The twin's line 442 verbatim:
|
||||
`if False: # Q45S9 disarmed: the pwd refusal is cut`. The **`3,043 minus 23`** derivation in the reply is
|
||||
**wrong in kind**, not wrong by arithmetic: the anchor is the insertion point, so the block is 3,024 B
|
||||
post-rename and 3,020 B pre-rename, and the subtraction only appears to explain it.
|
||||
|
||||
**The gate was re-run once on the real collector, with a four-stamp live guard around it**
|
||||
(`HELM_COLLECTOR=/root/crucible/q48/helm-collect.py`, subject sha256 `4e45021d80395d3f…`, 29,954 B):
|
||||
**rc 0, `helm-selftest: 176 passed, 0 failed`, `ALL GATES PASS`, 14,044 B stdout / sha256
|
||||
`585e0e4b0508b565a18ca52cde3c464b9f92673b8fad538a12a33fd8a07131c1` / 1,216 B stderr, 12.2 s**, and
|
||||
` PASS Q52 the subject's home-directory reads resolve inside the sandbox when the subject reads the home
|
||||
database` -- two spaces, which is the rendering the filter must match. **Live delta `{}` on bytes, sha256,
|
||||
mtime_ns AND ctime_ns** for both live objects (snapshot 14,039 B / `aa842b0fd88037f8…` /
|
||||
`1791479579475780303`; held pin 120 B / `5b6d70716153c3f4…` / `1791478687099553071`; ctime
|
||||
`1791941985122465693` / `1791941985123465776` on both, **unmoved** -- the restore trace from Run 22's
|
||||
witness cells, disclosed above, not re-created here).
|
||||
|
||||
**The readback is now durable, which closes reply 45 §5.1.** `out/Q55-READBACK.txt` on disk is the
|
||||
`8d105e9` read, so the `c4addca` read it was written to hold could not be re-derived from its own
|
||||
artifact. New instrument `/root/crucible/q55/readback_r23.py`, artifact `out/R23-READBACK.json`, reading
|
||||
**`/raw/commit/<rev>/<path>`** so the served body is the body *at that revision* forever:
|
||||
|
||||
| rev | file | HTTP / bytes | sha256 | served = git | served = disk |
|
||||
|---|---|---|---|---|---|
|
||||
| `c4addca` | `recoveries/helm-pwdir-channel-refusal.md` | 200 / 14,808 | `d4c381f713e9fe95beefbd14a93220ab4049625f280c116e656419f3e11b7b89` | true | true |
|
||||
| `c4addca` | `WORK-QUEUE.md` | 200 / 951,756 | `d8f54086edbcbbc96e39533d7b6dcf0e9effff108b596ed18685b03d1045e1db` | true | false (the pipe's three appends since) |
|
||||
| `c4addca` | `checkins/2026-10-14-merlin.md` | 200 / 9,279 | `2d815c65542f7ea2722865b47fd19b0fbfcfe688ecfba97e03c84ea8c31ad132` | true | false (same) |
|
||||
| `b31c727` (head at read) | record | 200 / 14,808 | `d4c381f7…` | true | true |
|
||||
| `b31c727` | `WORK-QUEUE.md` | 200 / 957,453 | `d60d6dee32376ef2…` | true | true |
|
||||
| `b31c727` | `checkins/2026-10-14-merlin.md` | 200 / 10,499 | `eae1c6b2c62983f0444b44ba1cc2b9233537374e4382a243c3981636fa451731` | true | true |
|
||||
|
||||
`head_at_read` = `b31c727f77d1c50cdb9019b915170a47684351c8`. **6 rows, 6 × served = git**; the two
|
||||
`served = disk false` rows are the pipe's own appends, named and dated, not a serve failure. The record
|
||||
itself is **byte-identical at both revisions** (`d4c381f7…`), which is what makes the corrected figures
|
||||
above the first change to this file since Run 22 landed.
|
||||
|
||||
**One defect of mine, logged here rather than in the reply, because I hit it inside this run and fixed
|
||||
it:** the first version of `run23_verify.py` extracted the Q52 line with `startswith("PASS Q52")`, which
|
||||
never matches the two-space rendering -- the lane's own logged defect, reproduced by its author on a fresh
|
||||
artifact and corrected to a regex before the run was recorded. The measured line is quoted above.
|
||||
|
||||
**Nothing else moved.** No gate deployed (`HELM_COLLECTOR` count 0 in `/root/.helm/bin/helm-selftest.py`,
|
||||
so Q40 stands and none of Q31-Q45 §9 is in production), `decisions/` and `inbox/` untouched, no
|
||||
another-party file edited, no secret printed. This block does not cite this record's own post-append
|
||||
digest; the readback artifact above is the durable row and it names its revision.
|
||||
Reference in new issue
Block a user