Skip to content

Understanding the Spectrum of Agency in AI Systems

Not every AI system should be fully autonomous. One of the most useful design decisions is choosing the right level of agency for the problem.

This page treats agency as a spectrum, from static outputs to collaborative multi-agent systems.

LevelNameWhat the system can doTypical examples
0No agencyReturn fixed or tightly scripted outputsFAQ bots, static classifiers behind a simple UI
1Routed workflowsChoose between predefined branchesworkflow bots, intake triage, template routing
2Tool-using assistantCall external tools in bounded waysinternal copilots, retrieval assistants, support agents
3Autonomous agentPlan and execute multi-step tasksresearch agents, coding agents, automation agents
4Multi-agent systemCoordinate several specialized agentsplanner-worker systems, reviewer-executor systems

At this level, the system does not really decide. It returns fixed or narrowly constrained outputs.

Use this when:

  • requirements are stable
  • risk of wrong action is high
  • the workflow is deterministic

The system can inspect an input and select a predefined path.

Use this when:

  • the space of outcomes is known in advance
  • you want some flexibility without open-ended autonomy
  • observability and compliance matter more than open exploration

This is often the first level where an AI system becomes genuinely useful in business workflows.

The system can:

  • search
  • retrieve
  • call APIs
  • query data
  • synthesize results

but within clearer boundaries than a full autonomous agent.

At this level, the system can plan, adapt, and continue over multiple steps with minimal intervention.

Use this when:

  • the task is open-ended
  • there are several possible paths to success
  • the system must recover from partial failures

This is where pages like AI Agents and Agentic AI become essential.

This is useful when one role is not enough.

Examples:

  • a planner creates the work plan
  • a worker performs the action
  • a reviewer checks the result
  • a coordinator decides whether to continue

This can improve specialization, but it also increases complexity and coordination cost.

Choose the lowest level of agency that can still solve the problem.

Questions to ask:

  1. Does the system need tools, or is generation enough?
  2. Does it need to recover from failures on its own?
  3. Does it need to act, or only recommend?
  4. Can the workflow be represented as deterministic routing instead?
  5. What is the risk if the system is wrong?

Higher agency usually means:

  • more capability
  • more flexibility
  • more cost
  • more testing burden
  • more safety controls

That tradeoff is the real point of the framework. Agency is not a badge of sophistication. It is an architectural choice.