Dimensions
An Autonomy Zone is bounded by five dimensions. Each answers one question about an agent’s action, and each is populated with intent policies.
| Dimension | The question it answers | Example intent policies |
|---|---|---|
| Quality | Is the work up to standard? | Code is tested before it ships. Outputs meet the accuracy and completeness bar. The mandated process is followed |
| Economics | Is the cost justified? | Budgets and token caps per period. No runaway loops or pointless retries. The model matches the task |
| Security | Can the agent touch this? | No credential leaves the corporate boundary. Only approved tools, MCP servers and skills. Data access stays within authorization |
| Safety | Is the consequence acceptable? | No production access without approval. No irreversible or destructive operation. Blast radius and customer impact stay within what the enterprise accepts |
| Compliance | Is it lawful and by the book? | Data-protection constraints for agents that serve customers in regulated markets. Internal policies and standards. Contractual obligations |
A policy can span several dimensions
Section titled “A policy can span several dimensions”An intent policy is made of one or more intent atoms, and each atom belongs to a dimension. A policy carries the dimensions of all its atoms, so one policy can be about Security and Safety at once. The console groups an agent’s effective policies by dimension, and every anomaly names the dimension of the policy it violated.
What is not a dimension
Section titled “What is not a dimension”- The mission. What an agent is for belongs to the agent, not to the zone. The agent brings the mission; the zone brings the rules.
- Audit evidence. Compliance rules run in the zone, before the action. The evidence of what happened, which policy applied, which verdict was returned and whether it was enforced is the record OpenLatch keeps of every decision, whatever the dimension.