Editorial policy

Facts and explanation

A fact is a recorded value with a state, dates and — where recorded — source references, and it has an evidence panel. A fact with no recorded reference says so in that panel. Explanation — page introductions, notes such as “a deadline is not an outcome”, and comparison labels — is editorial text written to help readers interpret the facts. Explanation never introduces a new fact without a source.

Where the site makes its own judgment, it says so: a “site classification” or “site assessment” label marks values the site derived rather than quoted.

Dated scope

Every financial fact describes the record on its own check date, a UTC calendar day shown in its evidence. In this edition, source checks are dated Oct 5, 2026 (UTC day). A statement such as “approval pending” means that was the record on that date. Future dates are labelled “upcoming at snapshot” relative to the edition date (Oct 6, 2026), and dates are never computed from the reader’s clock or the build time. Edition update times are shown in US Eastern time (ET).

Supported claims, unknowns and conflicts

• A value is shown as established only when its recorded evidence supports it. A site classification or assessment based on that evidence is labelled as such.
• When sources were checked but did not establish a value, the field says “Not confirmed” and lists what was checked.
• When sources disagree, both statements are shown, the value is withheld, and nothing derived from it — such as a tick value — is calculated.
• Unknown is not negative: the site does not write “not approved”, “not launched” or “no trading” unless a source says so.

Counting references

Documents that are versions of one publication — such as an exchange product page and the PDF generated from it — form one reference family and count once. A reference kept only for traceability is labelled as such and is not counted as corroboration. A source-level locator is never presented as a fact-specific citation. See Evidence and locators.

No automatic promotion of status

A record never moves to a stronger state because time passes or because a related record exists. In particular:

• Reaching a review or comment deadline does not make a contract approved.
• A first trading date on an exchange calendar does not become a launch date or a first trade.
• An announced platform integration does not become enabled access.
• A superseded launch date stays historical.
• Missing volume or open interest is never shown as zero.
• A group is not treated as the legal exchange, and a clearing venue code is not treated as a legal clearing entity.

Current controls and what is not yet in place

In place now

• The data is validated before every build. A build fails if the data’s digest, schema version or publication rules do not match — for example if an unknown becomes zero, or a calendar date becomes a launch.
• The built site is checked for broken links and anchors, evidence rendering rules, market-data components and third-party scripts.
• Each evidence panel shows its source, locator, role, dates and limitation.
• A public correction address, [email protected], listed with the other channels on the contact page.

Not yet in place

• Scheduled re-checking of sources. Facts are as of their own check dates: Oct 5, 2026 (UTC day).
• A full public change history. This edition revises the Oct 5, 2026 snapshot. 15 facts were re-reviewed from saved source copies and are marked “This edition” in their evidence; all other facts keep their earlier checks. A full public change history is not yet available.
• Published operator details.
• A dedicated human editorial sign-off, or a formal legal or compliance review.

Corrections policy

A correction changes the data record, not just the wording around it. When a fact is corrected, the change is made in a new data snapshot with its source and date, and the earlier value is not presented as though it had always been right. No corrections have been made so far. The current edition adds and updates facts from newer evidence and marks them in their evidence panels; it does not treat earlier values as errors.

What a useful correction identifies

1. The page and the field — for example “GPU2 page, Final payment”.
2. What is wrong or out of date.
3. The primary source that shows it, with a link and the page or section.
4. The relevant date: the source’s document date, an effective date, or the day you checked it.

How to send one

Email factual corrections and source suggestions to [email protected]. Please include the relevant contract or page, the disputed field, and the URL of the primary source that supports the correction. Other addresses are on the contact page.