Trust ladders for business agents
Autonomy should be earned per task: observe, suggest, draft, act with approval, act and report. Notes from prototyping an agent control plane.
Companies don't need "an AI agent" — they need specific tasks done with a level of autonomy they're comfortable with. I prototyped a control plane around that idea; these are the concepts that held up.
The ladder
- Observe — the agent watches and summarises; it changes nothing.
- Suggest — it proposes actions in a queue.
- Draft — it prepares the action (an email, a record) for a human to send.
- Act with approval — it executes after a one-click approval.
- Act and report — it executes and reports; humans audit after the fact.
Each task climbs independently, based on measured outcomes — not on how impressive the demo was.
Policy booklets
Every agent gets a plain-language booklet: allowed and prohibited actions, tone, data sources, escalation triggers, an autonomy level and a cost ceiling — versioned like code, readable by a manager.
Cost routing
Most requests don't need the biggest model. Routing rules send simple classification to small models and reserve large ones for drafting and reasoning, with spend limits per agent.
Open questions
- How do you demote an agent gracefully after an incident?
- What is the right unit of audit — a prompt, a decision or an outcome?
Keep reading
How I build with AI agents in the loop
AI writes a lot of my first drafts. Here is the workflow that keeps me — not the model — accountable for what ships.
Oct 2026
The model proposes, code disposes
A guardrail pattern for business agents: let the LLM classify and draft, but put every consequential rule in deterministic, tested code.
Sep 2026