Policies
Corrections
If a value here does not match the developer's document, please tell us. This page says how, what to include, and what happens next.
Data as of 26 Sep 2026 · Dataset v0.1 · Methodology v0.1 · Changelog
Our policy
We re-check a reported value against its source, publish the outcome in the changelog, and keep the previous value in the value's history, so a correction never erases what was shown before (Methodology §11). A corrected value carries the mark Corrected wherever it appears, and its details say what was recorded before.
The same goes for how values are grouped. If you think two values were joined into one line when they measure different things, or kept apart when they measure the same thing, report it in the same way (Methodology §5).
How to report
- From the value. Select any value on the site to open its details. The last section, Report a problem, starts an email to us with the value's reference, the dataset version and the source address already filled in.
- By email. Write to corrections@safetycardledger.example (a placeholder: no one reads this address yet).
- On GitHub. A correction form on GitHub will open once the project's repository is public. Until then, please use email.
What to include
- The value's reference, which begins “m-” and is shown in its details, or the address of the page where you saw it.
- What the document says, and where: the section, table or page number, and a link if that part of the document has its own address.
- Which version of the document you read, if you know.
- Anything else that helps, such as a later document that corrects the value.
What happens next
- We re-check the value against the document it was recorded from, and any source you point to.
- If our record is wrong, it is corrected in the next data release. The previous value stays in the value's history, and the value is marked Corrected.
- Either way, the outcome is published in the changelog, with the value's reference. Each decision is recorded with the evidence behind it.
For developers
Developers are welcome to tell us how their results are recorded, through the same channels. A developer's report is checked in the same way as any other, against the published document.
To be written by the owner before launchRight of reply
Whether developers are told before we publish a revision or a discrepancy that concerns their documents, and how long they have to reply. The default under consideration is to notify them and allow five working days (SPEC §15); it is not confirmed.