The 6 AI Architecture Primitives
Most teams begin agentic AI design with a model, prompt, and orchestration framework. That can create impressive demos—but not necessarily systems that are safe, reliable, cost-controlled, or ready to act in the real world.
This session introduces six architecture primitives that every production AI agent needs:
Reasoning — turning an objective into bounded plans and decisions
Memory — retaining the right context without carrying unsafe or stale state
Tools — taking action through APIs, workflows, and enterprise systems
Evidence — grounding outputs in current, authorized, traceable facts
Policy — defining authority, permissions, constraints, and approval rules
Control — observing behavior, enforcing budgets, degrading safely, and stopping unsafe autonomy
Participants will see how these primitives work together as an AI agent moves from “answering a question” to making a real-world recommendation or action.
An agent that has memory but no policy can retain information it should not use. An agent with tools but no authority control can take actions beyond its business mandate. An agent with strong reasoning but weak evidence can produce a convincing wrong answer. An agent with all of these capabilities but no control layer can retry itself into cost spikes, duplicate side effects, or unsafe decisions.
The key challenge is not simply building more capable agents. It is governing autonomy: deciding what the AI may know, use, recommend, commit, defer, and stop doing when conditions become uncertain.
Session details:
Using an AI-commerce agent as a live architecture case, the session traces a request from customer question to possible business action. The agent must retrieve customer and policy context, evaluate evidence, call inventory and payment tools, and decide whether to answer, recommend, issue a refund, or escalate.
Then the system is pressure-tested through Authority and Degradation simulations:
- The agent retrieves a stale return policy but a current exception exists elsewhere.
- Inventory is delayed, but the agent wants to promise two-day delivery.
A payment tool times out after a possible charge. - The model has enough information to recommend an action—but lacks authority to commit it.
- Tool calls and retries exceed the agreed churn budget.
- A required source becomes unavailable or an entitlement check fails.
- The system is operationally healthy, but its evidence is no longer trustworthy.
For each scenario, participants determine:
- Which architecture primitive has failed or become insufficient?
- What is the agent still allowed to say or do?
- Which policy and evidence checks are required?
- Should the system remain normal, become conservative, defer, freeze a capability, or escalate to human review?
- What receipt must be recorded so the decision can later be replayed and defended?
Value for participants:
- A clear mental model for designing production-grade agentic AI beyond prompts and model selection.
- A way to separate AI reasoning from business authority and policy enforcement.
- Practical patterns for memory boundaries, tool permissions, evidence qualification, and safe retrieval.
- A method to prevent uncontrolled retries, tool loops, excessive cost, and duplicate actions.
- A degradation strategy that reduces autonomy safely without shutting down the full customer experience.
- Reusable questions to pressure-test an existing AI agent design.
Attendees will leave with:
- The Six AI Architecture Primitives reference model
- An Authority Boundary Map for agent capabilities
- An Evidence and Policy Admission Checklist
- A Tool and Churn Budget template
- An Authority and Degradation Scenario exercise
- A Stop Authority Ladder: Normal → Conservative → Defer → Freeze → Human Review
About Rohit Bhardwaj
Rohit Bhardwaj is Director of AI & Data Architecture at Salesforce, an O’Reilly instructor, and founder of AI Architect Circle. With 30 years of experience in software and enterprise architecture, he helps engineers, architects, and technology leaders make architecture decisions they can explain and defend.
His work brings together enterprise AI, agentic systems, data architecture, and distributed systems. He focuses on the decisions that determine whether a system remains reliable, secure, accountable, and economically sustainable when it encounters real-world demands.
Rohit’s talks and workshops explore practical questions: What happens when an AI agent acts on conflicting information? Can a failed payment be retried safely? Who can stop an autonomous action, and what evidence explains the decision afterward? His teaching connects these questions to architecture, customer trust, and business outcomes.
He is the author of System Design with AI Interview Guide: Designing Scalable, Agentic, and Defensible Systems, published by Apress. He also developed ARCHVIEW™, ROCS Loops™, and LLM-SHIELD™ to help teams structure architectural thinking and address the challenges of building trustworthy AI systems.
Through AI Architect Circle, Rohit extends this learning through live discussions, book walkthroughs, videos, and interactive architecture challenges. These challenges explore incidents such as payment timeouts and conflicting bookings, helping participants practice the judgment behind their design decisions.
Continue learning with Rohit
Join Rohit live on Saturdays at 9:00 a.m. Eastern
System Design with AI — Live with the Author is a free live podcast and Q&A series featuring practical system-design scenarios, AI architecture discussions, and questions from the community.
See the next session and register
Try an interactive architecture challenge
Put your design decisions under pressure and explore the consequences.
Explore the challenges
Explore AI Architect Circle
Find architecture lessons, videos, resources, and ways to continue learning.
Visit AIArchitectCircle.com
Read the book: Amazon · O’Reilly
Watch and connect: YouTube · Instagram: @aiarchitectcircle · LinkedIn · X / Twitter: @rbhardwaj1
More About Rohit »