Module 3 • 22 min
Architecture Patterns
Match the architecture pattern to the task instead of defaulting to unnecessary complexity.What This Decision Controls
Reactive, tool-augmented, and multi-step planning patterns carry different reliability and operating burdens.
This decision affects the reliability, cost, governance burden, and operating value of the agent long after the first demonstration.
How to Evaluate It
Start with the simplest pattern that meets the business need, then add complexity only when the workflow demands it.
Work from a real workflow and real constraints. A technically possible design is not automatically the right operating design for your organization.
Decision Checklist
- State the business outcome and the bounded task the agent must support.
- Identify the accountable business owner, technical owner, and required human reviewer.
- Confirm the data, integrations, escalation path, and metric required before a build decision.
Worked Decision Scenario
An operations team needs to classify incoming vendor requests and route each one to the right queue. A reactive tool-augmented pattern is sufficient because the decision is bounded and the routing rules are observable.
The team avoids a multi-step planning pattern until the workflow truly requires coordinated research, tool selection, or recovery across several steps. This keeps the first implementation easier to test and govern.
Apply it
Architecture Exercise
Select an architecture pattern.
Saved locally for this review prototype. Your response will become private account data when the approved course backend is connected.