If this site disappeared tomorrow, the record would not
A measurement is only worth something if it outlives the organisation that made it — including the case where that organisation is the problem. Our published record is mirrored on hosts we do not control, so no single takedown removes it. This page says precisely what that does and does not buy you.
Measurement, not certification. Board unreachable from this browser — read it yourself at /api/gspc
One host, one takedown, no record
Most assurance evidence lives in exactly one place: the assessor's portal. That is convenient right up until the assessor changes the file, loses it, goes out of business, or has a reason to want the finding gone. If the only copy of a result is held by the party the result is about — or by the party that produced it — then the result is a courtesy, not evidence. The fix is not to promise better behaviour. It is to put copies where nobody, us included, can quietly reach them.
- PainEvidence held in one portal can be edited or withdrawn without trace
- Pain"Trust our archive" is the claim least worth trusting
- You getCopies on independent hosts remove the single point of removal
- Only hereIncluding removal by us — that is the point, not a side effect
Publish widely, verify locally, anchor externally
Three mechanisms, all of them ordinary and all of them checkable. We publish the same signed artefacts to several independent hosts. Verification runs in your browser against the trust root, with no call to us — so checking a card does not depend on our servers being up or our goodwill lasting. And the board is deposited with an external archive that issues a permanent identifier we do not administer. None of that is exotic. It is just refusing to be the only copy.
- You getPublished to Hugging Face, PyPI, GitHub and Zenodo — each checked live
- You getVerification is client-side: no account, no server call, no permission
- You getDOI 10.5281/zenodo.21991104 — an archival identifier we do not control
- Only hereWikidata Q141128616 and Companies House 16939677 for the entity itself
This is redundancy. It is not indestructibility.
Copies on several hosts are harder to remove than one copy. That is the whole claim, and it is worth having. It is not the same as being censorship-proof: every host here has terms, a jurisdiction and an off switch, and a determined actor with legal reach could pressure several of them. We have made that mistake in public before — we published a claim that three nominally independent legs would survive each other's failure, measured the effective independence at 1.21 against those three legs, and withdrew it in DR-0007. We are not going to re-make it with different nouns.
- PainEvery mirror has terms, a jurisdiction, and an off switch
- PainIndependent hosts are not independent failure modes — we measured that once and were wrong
- You getWhat survives is a real, small, checkable property: no single takedown
- Only hereThe retraction is published, not buried — see the corrections ledger
What this page does not claim
We publish the limits with the results. Everything below is something a reader could reasonably assume from a page like this one — and each is something we cannot presently evidence, so we say so rather than let the assumption stand.
- We do not claim the record is indestructible. It is mirrored. Those are different words and the difference matters.
- We do not claim censorship resistance. Every host we publish to has terms of service, a jurisdiction and the ability to remove content, and an actor with enough legal reach could pressure more than one of them.
- We do not claim independent hosts give independent failure modes. We published a claim of exactly that shape once, measured the effective independence at 1.21 against three nominal legs, and withdrew it in DR-0007. That retraction stands and this page is bound by it.
- We do not have a Software Heritage identifier. The source deck listed SWHID as one of three pillars; there is no SWHID anywhere in this codebase, so it is not on this page.
- We do not describe the DOI as immutable. It is an archival identifier administered by someone else, which is the useful property — not permanence we can promise on their behalf.
- We do not claim the mirrors are complete or continuously monitored. Each link on this page returned HTTP 200 when the page was written; that is a check, not a guarantee, and there is no uptime claim attached to it.
Coverage on this page is never typed by hand. Board unreachable from this browser — read it yourself at /api/gspc Corrections to anything we have published live in the refutation ledger — append-only, never a silent edit.