# Trust Receipts

Unstable

## Anatomy

Each receipt carries: `id`, `avc_id`,`actor_id`, `policy_hash`,`action_descriptor`, `outcome`,`custody_hash`, optional `prev_hash`,`timestamp`, and a `signature` over the canonical encoding.

## Outcomes

`permitted`, `denied`, or `partial`. Denied attempts produce receipts so the absence of authorization is itself attested.

## Custody chain

Each receipt's `custody_hash` binds it to its`prev_hash`, forming a per-actor hash chain. The chain is anchored to the EXOCHAIN ledger at block boundaries.

## Verification

Receipts are verifiable offline given the issuer's public key, the AVC, and the policy in effect at execution time. The SDK exposes a verifier that returns a structured result with reason codes.