The 5 Laws of Governed Autonomy

Foundational principles. Each law is independently violatable: a specific architectural decision can breach each one individually.

The three non-negotiables

Governance shall operate in the execution path, at the time relevant conditions must hold. Enforcement shall cover the declared cross-system effect boundary rather than rely on a fragment that the agent can bypass. Agents shall operate under Least Agency: no greater decision scope or authority than their approved missions require.

Least Agency includes the zero case: the mission owner first decides whether autonomous decision-making is warranted. Useful autonomy is then bounded and evaluated; success is not defined solely by how much work is blocked.

01

Agents Are Identities, Not Tools

An autonomous agent is an attributable operational principal with an accountable owner and lifecycle. Its logical identity, running workload, relevant model and tools, assignment and granted authority shall be distinguishable. Shared infrastructure shall not erase who requested, authorized or performed an effect. Identity does not by itself confer a mission or permission.

02

Enforce at Runtime

An agent proposal shall be subject to protected policy and enforcement before the governed effect occurs, with further checks where material conditions can change before completion. Initial admission and after-the-fact detection alone are insufficient. Standing authorization can permit repeated, varying jobs within approved bounds; it does not remove current automated checks or create permanent trust.

03

Governance Must Span Systems

The declared boundary shall include relevant tools, resources, queues, delegated work, persistent state and downstream effects. Controls shall maintain coherent authority, constraints and evidence across that boundary. Exclusions and uncovered paths remain explicit limitations. The doctrine requires coordinated properties, not one vendor, physical appliance or central service.

04

Trust Does Not Travel

A handoff carries a task and relevant authenticated context, not automatic authority. A recipient shall be identified and authorized at its own boundary. Federation is permitted: different resource authorities can grant the authority for their resources. Delegation may narrow or exercise an authorized grant chain; it shall not amplify what the delegator is authorized to grant or bypass receiving policy. An orchestrator need not accumulate every execution privilege held by its workers.

05

Humans Retain the Right to Intervene

Authorized humans shall have an effective means to inspect, interrupt and override governed activity. A profile shall identify the relevant authority and measurable intervention behavior. Prior authorization, interruption, revocation, containment and recovery are different operations. An interruption shall preserve accountable ownership of unfinished work and expose residual effects; neither safety nor successful continuity follows from a stop button alone.

The full v4 text, including the mandatory runtime baseline each Law is implemented through, is on the Doctrine v4 page.