PCAA
Read this page to understand what PCAA is, what it controls, and how route-review-prove closes final authority across changing runtimes.
What it is
PCAA is OSuite's control model for high-value agent actions. It treats the governed action itself as the trust-bearing object and keeps routing, review, and proof on one certificate path.
When to read this page
Read this page when you need to explain:
- who has final authority for a governed action
- why approval and proof stay attached to the same action record
- how OSuite can accept runtime or partner inputs without giving away control
The shortest mental model
| Step | What happens |
|---|---|
| Route | OSuite normalizes the action and decides the posture it requires |
| Review | OSuite escalates when risk, ambiguity, or policy requires human oversight |
| Prove | OSuite closes the action into replayable evidence and exportable proof |
What you see in OSuite
In Studio and exported artifacts, PCAA shows up as:
- one governed action vocabulary that survives request, review, replay, and proof
- approval receipts that explain who decided and why
- runtime receipts that can be attached without replacing final authority
- buyer-facing packets that still resolve back to the same action record
What it does not do
PCAA does not replace the runtime itself. It does not turn a partner receipt into final authority, and it does not treat transport evidence as proof closure by itself.
Where to go next
Workspace governancefor workspace control ownershipNeutral runtime contractfor runtime families and authority boundariesEnterprise assurancefor buyer-facing evidence and packet flow