Method

What is published here

13 datasets, 1,933 records, assembled from 68 publishers. Each record states one fact — an error code and its meaning, a version and the date its support ends, a threshold and what it triggers — and each has its own page and its own stable URL.

The datasets are chosen for a particular shape of question: one with a definite public answer that is scattered across many publishers, changes over time, or varies by jurisdiction. Those are the questions where a confident answer from memory is most likely to be a wrong one.

How a record is made

• Sources are chosen first, and recorded. Manufacturer documentation, regulators, standards bodies and official support pages before anything else.
• Values are copied, never normalised. If a source prints a code one way, that is how it appears here, even where another convention would be tidier.
• Each value is stored with the span of text it came from — not a paraphrase, not a summary, the passage itself.
• Every claim is then checked back against that passage before the page is built.
• Nothing is filled in. Where a source does not state a value, the record omits it. A plausible value is worse than a missing one, because it is indistinguishable from a checked one.

What the three markings mean

• UnmarkedStated by the cited source, and the quoted passage contains it. This is the ordinary case.
• our readingOur classification of what the source says, not its words. Some comparisons only exist once differently-worded rules are put on one scale — that scale is ours, and it is labelled wherever it appears. The quote below it is the evidence; the judgement is ours and can be wrong.
• unconfirmedTaken from the cited source, but we could not mechanically tie it to the quoted passage. It is shown rather than hidden, because the value and the quote together tell you more than an empty field does.

What “verified” does not mean

It means the value appears in the passage quoted from the page cited, on the date shown. It does not mean the source is correct, that it is still correct today, or that the passage is the most authoritative statement available. Checking that a page says a thing is not the same as checking that the thing is true, and we do not claim the second.

This is why the quote is on every page. You do not have to take the value on trust: follow the link and read the sentence.

Freshness

Reference data decays. Every dataset carries the date it was last checked against its sources and a date by which it is due to be checked again. When a page passes that date without a re-check, it says so at the top rather than looking current.

Pages are not deleted for being stale — a stale page that says it is stale is more useful than a broken link. Anything found to be wrong is corrected or withdrawn.

Disagreement between sources

Where two authorities state different values for the same thing, both appear on the same page, each with its own source, its own quote and its own date. Choosing between them would hide the most useful part of the answer, which is that the disagreement exists.

Corrections

An error in a value, a quote that does not support what it is attached to, or a source that has changed — all are worth reporting, and all are acted on rather than argued with. A contact address for corrections is published with the next release of this page.

Reuse

Facts are not owned, but a publisher's expression of them can be. Each dataset carries its own licence, stated on its page, and each source's terms were checked before its rows were included; rows from a source whose terms forbid reuse are not published. If you use this data, cite the original sources — they are listed on every record for exactly that reason.

For machines

Every record page is also served as Markdown at the same path (append index.md), every dataset as JSON at /<dataset>/data.json, and the whole catalogue at /catalog.json. Pages carry schema.org Dataset and Article metadata, and each record opens with a single plain sentence stating the fact, so there is something to quote that is not a table cell. No JavaScript is used anywhere on this site and no request leaves it — the HTML you fetch is the whole page. AI crawlers are explicitly allowed in robots.txt.