Editorial
Editorial and corrections policy
This page sets out what we publish, what we refuse to publish, and what happens when we get something wrong. Corrections are logged publicly at the bottom of this page rather than edited away.
It exists because a site with a transactional domain and confident claims about other companies' technology owes readers a way to check both.
Updated 2026-08-12
The writing standard
Every substantive page is built the same way: claim, then the evidence for it, then what the evidence actually means, then what follows for the reader.
- The opening answers the question in the title within the first few sentences. Nuance comes after the answer, not before it.
- Numbers, dates, and quotes are traceable to a cited source. A figure with no source does not ship.
- Quotes are verbatim and attributed to the document they appear in, not to a summary of it.
- Where a study tested a reimplementation rather than a production system, the page says so in the same sentence as the result.
- Pages are written to be useful when skimmed and defensible when read closely.
What we cut: rhetorical filler, invented suspense, and the tic of restating the question three ways before answering it.
AI assistance, disclosed
Research and drafting on this site are AI-assisted. Publishing that fact is not a legal formality here; it is the subject of the site.
What that does and does not mean: models are used to gather sources, draft, and cross-check. They are not used to invent facts, generate sources, or fill a table with plausible-looking numbers. Every claim is checked against the source it cites before publication, and anything that cannot be checked is either labelled unverified or cut.
This is also why the evidence ladder is strict. A generative model is very good at producing a confident sentence about a watermark mechanism that no provider has ever described, which is exactly the failure mode the labelling system is built to catch.
Corrections policy
To report an error, use the contact form: give the URL, quote the sentence you are disputing, and add a source if you have one. Reports that identify a specific sentence get handled fastest. You can leave a reply address or stay anonymous. A correction gets published on its merits either way.
What happens next:
- A factual error is corrected on the page and logged below with the date, the page, what was wrong, and what it now says.
- A significant correction (one that changes the answer a reader would take away) is noted on the page itself, not only in the log.
- An update is different from a correction. When a provider changes its documentation or a new source appears, the page's updated date changes and the log does not, because nothing we published was wrong at the time.
- If we cannot verify a disputed claim either way, the claim is downgraded or removed rather than left standing on our authority.
Corrections are never quietly deleted. If a page is merged or retired, its URL redirects and the log entry stays.
Corrections log
No corrections have been issued yet. This log opens with the publication of this policy on 12 August 2026, so an empty table here means nothing has been corrected since that date. It does not mean that nothing ever will be.
| Date | Page | What changed |
|---|---|---|
| None yet | None yet | No corrections issued since 2026-08-12. |
Links, citations, and reuse
External links are editorial. Nobody pays for a link on this site, and no link here is affiliate-tagged.
Sources are listed at the bottom of every page with their status label, so a reader can go to the primary document rather than take our summary of it.
If you want to cite or reuse a diagram, chart, or dataset from this site, that is welcome. A link back to the page it came from is the only thing asked for. If you are reproducing a finding, please also reproduce its sample size and limitations, since those are load-bearing.