Understanding the Spectrum of Agency in AI Systems
Understanding the Spectrum of Agency in AI Systems
Section titled โ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.
The Five Levels
Section titled โThe Five Levelsโ| Level | Name | What the system can do | Typical examples |
|---|---|---|---|
| 0 | No agency | Return fixed or tightly scripted outputs | FAQ bots, static classifiers behind a simple UI |
| 1 | Routed workflows | Choose between predefined branches | workflow bots, intake triage, template routing |
| 2 | Tool-using assistant | Call external tools in bounded ways | internal copilots, retrieval assistants, support agents |
| 3 | Autonomous agent | Plan and execute multi-step tasks | research agents, coding agents, automation agents |
| 4 | Multi-agent system | Coordinate several specialized agents | planner-worker systems, reviewer-executor systems |
Level 0: No Agency
Section titled โLevel 0: No Agencyโ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
Level 1: Routed Workflows
Section titled โLevel 1: Routed Workflowsโ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
Level 2: Tool-Using Assistant
Section titled โLevel 2: Tool-Using Assistantโ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.
Level 3: Autonomous Agent
Section titled โLevel 3: 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.
Level 4: Multi-Agent System
Section titled โLevel 4: Multi-Agent Systemโ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.
How To Choose the Right Level
Section titled โHow To Choose the Right LevelโChoose the lowest level of agency that can still solve the problem.
Questions to ask:
- Does the system need tools, or is generation enough?
- Does it need to recover from failures on its own?
- Does it need to act, or only recommend?
- Can the workflow be represented as deterministic routing instead?
- What is the risk if the system is wrong?
Design Implications
Section titled โDesign Implicationsโ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.
Next Steps
Section titled โNext Stepsโ- Read AI Agents for the core system building blocks.
- Read Agentic AI for planning and orchestration patterns.
- Use API Access and Keys if your system will interact with external services.