Governed Autonomy defines architectural requirements for keeping autonomous agent actions within approved mission-scoped authority as agents work across systems. It coordinates identity, policy, execution controls, human intervention, evidence and delegation. Adopters authorize missions and own policy and factual assumptions. Implementations demonstrate the applicable controls within a declared boundary.
A term in wide circulation
Since late 2025, "governed autonomy" has appeared across the industry: in vendor operating models for finance and security operations, in consultancy frameworks for the agentic enterprise, in analyst research, in academic work on agent safety, and in glossaries of agentic identity. The usages differ in scope and motive. They agree on the essentials: autonomy is a dial rather than a switch; policy must be encoded in the runtime rather than appended after it; every agent action must be explainable and auditable, and reversible where reversibility is possible; and the human role shifts from approving individual transactions to governing behavior. The doctrine's own position is that effects differ in recoverability: profiles classify effects as permitted within standing bounds, requiring additional authorization, or prohibited (see the action classes in the v4 text).
That convergence is evidence. When vendors, analysts, and researchers reach independently for the same phrase, the requirement underneath it is real. This doctrine treats independent convergence the same way everywhere it appears: documented, not claimed. See the standards landscape for the method.
What the circulating usages cannot do
Nearly every published use of governed autonomy is an assertion: a product that promises it, an operating model that describes it, a talk that recommends it. None of them can be failed. A description of governed autonomy tells you what good looks like. It cannot tell you whether a given deployment has it, and it offers no way to be proven wrong.
That is the difference between a phrase and a standard. A definition you cannot test is marketing. A standard you can fail is a discipline.
The standard
The Governed Autonomy Doctrine defines the term operationally. The full text is on the Doctrine v4 page; its parts are:
- The 5 Laws state what must be true for any governed agent: agents are identities, not tools; enforcement happens before each effect; governance spans systems; trust does not travel; humans retain the right to intervene.
- The Architecture places control: five planes covering agent identity and lifecycle, execution and tool governance, policy and compliance, human oversight and traceability, and multi-agent trust.
- The Framework sequences implementation: six pillars from agent identity through multi-agent governance.
- The Organizational Maturity Evaluation rates how consistently an organization sustains agent governance, by dimension: Identified, Governed, Continuous. It is separate from any deployment and licenses nothing.
The mandatory runtime baseline (R01 to R18) and the Assessment Companion state what a deployment must demonstrate and how it is assessed. RFC 001 is preserved as a historical proposal.
Provenance
This doctrine did not begin with the phrase. Development began in late 2025 with work on prompt injection and the trustworthiness of agent-retrieved data, matured through the arrival of largely ungoverned agent scaffolding in early 2026, and was first published as a standalone page on 18 March 2026 under its former name, the AI Harness Doctrine. The five-plane architecture followed in May 2026, and the doctrine was renamed in August 2026. See the publication record. Every substantive change is recorded in the changelog.
Where to start: read the Declaration, then the 5 Laws. To assess a real deployment, start with the Assessment Companion.