Data-error playbook
Detection, triage, quarantine — and the commitment to disclose errors nobody noticed.
Detection
- Automated guards run before every settlement. Quote-quality gates, MAD outlier trimming,
staleness limits and the thin-book anomaly check (
lib/indices/consolidated.ts) exclude bad inputs rather than averaging them in. - Engine fixtures run in CI.
npm run index:verifyasserts the engine still reproduces the published formulas to 1e-9. Drift fails the build. - The checksum chain makes any post-hoc alteration of history detectable by anyone holding an earlier checksum.
Triage
| Severity | Definition | Response |
|---|---|---|
| Blocking | The published value is materially wrong | Settlement halted; notice published same day; correction under restatement.md |
| Contained | A single constituent is wrong; the value is within tolerance | Constituent quarantined; value stands; disclosed on the next settlement |
| Cosmetic | Metadata, labels, display | Fixed; logged; no restatement |
Quarantine
A constituent whose input is suspect is excluded from settlement pending review rather than included with a caveat. The index is computed over inputs it trusts; a footnote is not a substitute for exclusion.
The reporting standard
An error that reached publication is disclosed even when nobody noticed. The value of a self-audited record is that it self-audits when it is inconvenient; disclosing only what has already been spotted is not disclosure.
The rest of the set
Methodology change & consultation
What counts as a material change, the 14-day consultation window, and why changes are prospective.
Data licence & rights
What the free tier grants, what attribution it requires, and what commercial use needs.
The loop architecture
The nine scheduled agents that cultivate indices, which one may publish, and the six mechanisms that assure accuracy.
The confirm gate
What human confirmation covers — merges only — and how to read the provisional and single-venue counts.
Restatement policy
The three narrow conditions under which a published value may be corrected — and the many under which it may not.
Cessation & fallback
What happens when a benchmark cannot be computed, and why the history stays published forever.
Conflicts & the conflict wall
The wall between index operations and the trading circuit, plus standing disclosures.
Complaints & challenges
How to challenge a value, a rule, or a constituent. No account required.