Versioned input
Stable normalized facts
Canonical inputs reduce differences between protocol adapters and expose unsupported or unavailable evidence.
Deterministic policy
A Policy Engine for Agent Commerce Decisions
Evaluate normalized agent-commerce evidence against immutable policy versions. The same material input and policy version produce the same result, explanation, and evidence references.
Current product boundaryPolicy evaluation is available in non-enforcing OBSERVE and Shadow Mode workflows.
THE OPERATING MODEL
Rules should be inspectable before they influence commerce.
Provider payloads are normalized at the edge. The policy core receives typed facts about identity, authority, resource, commerce context, attribution, and integrity instead of protocol-specific objects.
A result retains the exact policy version, normalized input digest, evaluation time, decision, stable reason codes, and minimized evidence references. Later policy changes never rewrite historical results.
WHAT THE RECORD MUST SHOW
Determinism turns policy into reviewable evidence.
Versioned rules
Immutable policy lineage
Every result points to the exact published policy version used at the recorded evaluation time.
Explainable output
Decision and reason codes
Operators can see why the engine returned allow, block, review, or require-authorization guidance.
EVIDENCE FLOW
A deterministic evaluation path
- 01Receive a normalized Agent Event
- 02Validate evidence state and provenance
- 03Select the immutable policy version
- 04Evaluate typed conditions
- 05Apply the decision-combination rule
- 06Issue an immutable Decision Receipt
CLEAR PRODUCT BOUNDARY
Policy evaluation does not execute the customer action.
The current customer-facing surface records OBSERVE results. It does not approve a payment, alter a cart, block a checkout, or call a downstream enforcement adapter.
COMMON QUESTIONS
Understand the evidence before changing the workflow.
Can policies differ by merchant or resource?
Policies are scoped and versioned. A result records the applicable policy and resource context so historical decisions remain reproducible.
What if required evidence is missing?
Missing evidence stays missing. It is not converted into a positive authority or attribution fact, and the explanation records the resulting limitation.
Does the policy engine replace a payment provider?
No. Payment processing, settlement, custody, and provider authentication remain outside AgentGateFee.
START WITH EVIDENCE