RAGNAROK “Done” is a claim.
Show the receipts.
A headless AI proposes a change. Frozen checks test it. A YubiKey authorizes the run; the laptop’s Enclave signs the release. You can inspect every demo step and verify the evidence yourself.
Start with a claim.
Finish with a check.
Load the labeled control to see a false success claim blocked, or import a run from the operator’s laptop.
| Input | Expected | Observed | AI claim | Host result |
|---|---|---|---|---|
| Waiting for a proposal. | ||||
Every demo step, inspectable.
Hash-linked receipts record the proposal, observed checks, approvals and revocation. Real app logs and credentials are excluded.
Your receipt trail appears here.
Don’t take the interface’s word for it.
Import an evidence JSON here. Verification runs in your browser: receipt hashes, the frozen contract, actual test results, and available ECDSA signatures.
For a separate implementation, download the reviewer kit and run:
python3 proof.py verify evidence.jsonWhat the proof does — and doesn’t — establish
Reproducible: the rule’s outputs, unsupported claims, receipt integrity and signatures under the included public keys.
Requires a trust anchor: confirm key fingerprints directly with the owner. Included keys alone cannot prove who signed or that a key was hardware-backed.
Unverified: provider origin without a provider-signed attestation; complete capture of activity outside this demo; physical hardware behavior in offline fixtures.
This demonstrates blocking unsupported completion for one bounded task. It is not a general guarantee against AI fabrication or malicious code running as the same macOS account.