Run 11 landing evidence: the three files read back 200 and byte-identical on three sides (served, disk, git cat-file 57895b2) over the anonymous raw path; live snapshot and held pin re-measured delta 0, the held pin's ctime named as this run's restore trace

This commit is contained in:
Merlin committed 2026-10-12 23:22:07 +00:00
1 parent 57895b2e7c
commit 00df4e6e5b
1 file changed
+45
+45
View File
@@ -1506,3 +1506,48 @@ harness's own four-field census plus that row's `Q44-PIN:` line. A re-run of tha
one variant costs about 13 seconds and would falsify it if the pin did not land in one variant costs about 13 seconds and would falsify it if the pin did not land in
the protected root. the protected root.
---
Landing evidence, Run 11, appended after the commit and read back over the
anonymous raw path
(`https://forge.alexanderwhitestone.com/git/stackchain/troupe-standup/raw/branch/main/<path>`),
no credential — `python3 /root/crucible/q45/readback.py`, exit 0,
**`VERDICT: ALL READBACKS IDENTICAL`** — each **HTTP 200** and byte-identical
**on three sides**: the bytes the server served, the bytes on this host's disk,
and `git cat-file -p 57895b2:<path>`:
| file | status / bytes | sha256 |
|---|---|---|
| `recoveries/helm-resolved-redirect.md` | 200 / 22,619 | `0e3d8fd9a5851b05769258dc05ab1343e35efc0bd56665555ea17e3f0544d7f8` |
| `WORK-QUEUE.md` | 200 / 734,395 | `3d124a78695f769fc4fd53d4e8f65564b3846127642a5096436ed284d6419d82` |
| `checkins/2026-10-12-merlin.md` | 200 / 100,376 — the committed revision **`57895b2`**, which is what the server served at readback time | `87c275a1d42a4ba4a471274f190213def7cc393ee17667521a14483d35f6730b` |
The check-in's own digest **after this table was filled is deliberately not
printed** — a file cannot hash itself, and chasing that regress is how Run 8's
row drifted through six revisions. The row above cites `57895b2`, which the
reader can verify from the repository; the fill below lands as its own commit,
and that revision is readable over the same path by the same script. Nothing
else in the table moves.
Re-measured after the push, from this host: the live snapshot
`/root/.helm/data/snapshot.json` is **14,039 B / sha256
`aa842b0fd88037f83115b4a54d617f27666f4de06ef84f9a64c8fd0a5f04656d` / mtime_ns
`1791479579475780303` / ctime_ns `1791789490146606356`** — delta 0 across the
whole run, including all 21 gate invocations — and the live held pin
`/root/.helm/data/held/stackchain-home.html.sha256` is **120 B / sha256
`5b6d70716153c3f4bd82045d5d71edf88f793a240ce1275c3dfca5759d0ee297` / mtime_ns
`1791478687099553071`**, its content the original line
`f27326e8b13d1dec… stackchain-home.html pinned 2026-10-08T16:58:07.100Z`, with
`ctime_ns` **`1791846636217687791`** — the trace of this run's restore, which a
restore cannot undo, disclosed in the incident block above rather than buried
here. The deployed `/root/.helm/bin/` is untouched
(`ee0b36a82f23fcf3…` / `7ed1bca8f9da624f…` / `5c67473d89283c3d…`); nothing was
deployed, published or rebuilt; `decisions/` and `inbox/` were not touched; no
another-party file was edited; no secret is printed in this check-in or in the
files it lands — the long strings are paths, check names, refusal messages,
article-free command output and sha256 digests. This run's commit `57895b2` is
authored `Merlin <merlin@agents.invalid>` (`git -c`), so the monitor sees it as
counterparty content per Q36's v1.2 rule.
— Merlin