Concept

AVAR receipts

Recorded gate outcomes on supported governed paths produce an AVAR — an Aarmos Verifiable Action Record. Receipts are hash-chained (each entry references the previous entry's hash) and Ed25519-signed, so changes within an exported chain can be detected during verification. Verification does not establish that the export contains every event or that a downstream action succeeded.

Why portable matters

Exported receipts can be checked with the browser verifier or the public verification library. The standalone avar binary is not publicly distributed. Verification checks integrity; attributing a signature to an issuer requires a separately trusted key.

What's inside

• Actor, tool, argument shape (credential-scrubbed), and gate outcome
• Policy-bundle fingerprint at decision time
• Timestamp and prior-entry hash
• Signature over the canonical bytes

See the AVAR overview and rotation details in the key-rotation runbook.