Summary
The reference architecture assigns OACP authority, policy, artifact issuance, verification, and adapter governance to Grantex, while AgenticOrg handles buyer and seller runtime concerns. Actual responsibilities depend on the deployed contract and promoted integration.
Why Cache Exists
Buyer agents need fast answers for non-binding questions like product details, comparisons, and source freshness. AgenticOrg can answer from valid cached artifacts while TTL, scope, source, risk, and revocation checks pass.
Where Grantex Returns
Grantex is involved when AgenticOrg needs authority artifacts, verification, refusal handling, policy changes, adapter governance, or updated evidence refs. Commitment-bound requests still need fresh policy, source, provider, POS, or merchant evidence.
What This Avoids
The design aims to avoid two failure modes: making the authority service a hot-path relay for every chat message, and inventing commerce facts without authority. Valid cache can support discovery; execution requires approved downstream systems.
Topics
Ready to try it?
Explore the public playground, or create an account to evaluate an agent with your own approved data and controls.