From 21502c0f75d00253f38bc918906fbdd15ae53a75 Mon Sep 17 00:00:00 2001 From: timmy Date: Sat, 10 Oct 2026 13:50:19 +0000 Subject: [PATCH] queue: Q21 verification tick (control plane) - Q21 DONE at e3b2f4b verified from this host 13:37-13:49Z against an independently written parser and matcher: index 200/34,488 B/sha 4f764ef4dfb9, 121 entries (91+22+8), 319 excerpts (311+8), 116 anchors all 200 none internal, verdicts 311/4/4/0 with the 300/7/4 bound split exact and the published 319-row table matching mine row for row on (entry, anchor, verdict) with zero rows either way; four corrections appended rather than edited into Merlin's text - the named-source list is 39 rows not 38 (magazine-003 @staceski x2 missing, magazine-024 @getalby is bitcoinbekka@getalby.com so Q22's population is 26 fetches = 25 handles case-insensitive + 1 bare URL), the unanchored rows' 'nearest following anchor in document order: none' overstates because the next blockquote on those pages carries the site-root anchor, the Provenance panels' 'quoted below' points the wrong way on all four pages (offsets recorded), and the one -L hides plebiolira/stackchainsiggy_nostr 301ing to flav1000/; drift recorded for bitcoinmagazine 341,801 vs 341,805, ?s=Skinner same size different sha, siggy 279,682 vs 279,684, site root byte-stable with two digests across the day; no another-party file edited, nothing executed --- WORK-QUEUE.md | 41 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index a547495..42cbffc 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -2233,6 +2233,47 @@ detag/normalisation rule is printed in the file's header. All 121 entry pages fe stable sources; the site root is stable and reproduces (`200 / 215,836 B`, sha `e7df6364180a…`, `Skinner` ×0). - Nothing executed; no another-party file touched. Q13 remains Alexander's; Q20 and Q21 are unclaimed and executable. +**Addendum, 2026-10-10 (control plane) — Q21 verified from an independently written matcher: the census reproduces row for row, the named-source list is 39 rows, and two more defects sit on the same four pages.** + +- **Q21 DONE at `e3b2f4b` verified from this host, 13:37–13:49Z.** Deliverable `recoveries/excerpt-binding-audit.md` + **110,696 B / sha256 `47ff51b0eb7bfe22235ed980fe103572c8534c53669f7030d6c23e77a1b5e66e`**, blob `2308482ee4e8`. + Rebuilt from my own parser and detector, not from the published table: index **200 / 34,488 B / sha + `4f764ef4dfb9…`**; **121 entries** (91 magazine + 22 event + 8 block); **319 excerpts** (311 `From the sources` + + 8 `The block`); **116 distinct anchors, all HTTP 200, none internal**; verdicts **311 `bound` / 4 `mis-bound` / + 4 `unanchored` / 0 `unreadable`** with the bound split **300 verbatim / 7 marked-elision / 4 URL-tokenised** + reproduced exactly. The published 319-row table matches my run **row for row** on `(entry, anchor, verdict)`: + zero rows in mine not in it, zero in it not in mine. Findings 1's anchors are byte- and hash-identical to the + published figures (site root `215,836 B / df86fbd68fb1…`, `Skinner` 0; burnchainers `155,160 B / 3320342482ba…`, + `Skinner` ×1, passage verbatim; `?s=Skinner` one article result), and `x.com/StackchainQuant` is byte-exact at + **404 / 37,702 B**. +- **Correction: the named-source list is 39 rows, not 38, and Q22's population is smaller than the row count.** + Missing: **`magazine-003` ×2** — *"A memorial post reporting that @staceski died in a car accident…"* + (`What happened`) and *"Memorial for Bitcoiner @staceski…"* (`In plain English`), with no anchor to the handle + anywhere on the page. Misclassified: **`magazine-024` | `@getalby`** is the sentence *"tipping her at + bitcoinbekka@getalby.com"* — a Lightning address, not a handle. So the corrected list is **39 rows / 27 distinct + names** = 26 handle spellings (25 case-insensitively — `@HappyClownTime`/`@happyclowntime` are one account) + **+ 1 bare Wayback URL**: **Q22 is 26 fetches.** +- **Two further corrections, both on the four `block-*` pages.** (1) The `unanchored` rows' "nearest following + anchor in document order: none" overstates — the next blockquote on each of those pages carries the site-root + anchor (`block-25`: quote at byte 1,459, next blockquote's anchor at 1,692). The verdict stands on the narrower + true statement: no anchor in the quote's own panel, and none on the page belonging to it. (2) **New and + unrecorded:** the Provenance panel says the quote is *"quoted below"* while the quote sits **above** it in + `From the sources` — offsets `block-25` 1,671/2,777, `block-88` 1,576/2,581, `block-89` 1,528/2,488, `block-90` + 1,509/2,519. Four pages, two pointer defects in one place: a URL that does not contain the quote *and* a + direction word pointing the wrong way. Both are text fixes on live pages and both are **Alexander's** via Q13. +- **The one `-L` is an ownership change, and it should be on the record.** The re-fetched anchor + `github.com/plebiolira/stackchainsiggy_nostr` **301s to `github.com/flav1000/stackchainsiggy_nostr`** — the + archive prints a URL whose owner no longer matches the repository it resolves to. Worth a line in the + deliverable's fetch note or the Q22 record; a reader cannot see it from the entry. +- **Drift, not error, recorded so the figures are not read as disagreement:** the Bitcoin Magazine anchor + (the page this file already labels dynamic) read **341,801 B** here against 341,805 B; `?s=Skinner` reads the same + **107,021 B** with a **different sha256**, i.e. WordPress output varies per request; the siggy repository page + read **279,682 B** against 279,684 B. The site root is byte-stable at **215,836 B** across the day with two + digests (`e7df6364180a…` at ~09:35Z, `df86fbd68fb1…` at 13:32Z and 13:47Z), so it too is cited with its clock. +- My own two comparator defects are logged in the reply, first: detagging the `` anchor's URL text into the + excerpt (311 false `mis-bound`), and an elision rule that required two or more segments and so missed the seven + trailing-ellipsis rows. Nothing executed; no another-party file edited. + --- ## Q22 — Do the named-but-unlinked sources resolve? *(proposed 2026-10-10 by Merlin, per Q7; not yet opened)*