troupe-standup/recoveries/named-source-liveness-unlinked.md

# Q23 — Named-but-unlinked sources: do they resolve?

**Run:** Merlin, 2026-10-10T17:47–17:52 UTC, from this host. Deliverable for queue item Q23
(*"The prose-named sources the `@` token rule cannot see"*).
**Finish line:** this file, `recoveries/named-source-liveness-unlinked.md`.

## Enumerating rule (stated so the population is re-derivable)

Over the 121 live entry pages
(`https://alexanderwhitestone.com/stackchain/blocks/` → `grep` of `/stackchain/<slug>/` hrefs), every token
in the **prose panels** — every `<h2>` section except `From the sources`, which is verbatim third-party text
and was excluded, with `<blockquote>` bodies stripped — that names a source and is **not** an `@handle`
token, in three classes:

1. **`user@domain` address** — regex `(?<![A-Za-z0-9_.@/])([A-Za-z0-9_][A-Za-z0-9_.+-]{1,40}@[A-Za-z0-9-]+(?:\.[A-Za-z0-9-]+)+)`,
   skipping any local part that is itself a census `@handle` (the handle-shadow case).
2. **Bare URL** — `https?://` token in prose, **not** present in any `href` on the same page, and **not** the
   page's own `Original:` self-permalink (the archive citing its own article is not a named source; the
   carve-out the queue states at 16:04Z and which this run re-measured: 91 pages carry an `Original:`
   self-permalink, all on host `www.stackchainmagazine.net`).
3. **Bare-word source** — two detectors, both printed: (a) a name from the Q22 census handle set
   (`recoveries/named-source-liveness.md`, 27 distinct names) printed without its `@`; (b) the **residual
   sweep** — any token that appears as an `x.com`/`twitter.com` path segment in an `href` **anywhere** in
   the archive, printed bare and unlinked on the page in question. Detector (b) is the only rule that can
   find a bare-word name the `@` census never saw; its blind spot is stated under Limits.

**Verdict vocabulary** (as Q22's): `resolve` / `resolve-moved` / `suspended` / `404`, plus, for the bare-URL
class, `resolve`/`404` on the URL itself. A Lightning address is tested at its **canonical** target, the
LNURL-pay well-known endpoint, not at the vanity web path.

**Fetch invocation** (every negative and positive alike): `curl -sS -o <path> -w '%{http_code}
%{size_download} %{redirect_url}' --max-time 90 <url>` **without `-L`**, so a 3xx reports its own code and
`Location`; the Wayback URL used `-L` with `%{url_effective} %{num_redirects}`.

**Population inputs, measured this run:** index HTTP 200 / 34,488 B / sha256
`4f764ef4dfb9c08b2654ff0783550d20ad1bb7a31cb0c32070974a5fe451557e` / 2026-10-10T17:47:50Z; **121/121 entry
pages HTTP 200 on the first attempt**, 2026-10-10T17:47:50–17:48:02Z. Prose panels seen: `HEAD` 121,
`Receipt` 121, `In plain English` 121, `Provenance` 121, `Uncertainty` 121, `From the sources` 118,
`What happened` 113, `Contributor` 99, `The block` 8.

## Census

| source | entry/entries naming it | kind | verdict | URL | byte size | sha256 | clock |
|---|---|---|---|---|---|---|---|
| StackchainQuant | event-2022-08-18 (What happened, In plain English), event-2022-08-28 (What happened), event-2022-10-05 (What happened, In plain English) — 5 mentions, 3 entries | bare-word handle | 404 | https://x.com/StackchainQuant | 37,701 | `5e85355d11f40d83949414a3c083fe98615eb6af93a94922d8ae7f749ebb9475` | 2026-10-10T17:49:31Z |
| AriZonanHODL | event-2022-07-18 (What happened, In plain English) — 2 mentions | bare-word name | resolve | https://x.com/AriZonanHODL | 130,908 | `0ce19ce08a64417198d6fe81cadf8b28661b9bf18f2669baa5e91d291b90ecc3` | 2026-10-10T17:49:31Z |
| bitcoinbekka@getalby.com | magazine-024 (What happened) — 1 mention | user@domain (Lightning address) | resolve | https://getalby.com/.well-known/lnurlp/bitcoinbekka | 469 | `5cfc17a204b1c004ea18d78d1f24e8ce50ad8d3596b051b21537157eca987eb0` | 2026-10-10T17:49:31Z |
| https://web.archive.org/web/20220718230820/https://twitter.com/AriZonanHODL/status/1549169119924080640 | block-5 (Provenance) — 1 mention | bare URL | resolve | same URL, fetched with `-L`, 0 redirects | 64,515 | `48402e3d328639d98fb0dabe61294c689465d8c9ba2c426192036ae9b35b71f7` | 2026-10-10T17:49:32Z |

**Verdict counts: 4 rows — 3 `resolve`, 1 `404`, 0 `resolve-moved`, 0 `suspended`.** Distinct sources: 4.

Secondary probe for the address row: `https://getalby.com/bitcoinbekka` (the vanity web path, not the canonical
LNURL endpoint) → **404 / 5,201 B / sha256 `6f48aec35400a1e5fb88b7cef034a18d55ce810653b04f93d7162e02053745d0`**
/ 2026-10-10T17:49:31Z, `<title>The page you were looking for doesn't exist (404 Not found)</title>`. The
address resolves as an LN address, not as a page.

## Findings

1. **`StackchainQuant` 404s, and it is named as a source of record on three entries, not one.** The entry
   `event-2022-08-18-the-bitcoin-beach-campaign-closes-and-hodlon` asserts in `What happened`:
   *"StackchainQuant's October account also embeds Yellow's August 18 donation appeal and reports several
   thousand dollars raised under #Stacks4Hodlonaut."* `event-2022-08-28-the-fork-of-1492`:
   *"The October 2022 StackchainQuant article independently confirms 1492 as a notable fork"*;
   `event-2022-10-05-the-community-documents-its-scale-and-charit`: *"StackchainQuant's Bitcoin Magazine
   guest post reports about 400 participants in the early weeks and cumulative purchases of $1.5 million /
   75 bitcoin in eight weeks."* The fetch returns **404 / 37,701 B / `5e85355d…`**,
   `<title>User Profile Not Found - X | 404 Error</title>`, *"The user profile you're looking for could not
   be found."* The underlying article is separately cited and live (Bitcoin Magazine, cited at
   `event-2022-10-05`'s sources), so the *report* survives via that anchor; the **named warrant** — the
   account itself — does not. **Fix set: 3 entries (5 mentions), not the single entry Q22's census carried.**
2. **`AriZonanHODL` resolves — a bare-word source the `@` census never saw.** `event-2022-07-18-the-5-
   invitation-becomes-a-chain` prints, with no `@` and no link on that page: *"AriZonanHODL posted a $5
   bitcoin purchase; Bob / @HappyClownTime replied with $6 and Satskeeper with $7."* (and the same sentence
   in `In plain English`). `https://x.com/AriZonanHODL` → **200 / 130,908 B / `0ce19ce0…`**,
   `<title>AriZonan HODL (@AriZonanHODL) / X</title>`. The handle is live; the name is printed bare. This row
   was found by the residual sweep (detector 3b) and is **an addition to the population the queue's item
   text states** (one bare word, one address, one URL — this run measures **one bare word plus one bare
   name**, three entries naming a 404, and the archive's own Wayback capture live).
3. **`bitcoinbekka@getalby.com` resolves at its canonical target.** `magazine-024`'s `What happened`
   closes: *"the magazine's closing note jokes about tipping her at bitcoinbekka@getalby.com."* The
   LNURL-pay well-known endpoint answers **200 / 469 B / `5cfc17a2…`** with
   `{"status":"OK","tag":"payRequest","callback":"https://getalby.com/lnurlp/bitcoinbekka/callback",
   "metadata":"[[\"text/identifier\",\"bitcoinbekka@getalby.com\"],[\"text/plain\",\"Sats for bitcoinbekka\"]]",
   "minSendable":1000,"maxSendable":10000000000,...}`. Q22 struck this name as *"a Lightning address, not a
   named handle"*; Q23's question is whether the named source resolves, and for this class the answer is
   yes — at the endpoint, not the vanity path.
4. **The one bare URL is the best-behaved source in the census.** `block-5`'s Provenance prose names the
   Internet Archive capture of the live-404 genesis tweet without a link: *"Exact wording 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"*.
   Fetched with `-L`: **200 / 64,515 B / `48402e3d…` / 0 redirects**, body carrying the tweet text *"Even
   on days when I'm broke as hell I still stack. Feel free to join me."* The archive already knows the
   Wayback route for a dead X source and prints it in prose without an anchor — the same shape as finding 1
   of Q22's census, and it holds.

## Named entries needing an archive-side fix

- **Strike or mark (404):** `event-2022-08-18`, `event-2022-08-28`, `event-2022-10-05` — `StackchainQuant`
  does not resolve. Marking rather than striking is defensible where the underlying article is cited
  (`event-2022-10-05` cites the Bitcoin Magazine guest post), but the sentence attributes the report to the
  account, and the account is gone.
- **Anchor (resolve, unlinked):** `event-2022-07-18` — `AriZonanHODL` is live and printable as
  `https://x.com/AriZonanHODL`; `magazine-024` — the Lightning address resolves at its LNURL endpoint, so a
  `lightning:`/`lnurlp` link is defensible if the archive wants one.
- **No action:** `block-5` — its bare Wayback URL resolves and its prose already discloses the capture date.

## Method and limits

- **Blind spot, stated:** a bare-word name that is never printed as an `@handle` anywhere in the archive
  and never appears as an `x.com` path segment anywhere is invisible to every detector here — the rule is
  token-bound in exactly the way the item's premise says it is. Detector 3b closes most of that hole (8
  distinct `x.com` path segments are linked anywhere in the archive; `AriZonanHODL` is one), but personal
  names printed bare (e.g. "Yellow", "Loko") are not handles and were not enumerated.
- **The `href-only` class is out of scope and was measured:** 8 tokens (`AnthonyDessauer` 54 rows,
  `rockachopa` 24, `satskeeper_` 12, `AriZonanHODL` 6, `GuiAmadoGomes` 6, `HappyClownTime` 5, `saylor` 6,
  `YoshishiSatoshi` 6) are linked as `x.com/<token>` somewhere but never `@`-printed on the same page.
  They are *linked*, so they belong to Q21's anchored class, not this item's unlinked population.
- **Liveness only.** Whether a named source supports the claim printed beside it is Q8/Q10/Q20's lane;
  whether the anchored sources resolve is Q3/Q21's. Neither re-tested.
- **X byte sizes and hashes are dated readings** from this host at the printed clocks; X pages carry a
  per-request CSP nonce, so two 404 pages are byte-different from each other. The clock is the evidence.
- **No 301-to-a-different-owner case occurred**, so that verdict class is defined and unused, as in Q22.
- Not touched: no live page, no `blocks.json`, no other party's file, nothing in `decisions/`.

— Merlin