diff --git a/recoveries/summary-fidelity-nonmagazine-pilot.md b/recoveries/summary-fidelity-nonmagazine-pilot.md index af0871b..5cc9ea9 100644 --- a/recoveries/summary-fidelity-nonmagazine-pilot.md +++ b/recoveries/summary-fidelity-nonmagazine-pilot.md @@ -33,29 +33,30 @@ sentence verbatim. Gradeable against the entry's own cited sources only. | 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 | unsupported | The clause's referent is not named anywhere in the entry's source lane: the three cited sources name no "genesis URL" (the GitHub repo page carries no tweet URL; the BM article says the account was deleted; SIP-0001's only twitter.com string is the author's handle in its header). Whether "genesis URL" means the original tweet or something else, and which "public mirror" 404s, cannot be settled from what the entry cites. | +| 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: 4 holds / 0 overstated / 1 unsupported / 0 contradicted. +5 clauses: 5 holds / 0 overstated / 0 unsupported / 0 contradicted. -### Wording-flag candidate (Q13 list, Alexander's call) +### Readability note (not a grade, not a Q13 flag) -- The entry's "genesis URL ... public mirror currently returns 404" clause names - neither the URL nor the mirror — either name both or drop the clause. This is - a suggestion, not a correction; the grade (unsupported) stands regardless. +- 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 29 linked entry pages: 8 block pages (block-5, block-6, block-7, block-25, -block-88, block-89, block-90, block-405-420) and 21 event pages (see below). -Q10's spec (WORK-QUEUE.md) counts "22 dated events and 8 block/receipt -entries" = 30; one event from the spec's 22 is not linked from the blocks -index — counted but not yet found (candidates: genesis/ directory or an -unlinked page; honest gap, not assumed). +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 (21): event-2022-07-18-anthony-enters-at-16-names-the-hill-at-24, +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, @@ -83,3 +84,17 @@ 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).