Built AI-first · Chapter 8 of 9

The Autonomy Spectrum

"Should the AI do it automatically?" is the wrong shape of question, because it asks about an agent when the answer differs per act. The same role can reasonably be trusted to move a calendar entry unattended and not trusted to send a one-line email to a client.

Five rungs, granted one act at a time. Where to start, what earns a promotion, and why the order is structural rather than cautious.

The five rungs Book 15 minutes

The spectrum

Five rungs, and most of the value is on the second

Read the rungs as grants of authority over a specific act — "draft and send the weekly status note", not "the delivery agent".

Suggest The agent proposes and a person does the work. Output is advice: a recommendation, an analysis, a list of what looks wrong. Nothing it produces leaves the organisation. This rung is undervalued — a great deal of the benefit of the whole exercise is simply having something that notices. To start here: nothing. This is the floor, and a new act starts here by default.
Draft The agent produces the finished artefact — the email fully addressed, the invoice complete, the report assembled — and a person presses send. Nearly every agent we run lives here permanently, by design rather than by caution. The work is done; the irreversible half-second is a human's. To get here: the act produces an artefact a person can check in under a minute, and the check is genuinely happening rather than theatre.
Act with approval The agent stages the irreversible act and it waits in a queue for release. The distinction from the rung below is real: at draft, the human still does the last step; here the act is fully prepared and the human decision is a yes or a no. Faster, and it concentrates the human's attention on the decision rather than the mechanics. To get here: a queue that is actually reviewed, a clear record of what will happen on release, and a cheap way to reject.
Act and report, inside an envelope The agent acts without asking, but only within written limits — amount, recipient, category, time window, volume — and reports every action afterwards. Anything outside the envelope automatically falls back to the rung below rather than being attempted. To get here: a written envelope, an automatic fallback when it is exceeded, and a track record for this exact act that you can point at.
Unattended, with exception escalation Runs on its cadence with nobody in the loop, escalating only what its rules define as exceptional. Appropriate for acts that are reversible, bounded and boring — and for very few others. Our unattended work is monitoring, assembly and scheduling, never anything that spends, sends externally, or commits the organisation. To get here: reversibility, a measured record, and an answer to "what does a bad night look like" that you would repeat to a board.

The rules

Four rules that decide the rung

Rule one

Per act, never per agent

An agent is not "trusted". A specific act by a specific agent, with a specific scope, is at a specific rung. Ours sit at different rungs for different work, and the grant is written down beside the routine rather than held as a general impression of how well it has been doing.

Rule two

The currency is reversibility times record

Two questions, both required. How expensive is the undo — minutes, an apology, a client, a licence? And how long is the verified record for this exact act? A long record on a similar act does not transfer, which is the mistake that produces the confident surprise.

Rule three

Promotion needs evidence that already exists

You cannot audit trust you never measured. If nothing logged the outcomes at the lower rung, there is no case for the higher one — which is why the verdict log from chapter five is a precondition for this chapter rather than a nicety.

Rule four

Demotion is automatic, not a discussion

An envelope breach, a failed check twice running, or a changed input drops the act a rung by rule. If demotion requires somebody to convene a meeting, it will not happen at the moment it is most needed.

Autonomy is not a reward for good behaviour. It is a bet on reversibility, priced with a record.

The sequence

Why you cannot start at the top and work back

The argument against skipping rungs is usually made on safety grounds. The stronger argument is political, and it is the one that actually decides whether an AI programme survives its first year.

An organisation gives a new capability roughly one serious mistake. Make it at rung one, and it is a bad draft that somebody caught — the system worked. Make the same mistake at rung four and it is an invoice sent to the wrong client, a records response released early, a message that went out under the organisation's name. The cost is not the error; it is that every subsequent proposal now arrives into a room that has seen this go wrong.

The sequence also produces the evidence the later rungs need. Six months at draft is not six months of delay — it is six months of exactly the record required to make the case for acting unattended, assuming you logged it.

Our own permanent floor. Four acts never rise above approval, regardless of record: sending on the organisation's behalf, spending or moving money, setting a price, and signing anything. Those are enforced in the system rather than promised in a policy — which is the distinction between a boundary and an intention.

In your world

Where to start, and what never moves

Fire & EMS agencies

Start at suggest. Disclosure never leaves approval.

Assembly and noticing are good early rungs — the certification about to expire, the grant window opening, the export that did not arrive. Anything that becomes a public record or leaves the agency stays at approval permanently.

Small cities & civic

Start at draft. Release stays human.

Packet assembly and first-pass drafting are genuine relief. Release of anything disclosable is a decision with legal consequence and an owner with a name, and no record length changes that.

Trades & field service

Draft the quote, never price it.

Quote assembly, follow-up drafting and job-cost noticing move up quickly because they are cheap to reverse. The number itself is the business and it stays with the owner.

Professional services

Draft everything client-facing, indefinitely.

The value is in the artefact being ready, not in it being sent automatically. Internal assembly and monitoring can climb; anything a client reads keeps a person on the last step.

What we will not claim

The boundary on this chapter

We do not sell "fully autonomous". We run unattended work only where it is reversible and boring, and we would be suspicious of anyone describing an autonomous back office without naming what it is not allowed to do.
No reliability figure. We have not measured ours to a standard worth publishing. What we can show is the machinery — the checks, the queue, the log — and let you judge it directly.
A higher rung is not a better system. Most organisations should have very few acts above approval for a long time, and that is a mature posture rather than a timid one.
None of this applies to an emergency response path. No rung, no envelope, no record. Dispatch, CAD, station alerting and patient care are outside the work entirely.

Where this sits

Next: the whole thing, on a calendar

Eight chapters of structure become useful when they are put in an order with dates and gates. That is the last one, and it is the one to read if you only read two.

ITMedic · Green IT Consulting, LLC · Snoqualmie, WA · (425) 242-3378
Built AI-first, chapter 8 of 9 — written from our own build. The agents draft; a human sends.