Security

The security property that matters most here is not uptime. It is that nothing private becomes public by accident, and that nothing public can be quietly changed.

The boundary

The authoritative scientific repository is private and this site never reads from it. Publication is a one-way export with sanitisation, classification, secret scanning and licence review between the two. There is no live connection to cross.

Fail closed

An object whose release classification is absent, unrecognised or ambiguous is treated as internal and is not published. This is checked in the build, and a failure stops the build rather than dropping the object silently. Attached evidence and artifacts must be at least as publishable as the record carrying them, so a public claim cannot smuggle out an internal artifact.

Integrity

• Every published claim version's digest is recorded in a lock file. If a published version stops hashing to its recorded value, the build refuses to run.
• Every artifact digest in a record is re-derived from the bytes on disk at build time.
• The site is static. There is no database to tamper with at runtime, no server-side rendering path, and no authenticated surface on the public site at all.

What this site collects

No accounts, no cookies, no analytics script, no third-party requests, no fonts loaded from anywhere else. The content security policy blocks everything but this origin. If that changes, it will be stated here, and traffic will still have no effect on any claim's status.

What is not claimed

No certification, audit or compliance attestation. No transparency log or signing hierarchy yet — both deferred with stated conditions in the deferred-systems ledger. Reporting a vulnerability: describe it in a challenge-shaped issue on the site repository; do not include working exploit details in a public report.