stackchain/troupe-standup
2
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
0ec1c643fa5cfcb996266423013de2b553eb0c95
troupe-standup/checkins/2026-10-09-merlin.md
T
timmy da95748696 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

11 KiB
Raw Blame History

2026-10-09 — merlin

Did: Claimed and finished Q11 — close the eight pass-2 date mismatches, the top unclaimed item in WORK-QUEUE.md (Q1–Q10 closed or claimed; Q13/Q19 gated on Alexander; Q11 was open and fully specified, and Timmy's 13536c1 named it as my next pick).

Deliverable: recoveries/ledger-date-closure.md — 8 rows, one verdict line each with the settling source named. Result: 8 / 8 archive correct, 0 source correct, 0 indeterminate, 0 unresolved. Every row is settled by a dated primary or contemporaneous source fetched live this run — all 8 entry pages and 13 cited sources HTTP 200, every file SHA-256'd so the record is re-checkable byte-for-byte.

The finding is that the flag itself was a rule artifact. All 8 compare an entry's event date against a source's publication date — which are supposed to differ whenever the source is a retrospective or a standards document written after the fact. Reading each source's body instead of its metadata resolves every row in the archive's favour, and one of pass 2's own notes is flatly wrong: row 1's detail claims the sources "support claims but none bears 2022 18", because it read SIP-0001's CREATED: header and never opened the abstract, which reads "On July 18, 2022 at 7:07 PM, @AriZonanHODL purchased a $5 USD stack worth of bitcoin." Rows 2, 5, 7 and 8 repeat the pattern.

Two things worth Alexander's eye: the archive's own basis: labels are accurate on all 8 rows (row 3's "repository text may include later edits" caveat is measurably true — GitHub shows 5 commits on sips/sip-0004.txt to 2022-08-09), and a void avenue is recorded so nobody repeats it: Stackchain block numbers (1492, 2079, 2080) are the social chain's own numbering, not Bitcoin heights — mempool.space/api/block-height/1492 returns a block from 2009-01-24, so a Bitcoin explorer cannot date them.

Blocked: Nothing. One sub-finding deliberately 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). The verdict does not depend on it and I would not guess which rendering is right.

Next: Q12 — the evidence-tier audit (badge census already taken 2026-09-26: 115 documented / 5 testimony / 1 corroborated / 0 unrecovered; the item requires every non-documented entry plus a stated sampling rule). Q20 (excerpt placement) is open behind it. No new queue item opened — depth is not thin.

Ask: None. Two decisions that are yours, not blockers:

  1. Retire or narrow the pass-2 date flag rule — as written it flags every event-vs- publication-date difference, which produced 8 false positives. Narrowing it to "no source of any kind bears the entry's date" would make it find real defects.
  2. Whether recoveries/ledger-date-closure.md should also be surfaced to zephyrus in a reply, or whether the queue status line I appended is enough.

— Merlin

Crucible run 3 — 2026-10-09 (queue item Q11, claimed and finished)

Method. Q11 asked for one verdict line per entry with the settling source named. I stated the resolution rule before the rows so it can be re-run and falsified: take the entry's displayed date and its own basis: label, take the strongest source the entry itself cites, search that source's body text for a matching date, and grade archive correct / source correct / indeterminate. A block explorer counts as valid evidence only for entries about actual Bitcoin block heights.

Measured from this host, 2026-10-09 ~09:20–09:55 UTC, /root/crucible/q11:

$ bash fetch.sh
index HTTP 200 / 34488 B
entry-01 event-2022-07-18-the-5-invitation-becomes-a-chain             -> HTTP 200 4281
entry-02 event-2022-07-18-anthony-enters-at-16-names-the-hill-at-24    -> HTTP 200 3913
entry-03 event-2022-07-20-receipt-provenance-becomes-part-of-consensus -> HTTP 200 4081
entry-04 event-2022-08-18-the-bitcoin-beach-campaign-closes-and-hodlon -> HTTP 200 4397
entry-05 event-2022-08-28-the-fork-of-1492                             -> HTTP 200 4380
entry-06 event-2022-10-07-gui-s-2079-and-saylor-s-2080                 -> HTTP 200 4057
entry-07 event-2022-12-00-builder-relationships-cross-into-nostr       -> HTTP 200 3957
entry-08 event-2024-05-20-one-community-multiple-living-chains         -> HTTP 200 3727

$ bash fetch-src.sh
sip-0001        …/sips/sip-0001.txt                                        HTTP 200 1610
sip-0004        …/sips/sip-0004.txt                                        HTTP 200 925
github-root     github.com/stackchainsats/stackchain                       HTTP 200 264541
bitcoinmagazine bitcoinmagazine.com/culture/how-5-bitcoin-purchase-…       HTTP 200 341594
eurobitcoiners  europeanbitcoiners.com/what-the-heck-is-stackchain/        HTTP 200 102858
mag-fork-1492   stackchainmagazine.net/the-fork-of-1492/                   HTTP 200 139734
mag-king        stackchainmagazine.net/waht-stackchain-done-dided-…        HTTP 200 153199
mag-builders    stackchainmagazine.net/stackchain-is-for-builders-…        HTTP 200 136509
mag-two-years   stackchainmagazine.net/two-years-of-stackchain/            HTTP 200 136607
x-anthony-8048  x.com/AnthonyDessauer/status/1560325688481026048           HTTP 200 110646
x-gui-3760      x.com/GuiAmadoGomes/status/1578475197211893760             HTTP 200 183500
x-saylor-0208   x.com/saylor/status/1578479561750110208                    HTTP 200 173878
wayback-genesis web.archive.org/web/20220718230820/twitter.com/AriZonanHODL/status/1549169119924080640   HTTP 200 64518

# the void avenue, measured rather than assumed
$ curl -sS https://mempool.space/api/block-height/1492
000000002590c6bd1c26…            # a Bitcoin block
$ curl -sS https://mempool.space/api/block/000000002590c6bd… | tr ',' '\n' | grep -m1 '"timestamp"'
"timestamp":1232763992
$ date -u -d @1232763992
2009-01-24 02:26:32 UTC           # not a Stackchain date — block 1492 is Bitcoin's, not the social chain's
# block 2079 → 2009-01-28 06:06:10Z ; block 2080 → 2009-01-28 06:26:34Z

# row 3's caveat, checked in git rather than trusted
$ curl -sS "https://api.github.com/repos/stackchainsats/stackchain/commits?path=sips/sip-0004.txt&per_page=100"
5 commits; earliest 2ac1fbab 2022-07-21T02:11:47Z "initial draft"
latest   c6256d0e 2022-08-09T18:33:56Z
$ curl -sS "https://api.github.com/repos/stackchainsats/stackchain/commits?path=sips/sip-0001.txt&per_page=100"
2 commits; earliest 16070f72 2022-07-20T19:23:49Z "rough draft of SIP-0001"

The eight verdicts and what settled each (full table with verbatim quotes in recoveries/ledger-date-closure.md §2):

  1. entry-01 / 2022-07-18 — archive correct. SIP-0001's abstract: "On July 18, 2022 at 7:07 PM, @AriZonanHODL purchased a $5 USD stack worth of bitcoin." · European Bitcoiners (2022-07-22, four days later): "@AriZonanHODL first posted July 18, 2022 @ 4:07 PST." · Wayback 20220718230820 of the genesis tweet: "11:07 PM · Jul 18, 2022 · Twitter for iPhone" with "Even on days when I'm broke as hell I still stack. Feel free to join me."
  2. entry-02 / 2022-07-18 — archive correct. Cited article: "I went back and found your first stack at Block 16, posted on July 18, 2022, so that was very early days in the Stackchain."
  3. entry-03 / 2022-07-20 — archive correct. SIP-0004: "CREATED: 2022-7-20"; earliest git commit on the file 2022-07-21T02:11:47Z, i.e. one day later, exactly as the entry's own basis label ("repository text may include later edits") predicts.
  4. entry-04 / 2022-08-18 — archive correct. Cited X post body: "6:00 PM · Aug 18, 2022".
  5. entry-05 / 2022-08-28 — archive correct. Cited retrospective: "August 28th, 2022 late in the morning, Stackchain block height was already 1492 when @caroghero decided to fork the chain (& the Stackchain Legend, @sathoarder) and call #1492 his."
  6. entry-06 / 2022-10-07 — archive correct. Both cited posts: "7:59 PM · Oct 7, 2022" (Gui) and "8:17 PM · Oct 7, 2022" (saylor); European Bitcoiners independently embeds "Block 2080 #stackchain … — Michael Saylor⚡️ (@saylor) October 7, 2022".
  7. entry-07 / 2022-12 — archive correct. Cited article: "In mid-December 2022, I tried Nostr again." Month precision is the honest precision; the slug's -00 day is a placeholder and the page renders month-only.
  8. entry-08 / 2024-05-20 — archive correct. Cited article's own line: "As of the date of my writing this May 20th 2024, Stackchain has an approximate cuck-buck market cap of 18-21 million war bu…", against the page's article:published_time 2025-07-22T14:33:48Z — both halves of the entry's basis label verified.

Three findings, logged.

  1. The flag was a rule artifact, and the root cause is the one Q8 found. Every flag compares an event date to a source publication date. Reading bodies instead of metadata resolves all 8 for the archive, and pass 2's row-1 note ("none bears 2022 18") is demonstrably wrong. Same defect class as magazine-040: a judgement made on metadata rather than content.
  2. The archive's basis: labels are accurate on all 8 rows and are doing the disclosure work Q12's badge tier is supposed to do.
  3. A void avenue, recorded. Stackchain block numbers are the social chain's own numbering, not Bitcoin heights; a Bitcoin block explorer returns January 2009 blocks and cannot date them. (Bitcoin-transaction entries like entry 9's heights 749873/749880 are a different class where the explorer is correct.)

Evidence bar. All 8 entry pages and 13 sources HTTP 200, every artifact SHA-256'd and listed in recoveries/ledger-date-closure.md §4 with the commands. Working files at /root/crucible/q11/ (fetch.sh, fetch-src.sh, extract.py, dates.py, settle.py, settle2.py, settle3.py, entry-01..08.html, index.html, src/).

Limits. Testimony only: the sources were fetched and hashed from this host, so the hashes are point-in-time readings of pages that can drift. Not settled: row 1's time of day (7:07 PM / 4:07 PST / 11:07 PM) — marked unverified, and the verdict does not depend on it. Not tested: the non-date claims of the 8 entries, which are Q8/Q10's lane. Not touched: no live page and no other party's file; recoveries/ledger-audit-pass2.md is unmodified and the closure is additive.

Landing evidence. Files written this run:

  • recoveries/ledger-date-closure.md (new, 16,510 B)
  • WORK-QUEUE.md (Q11 status line appended)
  • checkins/2026-10-09-merlin.md (this file)
$ sha256sum recoveries/ledger-date-closure.md
a3d022d3bb30ebc44ca2330684f4ec9ec43df7be57f991f6c61a27a4763b0857  recoveries/ledger-date-closure.md
$ wc -c recoveries/ledger-date-closure.md
16510 recoveries/ledger-date-closure.md

— Merlin

Reference in new issue View Git Blame Copy Permalink