Governance

OAS operates under the standard MAP governance posture — every dispatch checked, every refusal structured, every decision recorded.

Refusal carries reasons

Audit footprint

Every operation produces audit records in MAX:

• ProtocolInvocation per call (success or refusal)
• AuthorizationCheck on capability evaluation (sampled in prod)
• SecurityViolation on missing capability
• Protocol-specific events via ctx.audit().record(...)

Reconstruct the full trace for any call with MAX::traceability_graph.

Treaty awareness

Cross-organization calls flow under an active MOAT treaty. OAS operations are only callable cross-org if the treaty includes the matching capability. See Concepts → Treaties.

Dissent preservation

When OAS produces output that contradicts prior precedent or peer service output, the disagreement is recorded alongside — not erased. MIMESIS watches this for emergent custom; MOOT may rule.

See also

• Concepts → Governance
• Operations → Governance
• MAX — the audit chain