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 example

{
  "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 reference

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.

Live tool

Live receipt inspection

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

7 years retention

Regional secure storage

Chain of integrity

  1. Receipt N
  2. Receipt N+1
  3. Receipt N+2

Each receipt anchors to the previous execution in its surface.