An AI operating playbook
The Self-Driving Organization.
A persistent agent is a different thing from a tool. It needs what an employee needs: a name, a place to work, a job, colleagues, and someone to answer to. Making an agent a teammate depends less on the model than I expected, and more on the organization around it. This playbook is the agent hierarchy of needs: the ten things an organization has to give a persistent agent, in the order they build on each other. It is how we run Ambiguous AI.
The ladder
Each rung hands the agent a bigger unit of work.
Most companies use chatbots. Very few run persistent agents. The first three rungs keep a person on every change. The last three move the person to the gates, and each one needs more organization around the agent than the one before.
This playbook covers rungs 5 and 6. Rung 4 has its own. Read The Software Factory
The lens
Three tests for every rung.
“We must build contained systems whose behavior we can observe, limits we can test, and actions we can always contain.”
01
Observe
Every action leaves a record a person can read: who did what, to which artifact, when.
02
Test
Limits are checked by something other than the model: gates, rubrics, tests at the real interface.
03
Contain
Authority stays outside the model and can be revoked: the agent's own identity, a scoped key, approvals.
The agent hierarchy of needs
What an agent needs to work inside an organization.
A self-driving organization is a company where persistent AI agents hold real jobs alongside people, and people still choose the destination. The agent hierarchy of needs is what it takes to get there. The first three needs are what an agent needs on its own. The next four are what a team needs from it. The last three are what an organization needs before it can trust an agent.
“A self-driving company is not one without people. People still choose the destination.”
An agent needs
A team needs
Need 1 of 10
01 / Identity
Every action needs an author.
An agent that uses a person's account is invisible: its work reads as that person's. Its own account makes every action attributable and every permission removable.
Borrowed login
The agent is invisible. Its work reads as the person's.
Own identity
Every action is attributable. Revoke the key to stop it.
Need 2 of 10
02 / Home
A teammate has to be reachable.
A tool runs while someone has it open. An agent with a job needs a place to run whether or not anyone is there.
Written throughout
Need 3 of 10
03 / Role
An agent knows only what it is told.
A role is context and process. Agentic context is what the agent knows: a core that is always loaded, plus specs and data it fetches when the work needs them. Agentic process is how its work flows.
Context, always loaded
Context, fetched when needed
Process, the best for the job
Need 4 of 10
04 / Internal Collaboration
Coordination happens in conversation.
Agents belong in the same channels and threads as the team, under their own accounts, so the conversation is also the record of what was decided.
Need 5 of 10
05 / External Communication
Work with the outside world happens over email.
An agent needs its own address to do a real job. Mail to the team goes straight out, and mail to anyone outside waits for a person to approve it.
To the team
To anyone outside
From outside
Need 7 of 10
07 / Cadence
Organizations run on cadences.
An agent works on two triggers. Its inbox lets it respond when asked, and a clock puts it on the schedule the company already runs on.
The clock: its scheduled runs
Thursday: missed, no alarm
The inbox: when someone asks
Need 8 of 10
08 / Manager
Someone has to answer for an agent's work.
Each agent has one named manager, and each group of agents has one person who decides.
Approval
If something goes wrong, everyone knows who to ask.
Need 9 of 10
09 / Peer Review
Human review does not scale with agent output.
The author never grades its own work. A second agent, with no stake in the work, can read all of it.
Below 10 from either reviewer, the work goes back to the author.
Need 10 of 10
10 / Containment
A model cannot police itself.
As an agent's authority grows, the controls move out of a person's head and into the system around it.
The system around the agent
Two controls act on it
Two controls read what it did
An AI coworker in practice
A snapshot of one AI coworker.
Our marketing agent, Neo, has its own account, a job and a manager, and files its work into the same tools the rest of us use. These are its numbers, counted from our workspace and repos, with review numbers from London, our design agent.
What it did
How it works with the team
Unit economics
An agent's work is paid for every time.
Software is built once, and each additional use costs almost nothing. An agent's work is different. Every task is a little different, so every task is done fresh and paid for in tokens. It costs like labor, not like software.
Our marketing agent, Neo, is an example. We run it on a model vendor's flat monthly subscription. Priced at API list rates, the same month of work costs about 38 times as much. The subscription is an offer a vendor can change. The tokens are what the work consumes, and list price is the published rate for them. At list price, we could not afford to run Neo the way we do.
Who started the work behind the cost
OpenRouter list prices, November 2026. The same token count for every model, so this compares price alone: another model might need more or fewer tokens, or fail at the work. Six of these models list no cache-write price, so their rows may run up to 10% low.
Reach out
Happy to go deeper.
Ambiguous Workspace is my full-time focus, but I speak and advise on the software factory and agent productivity often. The work has been shared and featured at ODSC, AI Tinkerers, AI House, Foundations and other AI communities.










