Update, 20 October 2026. The evidence model below is now signed: every OACP artifact carries an ES256 signature and a status list entry, and relying parties refuse an artifact whose signature, scope, expiry or revocation status they cannot check. The UCP, ACP and AP2 preview adapters mentioned in earlier posts were replaced by spec-shaped surfaces. Current status: OACP runtime launch closure PRD.
Summary
OACP gives buyer agents a hard evidence model: source refs, freshness, TTL, revocation posture, risk tier, and blocked capabilities. If those fields do not support the answer, the agent must refresh or refuse.Target Audience
Buyer-agent builders, safety reviewers, and commerce operators.Architecture Diagram
End-To-End Flow
The buyer asks a question. AgenticOrg checks cached OACP artifacts for scope, source, freshness, revocation, and risk. Low-risk questions can be answered with labels. Commitment-bound questions require stricter checks and can only prepare handoff or refuse.What Is Implemented Now
Grantex emits artifact families and non-enablement flags. AgenticOrg checks cache records before answering and uses safe blockers for stale or unsupported requests.What Requires External Approval Or Config
Channel launch, provider capability checks, merchant policy scope, and any future execution controller path.Failure Modes
- Artifact missing from cache.
- Artifact expired.
- Revocation snapshot too old for the action.
- Buyer asks for payment/order/mandate without provider evidence.
- Source and adapter fields disagree.
Safe User Wording Examples
- “I can answer from the current merchant source snapshot.”
- “I cannot invent stock or price beyond the artifact.”
- “No checkout, payment, or order has occurred.”