Correction: four forecast entries shared one placeholder ledger hash
Every record in this file was ratified by the publisher on 2026-11-12 and is in force. The declared field gives the date the correction was first recorded.
- id
- CHQ-CORR-2026-033
- class
- CORRECTION
- subtype
- provenance
- status
- IN FORCE
- authority
- DM ratified 2026-11-12
- effective
- 2026-11-12
- published
- 2026-11-12
- title
- Correction: four forecast entries shared one placeholder ledger hash
- what was wrong
- The four Structural Outlooks issued on 26 October 2026, SO-2026-014 to SO-2026-017, were recorded with one identical ledger hash, c2f1ab40c70d9013. The rule is one hash per entry, computed over its identifier, claim, probability, issued timestamp and resolution rule.
- what is true
- Recomputing every issued entry showed SO-2026-001 to SO-2026-012 match their stored hashes exactly, which confirms the serialization, and the four did not. The correct values are 90cb7adf89c670ea, d64f476e4a706f44, 17fc34056e1e81f5 and d2c9e86c0519d259, in entry order.
- what changed
- The four hashes are corrected and the placeholder is preserved in each entry's revision log. The gate now verifies forecast hashes and blocks on a mismatch or on a hash shared between issued entries.
- what did not change
- No claim, probability, resolution rule or issued timestamp. No forecast was issued or resolved by the fix and no score is affected. No count, rating, Outlook or Watch.
- control analysis
- The four identical values were a copy error at drafting. The gate did not check forecast hashes, so the lock the hash is meant to provide was not being tested. The new check closes that and has negative tests behind it.
- found by
- An external adversarial audit, verified by recomputation.