2026-10-11 19:59:42 +00:00
..
2026-09-24 10:54:06 +00:00
Q12 DONE: are the evidence tiers earned? (recoveries/evidence-tier-audit.md) - 18/18 justified, 0 too strong / 0 too weak / 0 indeterminate, no badge in the sample misstates its evidence; sample rule stated before any fetch (every non-documented entry = all 6: 5 testimony_only + 1 corroborated + 0 unrecovered, plus every 9th documented entry in index order = 12, total 18 of 121); census reproduced from the live index (200 / 34,488 B / sha256 4f764ef4dfb9, grep 'badge documented' 115 / testimony 5 / corroborated 1 / unrecovered 0 = 121 <li id=); all 18 entry pages and 17 cited sources fetched live this run, 33 of 37 quoted excerpts >=25 chars verbatim in a source the entry cites, and 8 of 12 sampled magazine entries carry a displayed date equal to the cited article's own article:published_time to the day; five named findings, none a badge overstatement - (1) block-25/88/89/90 quote the 'Skinner Stacking' passage and link the bare site root which contains 'Skinner' 0 times while the passage is verbatim at /a-conversation-with-burnchainers/ (200 / 155,217 B / sha 50a2e57e3ba6), the publication's only ?s=Skinner result; (2) event-2022-08-18 names StackchainQuant's October account twice, links it nowhere, and x.com/StackchainQuant returns 404 'User Profile Not Found', its badge still earned by the post text verbatim x3 and tx ae63c499 confirmed at height 749999 / 2022-08-18T17:45:12Z / 851,979 sats; (3) magazine-026 names @a_koby with no anchor; (4) the legend's Unrecovered tier is defined and applied 0/121 times while material fitting it sits in lower-tier Uncertainty panels; (5) Documented on the 91 magazine entries is a liveness claim not a held-artifact claim (Receipt panel says 'No receipt is held', and bitcoinmagazine.com answered 403 to a Chrome UA and 200 / 341,802 B to a bare curl UA in the same minute); limits: 18 of 121 is a sample, the 6 non-documented are a complete census of their tiers and the 12 documented license no rate for the other 103, all byte counts and hashes are dated readings from this host ~09:0x UTC, nothing live edited; check-in 2026-10-10-merlin.md; Q12 status block appended; Q20 next, Q9 blocked on the audio handover, Q13/Q19 gated on Alexander, depth not thin so no new item opened
2026-10-10 09:08:47 +00:00
2026-10-10 13:35:36 +00:00
2026-09-24 13:22:42 +00:00
2026-10-11 11:16:20 +00:00
2026-10-11 15:39:52 +00:00
2026-10-11 19:59:42 +00:00
2026-10-11 09:08:58 +00:00
2026-09-24 10:56:00 +00:00
2026-09-24 11:18:38 +00:00
Q11 DONE: closure of the eight pass-2 date mismatches (recoveries/ledger-date-closure.md) - 8/8 resolved, all archive correct, 0 source correct / 0 indeterminate / 0 unresolved; every row settled by a dated primary or contemporaneous source fetched live this run (all 8 entry pages and 13 cited sources HTTP 200, each sha256'd): SIP-0001's abstract "On July 18, 2022 at 7:07 PM" for row 1, so pass 2's own "none bears 2022 18" is wrong (it read the CREATED header, never the abstract); king-of-stackchain article "July 18, 2022"; SIP-0004 CREATED 2022-7-20 plus git history (earliest 2ac1fbab 2022-07-21T02:11:47Z, 5 commits to 2022-08-09, which is what the entry's basis label warns); cited AnthonyDessauer post "6:00 PM Aug 18, 2022"; the-fork-of-1492 article "August 28th, 2022 late in the morning"; both cited X posts "Oct 7, 2022" (7:59 PM / 8:17 PM); "In mid-December 2022"; and "May 20th 2024" as the two-years article's own composition date against its 2025-07-22 upload; the flag was a rule artifact - all 8 compare an event date against a source publication date, which are supposed to differ for retrospectives and standards documents, so the flag rule should be retired or narrowed; the archive's own basis: labels are accurate on all 8 rows; one void avenue recorded so it is not repeated (Stackchain block numbers 1492/2079/2080 are the social chain's own numbering, not Bitcoin heights - mempool.space block-height/1492 returns a 2009-01-24 block, ts 1232763992); one sub-finding left unverified (row 1's three sources agree on the date and disagree on the hour: 7:07 PM / 4:07 PST / 11:07 PM); check-in 2026-10-09-merlin.md; queue depth not thin so no new item opened (Q12 next, Q20 behind it)
2026-10-09 09:11:05 +00:00
2026-09-24 13:34:47 +00:00
2026-09-24 13:34:47 +00:00
2026-09-24 20:32:46 +00:00
2026-10-10 17:53:09 +00:00
2026-10-10 15:46:04 +00:00
2026-10-10 22:17:19 +00:00
queue: Q26 hardening DONE (Merlin) - the two silent token classes now die at build time (pre-write sentinel scan, per-entry panel set so the quote branch is caught by construction, render_genesis panels routed through expand_prose), all five Q25 legs re-run green on the hardened prototype (no-token build byte-identical at 91ecf6bf, 125 files, diff -rq vs live tree silent, registry still 8, uncited-handle negative still exit 1, H1-H4 demo still 3 of 125 files), 12 negative fixtures all exit 1 with their own message (7 malformed incl. open brace/empty handle/whitespace/wrong namespace/over-15-chars/lone close/close-then-open, 5 outside-panel incl. quote branch, title, excerpt, display_name, coverage gap) plus a cited-token positive control expanding on the entry page AND the genesis page; contributor.display_name fifth slot measured without building it - G2 and I2 take the handle-only fix, G1 needs display_name as a fifth panel to anchor @AnthonyDessauer beside the single handle slot (a build change, Alexander's); hardened convention carries 4 of Q24's 31 deltas as links (H1-H4); shared build tree untouched at 97fedb5d with site-ledger byte-identical and nothing modified since 2026-10-10 18:00Z, live index 200/34,488 B/4f764ef4dfb9, blocks.json read-only, decisions/ and inbox/ untouched, nothing executed
2026-10-11 00:25:06 +00:00
2026-09-24 13:34:47 +00:00
2026-10-11 04:40:31 +00:00
2026-10-11 02:32:48 +00:00
2026-10-11 06:50:32 +00:00
2026-09-24 10:56:20 +00:00
2026-09-24 10:56:20 +00:00
2026-10-07 13:08:32 +00:00
2026-10-08 13:09:28 +00:00
2026-10-10 13:18:38 +00:00
2026-09-26 13:31:45 +00:00