Autonomy to do what?


With consequences for whom

The Boundary Framework decides how much autonomy an AI system should have by looking at where its consequences land: in the physical world, in law and organizations, or in a particular person's life.

The same autonomy can be right in one setting and wrong in another. Governance follows the consequences, not the technology.

Learn about The Boundary Framework:


Video coming soon

The first Boundary Framework video will appear here.

Three boundaries


Where consequences land

Every action an AI system takes meets the world at a boundary. Each boundary type shows errors differently, corrects them at a different speed, and calls for a different kind of oversight.

Implementation

The physical world

Governance
Extend established safety engineering: certification, failure-mode analysis, redundancy and containment.
Autonomy
High autonomy within an approved safety regime.
A spray drone treats a field, row by row.

Institutional

Legal, regulatory, contractual, financial

Governance
Conditional autonomy: defined parameters, accountability tracing, and human review for interpretive or high-stakes matters.
Autonomy
Bounded autonomy for routine, well-specified tasks.
$1,240 $860 $8,600 $495
An agent pays fees. One has an extra zero.

Normative

Access, opportunity, liberty, health, dignity

Governance
Preserved human agency: the AI system may assist, and a person takes the consequential action.
Autonomy
Assistive role. A person keeps the final say.
An AI screens three applicants and rejects two.

When an agent crosses a boundary


Goals drift. Oversight has to follow.

AI agents break goals into sub-actions. A goal set at one boundary can produce sub-actions at another, while the system's autonomy setting stays the same. Each step can look routine. In its consequences for a particular person, it is not.

63%

of recorded AI incidents involved boundary crossing, in a Bacon Center analysis of 1,786 incidents in the AI Incident Database.

Put it to work


The governance cycle

Organizations apply the framework at design, at procurement and at periodic review, and repeat it over the life of a deployment.

  1. MapIdentify every boundary the system's actions will touch, including foreseeable sub-actions.
  2. ClassifyAssign each action a boundary type and judge how serious its consequences could be.
  3. CalibrateMatch autonomy and oversight to each action's boundary type and risk class.
  4. ArchitectBuild boundary awareness in, so crossings go to a person by design.
  5. MonitorWatch for new crossings as goals, tools, data and permissions change. Then map again.

Read and use the framework


Free under CC BY 4.0

You may share and adapt this material for any purpose, including commercial use, if you give credit, link to the license and say whether you made changes. The names and logos of Iowa State University and the Murray G. Bacon Center for AI Ethics in Business are not covered by this license, and adapted versions may not use them in a way that suggests endorsement by the university or the Center.

Suggested citation

Howard, M. D., & Murray G. Bacon Center for AI Ethics in Business. (2026). The Boundary Framework: Specification, version 1.0. Iowa State University.