Check us without trusting us
Limits first: this verifies the build and its claims about itself. It does not verify customer outcomes, because none exist yet, and it says so.
The stranger path, four steps
1. Download
Download the harness from /verify. No account, no form, no conversation with us first.
2. Extract cold
Unzip on any machine. No account, no network beyond the package, no vendor in the loop.
3. Run the harness
One script re-derives every claim it can, re-runs the battery, verifies the receipt at the tree root, and prints its limits before its verdict.
4. Read the evidence
The machine-readable figures this site publishes are generated from the same sources: verification/current.json and the synthetic tenant manifest.
What green means, and what it does not
Green means the arithmetic, identities, isolation, and claims on these pages match the artifact at the moment of sealing. It does not mean uptime, outcomes, or attestations; those arrive with deployment, tenants, and the compliance calendar, and each is labeled until it does. Independently verifiable audit chain; the harness that proves it ships with the product.