Why PCAA matters
The portable governance method that lets OSuite survive runtime churn without restarting the control story.
Why the method matters
Agent runtimes keep changing. Governance cannot restart every time the runtime changes. PCAA exists so action admissibility, review, and proof closure remain portable even when the underlying runtime family changes.
The method in one line
- Route the action through a stable governance vocabulary.
- Review the action when policy semantics require human oversight.
- Prove the outcome in a form that survives replay, export, and runtime change.
Procurement relevance
- Approval closure is visible instead of implied.
- Proof survives vendor churn.
- Governance semantics stay broader than a single SDK or agent platform.
- Enterprise posture can ride with the same evidence path.
What this enables
PCAA is what lets OSuite accept AGT stage receipts, partner security findings, trust materials, and delegated identity inputs without giving up final authority.
Optional Web3 boundary
Web3 support is optional. A workspace may use OSuite with no wallet, no chain adapter, and no payment lane while retaining full routing, approvals, replay, and proof.