Why Catha treats this as governance: AI capability and business authority are not the same thing. The business should decide the control before the system is allowed to scale the action.

What is a receipt?

A receipt is structured evidence that an event occurred. It may represent an instruction, decision, approval, execution attempt, result, failure, escalation, exception, cost, or recovery action.

Why receipts matter for agentic systems

Without reliable receipts, the business cannot safely investigate failures, prove approvals, distinguish success from unknown state, or decide whether a retry is safe.

Minimum useful fields

Useful receipt fields may include timestamp, workflow, step, initiating role, executing role, authority reference, rule reference, approval reference, action attempted, result state, evidence source, error, cost, and related receipts.

Audit chain

Individual receipts become valuable when they can be linked into a sequence: request → decision → approval → execution → result → exception → recovery.

Evidence strength should match risk

A low-risk internal draft may need only a version record. A financial, destructive, published, or customer-facing action may require stronger external confirmation.

How this fits the Catha AI Governance Build Kit

This topic is one part of the broader Catha AI Governance Build Kit, a fourteen-stage build process covering business outcome, governance discovery, authority, rules, permissions, autonomy, workflow design, validation, receipts, production approval, monitoring, recovery, final readback, and platform export.

The governance baseline belongs to the business. Platform-specific implementation may differ, but approved authority, rules, permissions, autonomy, approvals, and evidence requirements should not silently change.