AMR proof packet pack
Download the AMR proof bundle with signed pass cases, negative failure cases, checksum ledger, public keyset, and packaged verifier.
Public proof test
The proof packet is live.
Download. Pin the hash. Run the verifier. Reject attacks.
Download a real G‑14 proof pack, run the verifier locally, and watch signed governed actions pass while fake, tampered, or incomplete evidence fails.
Plain English
A buyer can verify the action proof independently.
The proof pack shows the core claim in action: governed AI records survive export, valid records pass, and broken evidence fails.
Production evaluation path
Validate the evidence model, then bring a buyer-specific action class into a controlled production evaluation.
No dashboard trust required
The proof path centers exportable artifacts and local verification instead of screenshots, hosted-only demos, or claims that disappear outside the UI.
Evaluation path
Skepticism should end in a verifier result.
A buyer can move from first landing to local proof before deciding whether to spend time with the team.
Inspect the proof artifact
Start with a signed packet pack that leaves G‑14 as a downloadable object.
Verify locally
Run the included runtime verifier against the positive packet set and the named negative corpus.
Escalate only after evidence holds
If the artifact verifies, the next step is a focused production evaluation for the buyer action that matters.
Boundary
Public proof and deployment proof are connected, but not the same claim.
The proof pack earns the next conversation. Deployment proof still depends on the buyer environment, action class, and governance evidence.
Buyer-run artifact
A free local test that verifies signed AMR proof packets and failure cases generated from the runtime pipeline.
Controlled evaluation
A buyer-specific review that replaces generic claims with the action class, policy, signer topology, and evidence boundary they need to assess.
Deployment proof
A customer environment has to discharge its own assumptions. This test proves the artifact behavior, not every future deployment.
Evaluation path
The proof claim becomes executable by the buyer.
The buyer gets an artifact first, then a path into a governed production evaluation.
Before this
Compliance
Proof-bearing runtime compliance turns governed AI actions into independently checkable records.
Open ComplianceCurrent step
Test
The test turns the proof claim into a downloadable local verification path.
You are here
Next step
Request access
A verified artifact leads into focused production evaluation.
Open Request access