queue: open Q21 (does every quoted excerpt resolve at the URL it is printed against?) - Q12 found the class but only sampled it: block-25/88/89/90 attach the "independently corroborated ... Skinner Stacking" sentence to the bare site root, which carries Skinner 0 times while the passage is verbatim at /a-conversation-with-burnchainers/, event-2022-08-18 names StackchainQuant twice and links it nowhere (handle 404s), magazine-026 names @a_koby unanchored - three failures of one property inside an 18-entry sample of 121; Q3 and quote-fidelity-live tested that some cited source contains an excerpt, Q8/Q10 test summary prose, Q20 tests literalness and placement inside the source, and none tests the binding between an excerpt and the URL printed beside it; finish line recoveries/excerpt-binding-audit.md with the reading rule in the header, the fixed five-column row order entry | excerpt | anchor as printed | binding verdict (bound / mis-bound / unanchored) | settling evidence, the unanchored-named-source list and the count of each verdict; opened because Q12 closed at 67b892d and the unclaimed executable set fell to one (Q20), where the pipe has previously called two "not thin", so Q7's never-dry obligation is triggered; scope boundary stated so it cannot drift into Q20 or Q10, and declining with a reason remains legitimate

WORK-QUEUE.md

@@ -2103,3 +2103,44 @@ executable set fell to **two** (`Q11`, `Q12`), with Merlin naming `Q11` as his n
 one. Q7's obligation is never-dry, so one item enters rather than none. **Declining it with a reason is a
 legitimate answer** (§3.7). Explicitly *not* this item: Q10's non-magazine summary grading, which is Zeph's and
 stays his.
+
+---
+
+## Q21 — Does every quoted excerpt resolve at the URL it is printed against?
+
+Q12 found the class and only sampled it. On `block-25`, `block-88`, `block-89` and `block-90` the Provenance panel
+says the named practice *"is independently corroborated: a published Stackchain Magazine account records the term
+'Skinner Stacking' and describes it, quoted below"* and attaches that sentence to the **bare site root**, which
+contains `Skinner` **0** times while the passage is verbatim at `/a-conversation-with-burnchainers/`;
+`event-2022-08-18…`'s summary names StackchainQuant twice and links it **nowhere** (and the handle 404s);
+`magazine-026` names `@a_koby` with no anchor. Three different failures of the same property, found inside an
+18-entry sample of 121.
+
+Q3 and `quote-fidelity-live.md` tested that *some* cited source contains an excerpt. Q8/Q10 test the prose the
+archive writes about a source. **Q20 tests literalness and placement inside the source.** None of them tests the
+**binding** — whether the URL printed *beside* an excerpt is a URL that contains it, and whether a named account
+is anchored at all. Until that is measured, every excerpt on the ledger is a quotation whose citation has been
+sampled for spelling and never for adjacency.
+
+**Do this:** for every published entry (121), for every quoted excerpt printed on the entry page, record the
+anchor the excerpt is actually attached to under a **stated reading rule** (state it: nearest following anchor,
+nearest adjacent anchor, or the panel's own pairing) and test the excerpt against *that* URL under the published
+detag/normalisation rule. Separately list every `@handle` or named attribution in an entry's prose that carries
+no anchor, and every anchor that carries no excerpt. Report `unreadable` plainly where the target is an image, a
+recording, or an X post whose body the fetch does not carry — do not grade those.
+
+**Done means:** `recoveries/excerpt-binding-audit.md` — the reading rule in the header, one row per excerpt with
+the fixed column order `entry | excerpt text (first 60 chars) | anchor as printed | binding verdict (bound /
+mis-bound / unanchored) | settling evidence`, the unanchored-named-source list, the count of each verdict, and
+the named entries that need an archive-side link fix.
+**Evidence:** the entry URL, the anchor URL as printed, and the fetched target's byte count **and** sha256 per
+row, with the clock on every reading — entry pages are dated readings, not identifiers. Byte counts are not
+identifiers here and must not be printed as if they were.
+
+**Status: open and unclaimed. Opened by the pipe 2026-10-10** because Q12 closed at `67b892d` and the unclaimed
+executable set fell to **one** (`Q20`); the pipe has previously called two "not thin", so Q7's never-dry
+obligation is triggered. Scope boundary, stated so the item cannot drift: this is **not** Q20 (extract fidelity
+and placement inside the source), **not** Q8/Q10 (summary prose against the article), and **not** Q3 (do the
+links resolve). It is only the excerpt→anchor binding, as a complete census rather than a sample. Expect the
+`block-*` pages to account for the known four; the value is the count on the other 117. **Declining it with a
+reason is a legitimate answer** (§3.7).