# Q10 pilot — summary fidelity for the non-magazine entries

Draft 2026-10-06 ~20:35 ET. Method: Q8's clause grading applied to the entry the
queue names first (pilot = 1 of 30). Grades: holds / overstated / unsupported /
contradicted. Evidence: entry URL, summary clause, source URL, settling
sentence verbatim. Gradeable against the entry's own cited sources only.

## Entry: event-2022-07-18-the-5-invitation-becomes-a-chain

- Entry URL: https://alexanderwhitestone.com/stackchain/event-2022-07-18-the-5-invitation-becomes-a-chain/
- Page tier badge: Documented (badge check is Q12's, not graded here)
- Archive summary (full): "AriZonanHODL posted a $5 bitcoin purchase; Bob /
  @HappyClownTime replied with $6 and Satskeeper with $7. The important
  invention was not a token or software chain but a repeatable social act:
  reply to a purchase with a purchase one dollar larger. The genesis URL
  survives in the project repository even though its public mirror currently
  returns 404."
- Page's own provenance: "Archive summary written from the sources below — not
  a quotation." / "Machine-written summary, not an editorial statement."
- Sources the entry itself cites:
  1. https://github.com/stackchainsats/stackchain ("From the sources" quote)
  2. https://bitcoinmagazine.com/culture/how-5-bitcoin-purchase-cascaded-into-1-5-million-viral-movement
  3. https://raw.githubusercontent.com/stackchainsats/stackchain/main/sips/sip-0001.txt
- Page fetched 2026-10-07 ~00:35Z: HTTP 200 / 4,281 B. Bitcoin Magazine article
  fetched ~00:36Z: HTTP 200 / 538,925 B. GitHub repo page fetched ~00:36Z:
  HTTP 200 / 264,959 B.

### Clause rows

| # | Clause | Grade | Settling evidence (verbatim) |
|---|--------|-------|------------------------------|
| 1 | AriZonanHODL posted a $5 bitcoin purchase | holds | BM article: "Almost two months before he deleted his account, @ArizonanHODL tweeted an unassuming screenshot of a $5 Bitcoin purchase." URL: https://bitcoinmagazine.com/culture/how-5-bitcoin-purchase-cascaded-into-1-5-million-viral-movement |
| 2 | Bob / @HappyClownTime replied with $6 | holds | BM article: "The story goes like this: @ArizonanHodl posts his $5 bitcoin buy, @Happyclowntime, also known as Bob, followed it up with a $6 buy and Satskeeper followed Bob's with a $7 buy." (same URL) |
| 3 | and Satskeeper with $7 | holds | Same sentence as clause 2. (same URL) |
| 4 | The important invention was not a token or software chain but a repeatable social act: reply to a purchase with a purchase one dollar larger | holds (editorial frame) | The factual sequence ($5 -> $6 -> $7, one dollar larger) is the BM article's verbatim sentence above; "the important invention was not a token or software chain" is the archive's own interpretive frame, not checkable against the source — the page itself labels the summary "not a quotation". Nothing in the source contradicts it. |
| 5 | The genesis URL survives in the project repository even though its public mirror currently returns 404 | holds | SIP-0001 PROCESS step 1 (source 3 above; fetched 2026-10-08, HTTP 200 / 1,610 B) names the genesis URL verbatim: "Visit the @AriZonanHODL Stackchain thread located at 'https://twitter.com/AriZonanHODL/status/1549169119924080640'." The project repository's README (raw, fetched 2026-10-08, HTTP 200 / 9,663 B) carries the same URL as the link on "decided to buy". The second half is a fetch fact: the tweet's public mirror resolves twitter.com -> 301 -> x.com -> 404 (documented in recoveries/dead-link.md). Corrected 2026-10-08 per reply 45/46; the earlier unsupported grade rested on a false reading of the source lane (two of the three cited sources do name the URL). URL: https://raw.githubusercontent.com/stackchainsats/stackchain/main/sips/sip-0001.txt |

### Pilot totals

5 clauses: 5 holds / 0 overstated / 0 unsupported / 0 contradicted.

### Readability note (not a grade, not a Q13 flag)

- The entry's "genesis URL ... public mirror currently returns 404" sentence
  names neither the URL nor the mirror in the summary, though the cited
  sources do name the URL (see clause 5). Naming the URL and mirror would help
  the reader; this is a readability suggestion, not an evidence gap. It is NOT
  added to the Q13 list — it reaches that list only on Alexander's call.

## Remaining scope (Q10 full sweep)

Site census 2026-10-07 ~00:37Z from https://alexanderwhitestone.com/stackchain/blocks/
lists 30 linked entry pages: 8 block pages (block-5, block-6, block-7, block-25,
block-88, block-89, block-90, block-405-420) and 22 event pages (see below),
matching Q10's spec (22 dated events + 8 block/receipt entries = 30). All 30
are linked from the blocks index — the earlier 29/21 count was my census error,
corrected 2026-10-08 per reply 45/46.

Event pages found (22): event-2022-07-18-anthony-enters-at-16-names-the-hill-at-24,
event-2022-07-18-the-5-invitation-becomes-a-chain (done above),
event-2022-07-19-op-backstack-experimentation-almost-immediat,
event-2022-07-20-accessibility-becomes-a-protocol-question,
event-2022-07-20-receipt-provenance-becomes-part-of-consensus,
event-2022-07-22-skinner-s-405-420-and-the-social-fork-questi,
event-2022-08-17-bitcoin-beach-transfers-leave-a-transaction,
event-2022-08-18-the-bitcoin-beach-campaign-closes-and-hodlon,
event-2022-08-21-block-1414-becomes-the-first-million-target,
event-2022-08-24-a-practical-fork-resolution-offer-at-1438-14,
event-2022-08-28-the-fork-of-1492,
event-2022-09-12-actual-miners-get-an-accounting-route,
event-2022-10-05-the-community-documents-its-scale-and-charit,
event-2022-10-07-gui-s-2079-and-saylor-s-2080,
event-2022-12-00-builder-relationships-cross-into-nostr,
event-2023-01-30-burnchain-and-loko-s-sj-lottery-are-already,
event-2023-05-00-siggy-reaches-nostr,
event-2023-08-00-the-archive-becomes-a-magazine-a-game-and-a,
event-2024-04-14-burnchain-explains-itself-in-its-own-words,
event-2024-05-20-one-community-multiple-living-chains,
event-2025-02-15-ogchain-receives-a-first-person-governance-a,
event-2026-01-08-golden-blocks-become-an-artifact-worth-remem.

Method note for the full sweep: the block/receipt entries (8) are the ones the
queue says matter most — they make claims about chain events. Several sources
may be X posts, receipts, or space recordings; where a cited source is
unreachable or is a live post behind a login wall, grade `unreadable source`
plainly instead of graded, per the Q10 spec.

## Corrections (2026-10-08, per reply 45/46)

- Census: 21 -> 22 events, 29 -> 30 linked entry pages; the "counted but not
  yet found" sentence was wrong — all 30 are linked from the blocks index
  (Timmy counted 22 event links at the live index; my own list above prints 22
  slugs, counted by matcher `event-[a-z0-9-]+`).
- Clause 5: unsupported -> holds. The grade rested on a false reading of the
  source lane: SIP-0001 PROCESS step 1 names the genesis URL verbatim and the
  repo README carries the same URL as the "decided to buy" link (both verified
  from this host 2026-10-08: sip-0001.txt 200/1,610 B, two twitter.com strings;
  raw README 200/9,663 B). New pilot totals: 5 / 0 / 0 / 0.
- Wording-flag candidate withdrawn on its stated ground; kept only as a
  readability note above (not a grade, not on Q13 — Alexander's call to list it).