Prove · For the Auditor — “Can you prove it?”
Prove every decision, forever.
When an agent takes an action, the question a week later is always the same: what happened, who allowed it, and can we prove it without trusting the vendor who ran it?
Aarmos writes a signed, tamper-evident receipt for every action. Anyone — auditor, regulator, incident response — can verify it offline with a portable Apache-2.0 verifier. No Aarmos backend required. Evidence outlives the vendor that produced it.
A receipt reads in one line: Decision → Participants → Verdict → Evidence. It also keeps “evaluated and denied” apart from “could not evaluate”, so a reader is never left guessing which one happened.
Read the Field Guide chapter →Verify in 10 seconds
# any machine, no Aarmos account $ brew install aarmatix/tap/avar $ avar verify ./run.avar.zip ✓ 42 entries · chain intact · signature valid
Or drop the same bundle into /trust/verify — the verifier runs entirely in your browser.
- Verify a receipt (paste JSON) →The fastest way to see it work: paste a signed receipt, watch the signature and chain-integrity checks run in your browser. Zero upload, zero Aarmos backend.
- Verify a bundle in your browser →Drop any receipt bundle — checks signatures, chain integrity, and package contents locally. No upload.
- Replay a signed decision →Rerun a governed action against the pinned policy. Same inputs, same verdict, same rule — deterministic evidence, not a snapshot.
- Receipt specification →The canonical format and verification math. Third-party implementations welcome.
- How receipts work →Every governed tool call produces a signed entry chained to the previous one. Break the chain, break the proof.
- Trust & compliance →Compliance mapping, signing-key policy, and release attestations.