From e71bb39d19365ce0a48749213a8843e17d56c5ca Mon Sep 17 00:00:00 2001 From: timmy Date: Sat, 10 Oct 2026 20:19:54 +0000 Subject: [PATCH] queue: withdraw our own "stable source" claim about the site root (three digests at two sizes today) The tick above corrected Merlin's check-in sentence but left our earlier claim standing: this file calls https://www.stackchainmagazine.net/ "stable" and "byte-stable at 215,836 B across the day", using it as the contrast to the dynamic Bitcoin Magazine page. It is not stable across the day. Three digests at two sizes today: e7df6364180a and df86fbd68fb1 both at 215,836 B, then 217,162 B / 9a5ee1328d4a, read twice from this host at 20:19Z with identical results - so it moves between hours, not between requests. Root byte and hash figures are dated readings, like the Bitcoin Magazine page's, never identifiers. The stable contrast is /stackchain/blocks/: 34,488 B / 4f764ef4dfb9, re-read twice at 20:19Z and unchanged all day. Also verified this tick and unchanged: docs/q13-fix-pack.md 32,942 B with 25 distinct clause ids (A1-J1) and the pack's 31 deltas; docs/q13-fix-pack/apply_fix_pack.py 25,361 B, unrun; the build tree at its before-hashes (blocks.json 63c9cee6103a, build_blocks.py 97fedb5dd5e8) with 0 files newer than 18:00. --- WORK-QUEUE.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index 866592d..b737996 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -2760,6 +2760,14 @@ finished it. `9a5ee132…`**, a third digest today. (3) The printed clock window (*"~18:40–19:1x UTC"* in the check-in, *"~18:5x UTC"* in §1) precedes the run's own artifact stamps (**19:55–20:08Z**); §1's live-page clock line should read ~19:5xZ. +- **Correction (4), to our own record: the *stable source* claim about the site root is withdrawn.** Lines above + in this file call `https://www.stackchainmagazine.net/` *stable* and *"byte-stable at 215,836 B across the day"*, + and use that as the contrast to the dynamic Bitcoin Magazine page. It is **not** stable across the day: **three + digests at two sizes today** — `e7df6364180a…` and `df86fbd68fb1…`, both at 215,836 B, then + **217,162 B / `9a5ee1328d4a…`**, read twice from this host at 20:19Z with identical results (so it is not + per-request noise — it moves between hours, not between calls). Treat the root's byte and hash figures as + **dated readings**, exactly like the Bitcoin Magazine page's, never as identifiers. The stable contrast is + `/stackchain/blocks/`: **34,488 B / `4f764ef4dfb9…`**, re-read twice at 20:19Z and unchanged all day. - **One partial recorded, not scored.** The item's step list asks for the staging *"the `091` way (EDITS/ record + unrun apply script + revert command + emitted-file blast radius)"*. The last three are present; the `EDITS/` record covers `D1` only (the 2026-09-26 file, re-run in check mode rather than duplicated) and the