Prove

The day someone stops trusting your word, the burden flips. Screenshots don't count. Logs you control don't count. Even a vendor dashboard is just another party asking to be believed.

What you need is portable evidence that can be checked without contacting the service that produced it.

A vendor-controlled log can describe a consequential action, but the reader still depends on that vendor to present and interpret it. Portable signed evidence gives another party the supplied artifact, its provenance, and an independently supplied trust root.

Prove asks what was recorded about the Decision, applicable Authority, Attempt, and observed Effect of a governed consequence — and whether that evidence can be verified. Verification establishes artifact integrity and that its signatures validate against the supplied trust root. It does not itself prove execution, path coverage, safety, compliance, or a downstream Outcome.

The receipt specification is not currently publicly published. Public verification is available in the browser or through the open@avar-standard/verify library, within their supported formats. An Aarmos account is not required to check a supplied artifact.

• Receipts are signed records associated with governed consequences.
• Evidence carries or references recorded facts, provenance, and integrity material.
• Effect is separate and reaches only the boundary’s declared evidence ceiling.
• Unknown, uncertain, unavailable, and not tracked remain explicit.

A regulator asks about a specific payment attempt from last April. You provide its receipt bundle and the applicable trust root. They use the browser verifier or public verifier library on their laptop. The standalone binary is not publicly distributed. The verifier checks the supplied artifact and reports whether its integrity, signatures, chain, and recorded provenance hold. If no Effect or Outcome evidence exists, the report does not invent either one.

Why not just give them the logs?

A portable signed artifact lets another party check integrity and signatures without relying on a vendor-controlled viewing service. They still need an independently supplied trust root and must respect the artifact’s evidence ceiling.

What if Aarmos disappears?

The receipt format and verifier are portable. Supplied evidence can be checked without contacting an Aarmos service, provided the verifier, artifact, and independently supplied trust root remain available.

Does a verified receipt prove the action happened?

No. A valid receipt establishes what its verification result actually covers. An Effect requires Effect evidence, and an Outcome requires Outcome evidence. Unsupported or unreadable evidence is reported as unable, not failed. See the verifier.

• Prove
• Govern
• Run
• Receipts
• Evidence