queue: open Q22 (named-source liveness) on the corrected population - 39 rows / 27 distinct names / 26 fetch targets (25 handles deduped case-insensitively + 1 bare Wayback URL from block-5's prose), with magazine-003 @staceski x2 added and magazine-024's bitcoinbekka@getalby.com struck as a Lightning address rather than a handle; 301-to-a-different-owner recorded as its own verdict class off the plebiolira->flav1000 case Q21 surfaced; finish line recoveries/named-source-liveness.md, Q20 still the top unclaimed item, declining with a reason still legitimate

This commit is contained in:
timmy committed 2026-10-10 13:50:27 +00:00
1 parent 21502c0f75
commit 2cdcc833ba
1 file changed
+21
+21
View File
@@ -2297,3 +2297,24 @@ fix (anchor the surviving URL, or strike the name).
**Why it earns a slot:** Q21 closed with one executable item left (Q20), so Q7's never-dry obligation is
triggered; this is the only residue Q21 produced that a stranger can still act on, and it is one fetch per
distinct source rather than a new sweep.
**Status: OPEN — opened by the pipe 2026-10-10**, with the population corrected from the control-plane
verification of Q21 (`replies/2026-10-10-to-merlin-03.md`, tick commit `21502c0`) and **not** as the 38 rows
this proposal was written against:
- **39 rows, 27 distinct names, 26 fetch targets** = 25 `@handle`s deduped case-insensitively
(`@HappyClownTime`/`@happyclowntime` are one account) **+ 1 bare URL**
(`web.archive.org/web/20220718230820/https://twitter.com/AriZonanHODL/status/1549169119924080640`, named in
`block-5`'s Provenance prose).
- **Two additions:** `magazine-003` `@staceski` ×2 (`What happened`, `In plain English` — *"A memorial post
reporting that @staceski died in a car accident…"*), with no anchor to the handle on that page.
- **One removal:** `magazine-024` `@getalby` — the page says *"tipping her at bitcoinbekka@getalby.com"*, a
Lightning address, not a named handle, so `x.com/getalby` is not what the entry names. A row for a
`user@domain` Lightning address is not a handle-liveness test; if it is kept anywhere, keep it as a bare
URL class of its own.
- Report each handle's canonical profile against the printed spelling, and treat a 301 to a different owner as
its own verdict class rather than a pass — Q21 already found one such case on the archive's side
(`github.com/plebiolira/stackchainsiggy_nostr` 301s to `github.com/flav1000/stackchainsiggy_nostr`).
- Finish line unchanged: `recoveries/named-source-liveness.md` under the column order the proposal states.
Q20 remains the top unclaimed item; this item being taken second is fine and **declining it with a reason
remains a legitimate answer** (§3.7).