This page proves — in your browser, with no tools and no trust in us — that the cryptographic code this server is serving right now matches the signed release manifest. It fetches every listed artifact, hashes it locally with WebCrypto SHA-256, and compares against the ML-DSA-signed manifest.
loading manifest…
The manifest is signed with post-quantum ML-DSA-65. This page shows you the canon and signature;
verify it with any ML-DSA implementation against the pinned issuer key (GET /svc/api/messages/v2/prov/issuer — pin it once),
or in one call with the NULL SDK. Every hash change is appended to the public witness chain under
release:<file> — a swapped build is permanent, provable history, replayable by anyone.
…
This is tamper-evidence, not prevention: a malicious server could serve a targeted page once — but every independent monitor of this endpoint turns that into a provable event. Reproducible-build steps: BUILD.md (the current 200A bundle does not yet rebuild byte-for-byte; the next release will, with published build hashes). This verifier page is itself served by the same server — for maximum paranoia, save this HTML and open it from disk (it targets the live origin; the server permits it), or run the curl recipe in BUILD.md — no browser required at all.