Before any design or any cloud: what kinds of AI application exist, what an agent really does on each turn of its loop,
what goes wrong when nothing holds it, and what an agent harness is. Nine stops, one simple picture each, two simulations you can play.
No vendor names on this road. Everything here is the idea; the products come later.
The roadmap
The whole road on one picture. Click any stop to open it.
Lavender boxes are model calls. Blue boxes are your own code. The kind depends on one thing: who decides the next step.
Every AI application is one of three kinds, and the difference is a single question: who decides the next step?
Nobody (there is only one step), your code, or the model. The more the model decides, the more can go wrong, so choose the simplest kind that does the job.
Autonomy is a dial with five positions, not a switch. Most business value today sits at levels 2 and 3.
An autonomous agent is an agent with less of a person watching it. Businesses want that because work stops waiting for office hours,
queues stop growing in a spike, and people spend their time on the cases that need judgement.
The agent loop. It ends in one of two ways: the model answers, or our code says "enough".
Step through one request a move at a time: the exact request our code sends, the exact reply the model returns, the tool our code runs,
and the result going back in. Then watch it stop for one of two reasons: the goal is reached, or the limit is.
The real run on Azure, 14 October 2026: three model calls, $0.00087, nothing paid.
Six short stories with the guardrails switched off, among them a document with hidden orders, a stranger who simply asks for someone else's data,
a refund nobody approved and a loop that runs all night. Each ends with what it cost the business. Then switch the guardrails on and play it again. Six real incidents follow.
The model is the horse. Everything else in the picture is the harness, and its one job is to keep the horse on the green path.
The model is a strong horse that does not know the road. The harness is everything that keeps it on the green path:
reins, blinkers, a driver and a cart. This is the picture the rest of the course hangs on.
Seven groups. The top row is what an agent does. The bottom row is how well and how safely it does it.
Before the big picture, every requirement by itself: a front door, knowing who is asking, running the loop, calling the model, tools, four kinds of guardrails,
logs and traces, cost, evals, safe release, secrets and more. Thirty-three requirements, one small picture each, the way an architect would walk an engineer through them.
The architecture in five bands and two rails. Only the row of agents changes from one business to the next.
Five bands and two rails. Then one band, the shared parts, opened up into five families of concerns: Think, Act, Control, See and Change.
By now every box in it is a requirement you have already met.
One claim, end to end. Every box here is a place where the earlier stops show up again.
Everything above, in one working agent: a claims assistant that takes the first report of a car accident.
Follow one message from start to finish, then send your own in the simulator.