Plane 05

Evidence

The receipt generation and binding layer. Every governed execution produces a cryptographic receipt. Receipts are the mechanism by which execution becomes provable.

This page explains how receipts are generated. To verify them, see the Prove It hub.

Receipt Properties

Evidence exists at authorization time.

Receipts are generated at authorization time

A DecisionReceipt is produced when Governance issues a Decision, before execution proceeds. It is a contemporaneous artifact of the governance event.

Cryptographically bound to policy and agent

Every receipt carries the PolicyHash of the active policy version, the AgentId of the requesting system, and a ledger reference that anchors it causally to the Spine Ledger.

Ed25519-signed at issuance

Receipts are signed with Ed25519 at the moment of issuance. The signature binds the receipt contents to the issuing governance authority.

Evidence Packs bundle receipts for independent verification

An Evidence Pack is a self-contained, cryptographically sealed bundle of execution artifacts. Verification requires no access to Keon infrastructure.

Boundary

Generation and verification are separate concerns.

This plane documents how receipts are produced and bound. The Prove It hub documents how to verify them independently, without running Keon.