A reference architecture for enterprise agentic AI, in seven layers
Most agent projects fail at the seams between layers, not inside the model. Here is the stack we draw on the whiteboard before writing any code.
Enterprise agentic AI, built to survive production.
Most agent projects fail at the seams between layers, not inside the model. Here is the stack we draw on the whiteboard before writing any code.
A model can propose actions. Something else has to decide whether they happen. That something is the control plane.
Giving an agent a tool is giving it a credential. Treat it with the same rigor as a service account.
An agent task that takes forty minutes will meet a deploy, a timeout, and a rate limit. Plan for all three.
More agents is not more intelligence. Choose the smallest topology that keeps responsibilities legible.
If you cannot say what good looks like in a test, you cannot ship the agent, or safely change it.
The moment an agent remembers something, you have created a new datastore with retention, access, and privacy obligations.
Finance does not care about your token price. They care that a runaway loop cost what a mid-sized project does.
Approval screens that nobody can evaluate are theatre. Design review as a first-class part of the system.
An HTTP trace tells you a model call took two seconds. It does not tell you why the agent refunded the wrong customer.