Corrections & verification

Two integrity defects were found on 2026-07-26 and are recorded here in full. No card, metadata file, ledger entry, recorded hash, or timestamp proof was rewritten to make either go away.

How to verify a card

Download card.json from any card page and hash it (sha256sum card.json). That value should equal the downloadable artifact hash shown in that card’s “Verifying this card” box. The card’s OpenTimestamps proof commits to those same bytes.

There are four independent evidence layers, answering different questions:

1. The append-only ledger and Git history — when the card was committed, and that nothing was edited afterwards.
2. The card lock and publication timestamps — that the card existed before first post.
3. The OpenTimestamps calendar commitment — independent third-party evidence that those exact bytes existed when we say they did.
4. A Bitcoin attestation, once the proof is upgraded — the same evidence anchored in a block.

Layers 1 and 2 establish that a pick was published before post. A Bitcoin confirmation arriving later strengthens the external evidence; it is not what makes the pre-post claim true, and a pending proof does not weaken it.

Card hashes: recorded lock hash vs downloadable file

Cards published before 2026-07-26 were generated on Windows. The lock hash was calculated from CRLF-formatted bytes before Git stored the same JSON with LF line endings, so the recorded hash does not match the file you can download. The selections and JSON values are unchanged — the difference is exclusively line endings, proven byte-for-byte for every affected card. This broke reproducible verification, which is why it is disclosed here rather than described as a formatting detail.

Machine-readable: card_hash_corrections.jsonl (hash-chained, append-only) and proof_status.json.

Metadata proofs

A card’s meta.json holds presentation detail — publish time, weather, per-pick notes. For 2026-07-17 (both tracks) that file was edited after its proof was created, so the original proof commits to the metadata as first published, not to the current file. Both are kept: meta.json.ots is the original-publication proof, and meta.current.json.ots commits to the current bytes, stamped 2026-07-26 and labelled as such. The card hash embedded in the metadata never changed, and the card.json proofs are unaffected. Metadata is presentation, not locked evidence — the card is the locked evidence.

Result entries: provisional grades superseded by chart grades

Provisional results were later superseded by enriched chart results. Both entries remain in the append-only ledger, while the canonical record counts each selection once. Settlement values — win/loss and P/L — agree in every case; the later entry only adds finishing position, closing odds and drift.

Machine-readable: record.json. It distinguishes raw ledger entries from effective results, so the de-duplication rule is visible rather than something you have to reconstruct.