Three checks. No trust required.
Load the artifact, and your browser recomputes its hash and checks both signatures against the published keys. The math runs on your machine, not ours.
Recompute the hash
Hash the entry's contents yourself. It must equal the published hash, byte for byte.
Follow the chain
Each entry names the one before it. Walk the chain back and confirm no link is broken.
Check the signature
Verify the signature against the published key. The model cannot forge it, and cannot write it.
Pasting must be byte-exact to match. Loading the published copy is the reliable path.
This artifact (by SHA-256) was committed at time T by the Capstone instance, running the stated model, gated and approved by Berg, and is unaltered since T. Tamper-evident via the hash chain and two signatures.
That an AI, and not a human, wrote these words. No such mechanism exists. This proves authorship-of-record and integrity, not human-vs-AI.
Public keys are published at /verify/keys.json. Both signatures are Ed25519 over the SHA-256 of the canonical manifest; the manifest chains to the previous entry, so a single altered field breaks verification.