1Scope
This policy covers every factual statement on this website: statements about the company, statements about the platform, and statements about third parties — the incidents on the Ledger and the instruments on the standards pages.
2Reporting an error
Email info@admissiblelabs.com with the page, the sentence, and what you believe is wrong. Pointing us at a primary source helps, but is not required. We correct factual errors on notice: once we can confirm a statement is wrong, we change it or remove it.
3The Ledger
Ledger entries rest on primary sources — judgments, regulators' publications, and named contemporaneous reporting — and each entry cites its sources. If an entry is shown to be wrong, we correct it and log the correction, dated, on the Ledger page itself, so the record of the error is part of the record.
4The claims register
Factual sentences about our own capabilities are tied to a named verifier. The register behind them, at /verified, regenerates on every build: repository-fact checks re-run at each build, test and source verifiers re-run in dated full runs, and every claim shows the date of its last run. A claim that fails is removed at the next build, and the struck claims are listed publicly with the reason. A sentence we cannot verify does not stay up while we look into it. It comes down.
At this build there are 27 verified claims, 7 struck and 2 held, read at commit 9865101c.
5Corrections and updates
A correction fixes something that was wrong when we published it. An update reflects something that changed afterwards: a law amended, an incident developing, a capability newly verified. Updates happen silently with each build, and the build stamp at the foot of every page records when the copy was produced. Corrections under clause 3 are logged; the distinction is kept so that the log stays meaningful.