Skip to main content

​
OACP Launch Readiness

Canonical end-to-end flow: OACP authority overview. OACP authority is launch-ready only for the scoped path where Grantex issues internal artifacts to an allowlisted AgenticOrg tenant and AgenticOrg uses them for non-binding buyer answers or prepared handoff decisions.

​
Readiness Matrix

GateRequired evidence
Runtime routeAuthority endpoint merged and protected by operator/service auth.
Tenant allowlistAgenticOrg tenant explicitly allowlisted.
Source evidenceShopify read-only sync evidence is redacted and timestamped.
Artifact issue/refuseAll 11 families issue for valid evidence; unsafe requests refuse.
Adapter mappingSchema.org, UCP-style, ACP-style, AP2-style, A2A, MCP, and OpenAPI mappings derive from OACP artifacts.
Cache behaviorValid cache can answer non-binding questions; stale cache blocks commitment.
Provider boundaryPlural/Pine capability evidence is provider-owned and redacted.
RollbackTenant removal and service-token rotation tested.

​
Launch And Rollback Diagram

​
Do Not Claim

Do not claim official protocol approval, broad payment support, all-buyer purchase support, or payment/order success. Current OACP authority supports trust artifacts, compatibility mapping, cache-backed discovery, and prepared handoff boundaries.