Before You Build an Agent: The 3-Tier Architecture Spectrum
The most common engineering mistake is wrapping a 20-line deterministic script in an autonomous Agent loop. As Anthropic emphasizes in Building Effective Agents ↗, start with the simplest architecture that works, and only introduce an open-ended loop when execution paths cannot be hardcoded upfront. Primary Source · Anthropic Engineering
Fixed input, single-turn output constrained by Prompt rules, JSON Schema validation, and optional retrieval.
Multi-step chaining, routing, or parallelization where every branch is explicitly controlled by application code.
Open-ended tasks where the model dynamically chooses the next tool based on live environmental feedback.
Anatomy of a 2-Turn Production Agent Run
Suppose an on-call engineer sends one prompt to an internal ops Agent: “Checkout API started returning 500s after today’s v2.14.2 deploy. Find the root cause and prepare a rollback plan.” This is a genuine Level 03 task: the model must inspect live logs first (Turn 1) before proposing a rollback guarded by human approval (Turn 2).
Inspect the payloads across both turns and the LLM’s boundary becomes obvious: it does only one thing—read the current token sequence and decide whether to answer or request a tool call. Fetching logs, enforcing permissions, executing commands, and saving checkpoints are all deterministic application code.
kubectl logs and git diff?