DATA GOVERNANCE · 2026-08-12
Data sources, freshness and corrections
This page explains where each Contract Atlas fact comes from, when it was reviewed, and which dates are confirmed schedules versus rule-based estimates.
- Contracts
- 70
- Date events
- 142
- Confirmed
- 56
- Official domains
- 13
01 · SCOPE
One search intent per page family
Live market state
The home timeline owns open/closed state, next transition and regular sessions.
Open the live clock →Contract specifications
Each contract page is the canonical owner of size, tick, tick value, expiry rule and upcoming dates.
Browse contracts →Expiry overview
The expiry view is an on-site finder only; it does not offer calendar downloads, subscriptions or duplicate month pages.
Browse expiry dates →02 · PROVENANCE
Source and review records
Every record must have a reachable official-exchange source, review date, review state and public-reference rights state. The exact source is exposed on the contract page and each expiry event.
| Field | Evidence | Publish rule |
|---|---|---|
| Size, tick and tick value | Official contract-specification page | Source and rights state accepted |
| Expiry rule | Official rulebook or contract guide | Traceable rule text and review date |
| Front-contract dates | Current schedule, or an accepted rule calculation | Must say confirmed or rule-based estimate |
Current review state: accepted· Rights state: approved_public_reference· Latest review: 2026-08-10
03 · DATE STATUS
Confirmed and rule-based are different states
- Confirmed schedule
- A date explicitly present in the current contract schedule; shown without an asterisk.
- Rule-based estimate
- Calculated from an accepted expiry rule and marked *; holidays, notices or exchange adjustments can move the final date.
A rule-derived value must never be presented silently as confirmed. Re-open the linked official source before trading.
04 · FRESHNESS
Automated gates and review targets
- 120 daysMinimum future coverage; current coverage ends .
- 30 daysNear-term dates must carry an explicit review state.
- 80%Maintenance target for confirmed dates in the next 90 days; shortfalls remain visibly estimated.
- 90 daysMaximum record review age before the build gate alerts.
05 · CORRECTIONS
How corrections are handled
Send the page URL, field to correct, official notice URL and notice date. The accepted value stays in place until the evidence is reviewed through a traceable change; external feedback never silently overwrites it.
Report a data correction