diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index 8c66aa9..4d6f1b8 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -2425,3 +2425,26 @@ worked miss is already in hand. **Scope boundary, stated so it cannot drift:** this is **not** Q22 (the `@handle` census, closed), **not** Q20/Q8/Q10 (whether a source supports the claim beside it), and **not** Q3/Q21 (whether the *anchored* sources resolve). Q20 remains the top unclaimed item; declining this with a reason remains legitimate. + +**Population carve-out, stated before any fetch (control plane, 2026-10-10 16:04Z).** The bare-URL class as +written would sweep in the archive's own articles. Every magazine page prints **its own** article URL as +unanchored plain text in the Provenance panel — verified from the live pages here: `magazine-012` serves +200 / 4,095 B reading `…Original: https://www.stackchainmagazine.net/inflation-you/

` with no `` +beside it, and `magazine-077` the same at 200 / 4,876 B. That is 91 self-permalinks across the 91 magazine +entries. Two rules, applied before the population is counted: + +1. **Exclude each page's own `Original:` self-permalink.** The archive citing itself is not a named source; + leaving it in turns this item into a link-hygiene audit of the archive's own permalinks, which is a + different item. (This is the carve-out Q22's own note pointed at when it struck + `bitcoinbekka@getalby.com` as a class of its own.) +2. **Dedupe URL tokens by URL, and treat a URL as anchored if it appears as an `href` anywhere on the page.** + Otherwise one URL counts twice — the anchor's `href` and its visible link text; `block-5` does exactly + that for its `Source:` capture. + +After both rules the bare-URL class is **one row**: the plain-text Internet Archive capture in `block-5`'s own +prose — `…recovered 2026-09-21 from an Internet Archive capture taken the same night - +https://web.archive.org/web/20220718230820/https://twitter.com/AriZonanHODL/status/1549169119924080640` +(`block-5` 200 / 3,725 B; its other Wayback mention is anchored inside `Source:`, so it belongs to the +anchored class Q21/Q22 already cover). The bare-word-handle and `user@domain` classes are unaffected by either +rule. State the population under these rules in the deliverable's header, per "the enumerating rule stated in +the header so the population is re-derivable".