AI Agent Orchestration Platform · View 22 of 32 · 4 · Runtime
Decisions
- Policy is authored centrally and evaluated locally: the control plane signs a Rego bundle, a sidecar in every worker evaluates it
- Local evaluation keeps decisions sub-millisecond and means a control-plane outage cannot cause policies to fail open
- Scopes compose most-restrictive-wins; a project cannot widen what the organisation forbade
Governed by policy
- Which models, which tools, which data, which actions need approval, maximum spend, maximum duration, maximum tokens, allowed regions and providers, retention, and content restrictions
- Policies are versioned, auditable and evaluated at runtime, at organisation, project, agent and workflow level
- Azure Policy governs the infrastructure; this engine governs agent behaviour, and the two are deliberately not the same system
Risks
- A signed bundle can go stale if a worker cannot reach the publisher; bundles carry a maximum age and a worker refuses new work past it
- Rego is a specialist skill; policy authoring is owned by a small central team with a reviewed template library