| One bounded door | All agent actions cross one gateway. Tools are scoped to an identity and every decision is audited. | A central policy enforcement point, so teams add tools without adding credentials. | Throughput, tenant isolation and who owns the policy. |
| One source, two consumers | The cockpit and the agents read one relationship service. A same-answer check compares both. | A service catalog and system map that people and agents query the same way. | Keeping it fresh across many teams' data. |
| Governance as code, honestly labelled | Rules are typed records in git. Each says mechanised, reviewed or honour system. | A control library that reports real enforcement, like control-effectiveness in an audit. | Label drift across hundreds of rules. |
| Graduated autonomy | Actions are sorted by blast radius: green proceeds, yellow asks, red is never autonomous. Authorization layers run in shadow before they enforce. | Risk-tiered approval for agent actions, tuned with evidence. | Thresholds against real incident cost. |
| Missions with separation of duties | The session that builds a change never merges it. An independent review comes first. | Change management for work done by agents. | Reviewer capacity and its cost. |
| Degraded mode | Two sites, the same playbooks and a documented repair path. | Break-glass access and recovery for the agent plane itself. | Failover drills at real scale. |