TrigGuard
TRIGGUARD Receipt Explorer

Receipt Explorer

Inspect and verify TrigGuard execution receipts locally. Paste receipt JSON, load an example from the catalog, or open a receipt via URL parameters.

Verification runs entirely in your browser using WebCrypto and the same canonical JSON logic as the trigguard verify-receipt CLI. There is no server-side verification API on this page.

Inspect execution receipts like a transparency log explorer

Search the on-site example catalog, paste arbitrary JSON, or open a receipt from URL parameters. Signature checks use WebCrypto only; optional key discovery fetches published keys only, not your receipt body.

Demo receipt explorer

Example receipts and catalog entries only - not live production telemetry. Footer traces are illustrative.

TG-01 protocol playground - generate, tamper, and verify signed receipts in the browser.

1 Paste receipt · 2 Verify signature · 3 Inspect result

Paste receipt JSON

Edit the canonical JSON below. Aliases such as signature / policy_hash are accepted for offline verify (same canonical bytes as the CLI).

Formatted JSON

-
Receipt fields

Recent receipts

Loads from GET /v1/receipts when your log exposes it; otherwise shows catalog preview. Click a row to load that receipt into the viewer.

Timestamp Surface Decision Receipt id

Optional key discovery performs a GET of published public keys only. To load from a self-hosted receipt log, use ?receipt_id=... and optional receipt_log=https://host (GET /v1/receipts/:id).

Offline receipt verification

This page focuses on operational verification workflow. Receipt field semantics and invariants are canonical in /protocol/receipts and /protocol/spec.

Use this explorer to validate receipts locally; use /docs/verification for verification procedure details and /execution-flow for request-to-receipt lifecycle context.

Independent decision proof

Cryptographic verification on this page runs only in your browser. Optional key discovery fetches published keys only, not your receipt body. For the full lifecycle from request to receipt, see execution authorization flow; for keys, canonical JSON, and Ed25519 details, see the verification guide.

Related protocol documentation