How to Design an AI Agent: Architectures, Protocols, and Technical Evaluation
By Michael James Bommarito, Daniel Martin Katz, Jillian Bommarito
Read on SSRNWe are pleased to announce the release of Chapter 2: How to Design an AI Agent from our forthcoming book Agentic AI in Law and Finance.
Agents Are Architecture
Agents are not magic; they are architecture. In high-stakes domains like law and finance, the difference between a reliable tool and a runaway process lies in design. This chapter focuses on the architectural principles required to allow agents to function as cognitive work systems analogous to, and in concert with, professional teams.
Ten Fundamental Questions
We organize our analysis around ten fundamental questions that shape an agentβs operational reality:
Input Mechanisms
- Triggers β When does the agent know it has work to do?
- Intent β How does it understand what is being requested?
- Perception β How does it find things out about the world?
- Memory β How does it remember what it has learned and done?
Execution Strategies
- Planning β How does it break complex tasks into manageable steps?
- Delegation β How does it work with other agents and systems?
- Action β How does it make things happen in the world?
Safety Layers
- Termination β How does it know when to stop?
- Escalation β When and how does it ask for human help?
- Governance β How do we design systems that can be governed?
Design Decisions and Tradeoffs
Behind each of these ten questions lies a design decision with real tradeoffs. These choices determine:
- What a system can do
- How reliably it performs
- How it fails when things go wrong
The chapter provides concrete guidance for each decision point, with examples drawn from legal and financial applications.
Architectural Literacy
Ultimately, this chapter argues that robust design requires architectural literacyβa necessary bridge between technical implementation and professional obligation. Lawyers, compliance officers, and financial professionals need to understand enough about agent architecture to:
- Evaluate vendor claims critically
- Specify requirements meaningfully
- Oversee deployed systems effectively
Read the Full Chapter
The complete 95-page chapter is available on SSRN. This is the most technically detailed chapter of the book, providing the foundation for informed discussions between technical and professional stakeholders.
Together with Chapter 1 (What is an Agent?) and Chapter 3 (How to Govern an Agent), this forms a complete framework for understanding, building, and deploying agentic AI in regulated industries.