Workflow vs agent
Who decides the next step: your code or the model.
Module 08 · Agents
An agent is a loop with model-selected decisions.
What you’ll learn
Who decides the next step: your code or the model.
Observe, decide, act, update state. Repeat until done or stopped.
Why a chain of mostly good steps can still fail as a whole.
Where a human approves, and when a plain workflow is the better choice.
Applied exercise
Redesign four use cases as workflows, partially agentic systems and autonomous agents, then compare risk.
Cheat sheet
One page you keep: the questions to ask on every project, the rules of thumb, and a decision guide you can use on your own product. All ten come with The Book.
Leave at the door
| Myth | What’s actually true |
|---|---|
| “More agentic is always better.” | More autonomy adds variance, cost and risk too. |
| “The agent takes the action.” | The model requests it. Your system executes it. |
| “It made a plan, so it stays on track.” | A plan is text. Only checks keep it on track. |
| “More agents give better answers.” | Each hand-off adds cost and a chance to fail. |
| “A human in the loop makes it safe.” | Only if they see the evidence and can say no. |
Before you move on
A research agent misreads a figure at step 2. The report builds on it.
Why did the error spread? Name two design changes that would have caught it earlier.
How we would answer
Every module ends on a question like this. Join the waitlist →

The Autonomy Engineer
builds and breaks agent workflows to discover when independent AI becomes useful and when it becomes chaos.
Episode 08 · Agents without the mythology
Included with the course.
Coming soon · an AI character from the show, not a real researcher.