From 6954cc6e1f066ea0e888875b1a87ec1483f07cd8 Mon Sep 17 00:00:00 2001 From: Merlin Date: Tue, 13 Oct 2026 16:08:55 +0000 Subject: [PATCH] helm: run 18 landing evidence -- three-way byte-identical readback of recoveries/helm-home-channel-guard.md (13,173 B / 3f813ca2), WORK-QUEUE.md (897,771 B / e8da72cf) and the check-in's c559d33 revision over the anonymous raw path; live state delta 0 on bytes/sha256/mtime; deployed bin untouched; no secret printed --- checkins/2026-10-13-merlin.md | 39 +++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/checkins/2026-10-13-merlin.md b/checkins/2026-10-13-merlin.md index a3db7d8..dd22c77 100644 --- a/checkins/2026-10-13-merlin.md +++ b/checkins/2026-10-13-merlin.md @@ -894,3 +894,42 @@ Alexander: nothing blocking. The standing items, consolidated: (a) rule on the * puts Q31–Q52's protection into production (the deployed gate today has no subject-selection path at all); (b) the **`manifest_match` pin** decision (stale since 2026-10-08); (c) the **Q13 publication call** (item 13's decided note — escalate, do not edit the live page — still controls over its `proposed_action`). + +--- + +### Run 18 landing evidence + +Read back over the anonymous raw path with no credential +(`https://forge.alexanderwhitestone.com/git/stackchain/troupe-standup/raw/branch/main/`) +and byte-compared on three sides — the bytes the server served, the bytes on disk, and +`git cat-file -p c559d33:` — by `python3 /root/crucible/q52/readback_q52.py`, exit 0, +`VERDICT: ALL READBACKS IDENTICAL`, artifact `out/Q52-READBACK.json`, read at +2026-10-13 ~16:1xZ after the push `0c190a4..c559d33`: + +| file | HTTP / bytes | sha256 (served = disk = git) | +|---|---|---| +| `recoveries/helm-home-channel-guard.md` | 200 / 13,173 | `3f813ca23202590c675f7ac7587f0d5e7d8b0ff9ee9f4f0711996530a2d6d7db` | +| `WORK-QUEUE.md` | 200 / 897,771 | `e8da72cff24460ec…` | +| `checkins/2026-10-13-merlin.md` | 200 / 65,145 | `d89b2189e69ba6ff…` | + +The check-in's own row cites the committed revision `c559d33`, which is what the server +served at readback time and what `git cat-file -p c559d33:checkins/2026-10-13-merlin.md` +reproduces locally — a file cannot hash itself, so this row cites the revision it was +written against; this fill lands as its own commit. + +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`** and the held pin +`/root/.helm/data/held/stackchain-home.html.sha256` is **120 B / +`5b6d70716153c3f4bd82045d5d71edf88f793a240ce1275c3dfca5759d0ee297` / mtime_ns +`1791478687099553071`** — delta 0 on bytes, sha256 and mtime_ns across the whole run; +the deployed `/root/.helm/bin/` is untouched (`ee0b36a8…` / `7ed1bca8…` / `12570786…` / +`73869998…`). Nothing was deployed, published, rebuilt or re-run beyond the measurements +above; `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 gate +check names, refusal messages, file paths and sha256 digests. This run's commit is +authored `Merlin ` (`git -c`), so the monitor sees it as +counterparty content per Q36's v1.3 rule. + +— Merlin