Not Every Workflow Needs an Agent

The pressure to "use an agent" often arrives before anyone has asked where the uncertainty in a process actually sits. This series gives product teams, engineers and architects a practical control gradient. A deterministic workflow handles what can be written down. A bounded agent step, with one question, read-only tools, a budget and a typed output, handles a genuinely uncertain step inside a workflow. Agent-led orchestration is reserved for work where the next step depends on what the last one found. The series shows how to locate the uncertainty, how to specify and test the bounded step, and how to test each pattern on its own terms. It follows the accounts-payable process of Gamtoos Valley Municipality, a fictional Eastern Cape municipality, and draws on a small public-safe lab with synthetic invoices and a simulated model. Research claims were checked on 5 November 2026.

1 article