Signed packets, verifier receipts, negative corpus, public keyset, offline verifier wheelhouse.
G‑14 Verify
Verify it on your machine.
The AMR v0 proof pack is a downloadable diligence artifact: five signed proof packets that must verify, six negative-corpus packets that must fail with named checks, the public keyset, and an offline verifier. No account and no dashboard — the receipts either prove themselves on your hardware or they do not.
Hold, operator review, release amr-evidence-packet-9f34c049c4bb
t+200.0sProposedzone_authorize: AMR amr-12 requests entry to zone-g3, warehouse-east.
t+200.0sHeldStructural lane holds the action; dispatch suppressed; robot keeps safe state hold_position.
t+220.0sReviewedOperator allow: "Zone clear; camera and scanner evidence checked."
t+220.0sReleasedDispatch executed through the governed fleet channel (operator_allow).
t+221.0sSealeded25519 product signature over the canonical packet body.
Times are seconds on the demo-run clock. Permit industrial-permit-4c400c4da12e; ed25519, key g14-customer-proof-demo-key. Verifier result: pass — 225/225 checks, signature valid.
DownloadFour files. The zip is the artifact; the rest let you check it.
Read the proof model The pinned inventory: every artifact the pack claims to contain, by name and hash.
One line per file. Run sha256sum -c against it before trusting anything else.
Offline commands for checksum validation, local installation, positive verification, and negative-corpus rejection.
Pack sha256: b00b2ce5298e2795b7453fbaa8558ab6b7a472423375cdabd5d3478ab7495a55 · generated April 25, 2026.
Verify offline
Five commands. No network after the download.
The wheelhouse ships every dependency, so the verifier installs and runs with the network unplugged. The verifier requires Python 3.10 or newer.
unzip g14-amr-customer-proof-pack-v0-20260425.zip -d amr-pack && cd amr-pack
sha256sum -c SHA256SUMS.txt
python3 -m venv .venv && . .venv/bin/activate
pip install --no-index --find-links verifier-wheelhouse agent-control-runtime
python tools/verify_pack.pyCaptured output of the final command — agent-control-runtime 0.1.0, Python 3.10, July 19, 2026:
{"negative_packets_failed_as_expected": 6, "positive_packets_verified": 5, "status": "pass"}Negative corpus
Six packets that must fail.
A verifier that only says yes proves nothing. These six packets are broken in specific, named ways, and the verifier must reject every one of them for the pack to pass.
A packet with no product signature must be rejected, not warned about.
One altered byte under an intact signature must break verification.
A packet that cannot prove its sections belong to the sealed body must fail.
A packet missing its cross-view transcript binding must fail.
A signature from an undeclared key must not be trusted.
Signer topology that collapses independence must be rejected.
Claim scopeWhat this artifact proves, and what it does not.
This artifact demonstrates that the runtime generates signed packets, positive verifier receipts, and named negative-corpus failures through one verifier path. It is not a certification, a customer deployment attestation, or a claim that any external production environment has been assessed.
Next step
Bring the workflow where a receipt like this has to survive review.
The pack shows the mechanism. A private proof runs the same mechanism against one of your consequential action paths.