Explanation · Understanding why it is the way it is
Verifiability as a principle
Nothing asserted, everything measured: why every figure has a source and every date a state.
On this page
The platform's claim is not that its statements are true, but that anyone can check whether they are.
For entries
Every interface itself names the minimal harmless probe it can be checked with. The checker runs it and records instant, probe and address. The entry page shows three states, never more: never checked, passed, failed. Nothing is shown as passed that was not measured.
For the platform itself
The modules of the infrastructure page live in a file (modules.json). Every piece of evidence carries a source and a date; values marked «recounted» are counted from the source by the generator at every build, and if the figure differs the build fails. The first run of this gate found two stale statements on the platform's own page. That is the point.
For this documentation
Every page carries a state date and a review date, names its source in the repository and exists as Markdown beside its HTML. Commands in tutorials and guides run in the check pipeline. A page that no longer holds is an error one can report, not a text that ages quietly.