What
Canonical action and result
Identify the evaluated action, resource, mode, decision, and time through stable references and digests.
Decision evidence
A Decision Receipt is an immutable record of what AgentGateFee observed, which policy version it evaluated, what result it produced, why it produced it, and which evidence supported the outcome.
THE OPERATING MODEL
The receipt binds the normalized input digest, policy identity and version, decision, stable reason codes, evaluation time, evidence snapshot, and operating mode. It preserves the historical statement even when evidence or policy changes later.
The Decision Timeline links related events and later evidence without rewriting the origin request or accepted receipt. Operators can distinguish observed facts, derived conclusions, missing data, and later lifecycle changes.
WHAT THE RECORD MUST SHOW
What
Identify the evaluated action, resource, mode, decision, and time through stable references and digests.
Why
Retain the immutable policy version and deterministic explanation used when the result was created.
Evidence
Reference relevant evidence state and provenance without copying secrets or unnecessary customer data.
EVIDENCE FLOW
CLEAR PRODUCT BOUNDARY
A receipt proves what AgentGateFee recorded and evaluated under the stated profile. It does not certify legal compliance, guarantee that upstream evidence is true, or establish that a payment, delivery, or outcome occurred without corresponding evidence.
COMMON QUESTIONS
No. Historical receipts retain the original policy version and result. A new evaluation creates a new record rather than changing the earlier one.
No. The canonical record uses minimized fields, identifiers, verification states, and digests instead of secrets or raw provider data.
Not by itself. Execution, payment, delivery, and outcome require their own evidence stages and must not be inferred from a policy decision.
START WITH EVIDENCE