Protocol

Execution Receipts.

Cryptographic evidence of authorization. Every action processed by the Gate produces an immutable receipt, signed by the regional authority.

Anatomy of a Receipt

Receipts contain the canonical state of the authorization decision at the moment of execution.

json

{
  "receipt_id": "tg_rec_928f1",
  "authority": "trigguard-us-east-1",
  "decision": "PERMIT",
  "timestamp": "2024-05-04T23:42:11Z",
  "signature": "ed25519:7f2a...9b1c",
  "anchor_hash": "sha256:d8a...2e31"
}

Field	Role
`receipt_id`	Stable identifier for this attestation.
`authority`	Regional issuer that signed the receipt.
`decision`	Authorization outcome (`PERMIT`, `DENY`, or `SILENCE`).
`timestamp`	Decision instant in UTC.
`signature`	Cryptographic binding to canonical payload and keys.
`anchor_hash`	Integrity anchor for offline verification.

Offline Verification

Verify receipts anywhere, even without internet access. Use our open-source verification CLI or native library.

How to Verify

Live Tool

Receipt Explorer

Input a receipt ID to inspect the full cryptographic trace and policy context.

Long-term Archiving

Receipts are stored in regional secure enclaves for 7 years by default, ensuring a permanent audit trail for all AI actions.

Chain of Integrity

Each receipt is anchored to the previous execution in its surface, creating a verifiable chain of authorization state.