Agentic Architecture

Convictions for designing agent-based systems
1 Agent vs Tool — The foundational distinction
A AGENT Non-deterministic Works and decides autonomously based on an intention depending on a context vs T TOOL Deterministic Programmatic usage API or MCP Deterministic same call = same result The tool is deterministic. The agent is not: its result is statistical and depends on the execution context.
2 Platform foundations — MVP = the platform · POC = an agentic application that validates concepts
AGENTIC APPLICATION Orchestrator coordinates decide and act Ag. A Ag. B Ag. C tools tools tools reads writes READ Understand · Resources · Context WRITE Act · Actions · Modifications functional decoupling DIGITAL PLATFORM Existing IS · APIs · Data · Business services First, frame the platform. Expose read and write. Then, agents decide.
3 Decoupling & Business domains — Bring each agent closer to its business context
Monolithic application Orch. Agent Monolith Inside the monolith with the orchestrator Coupled · Synchronous decoupling Orch. API Agent the agent is useful Exposed agent Coupled call via API the agent is useful Takes business context into account empowerment Dom. B Agent Dom. A Orch. Dom. C Dom. D A2A MCP ownership in this domain Agent-product Designed as a product ownership in another domain Strategy · Product management
4 Agentic Mesh — 4 pillars for a value-driven mesh
BUSINESS PROCESS H A H A A A H H A H A DOMAIN A 1 2 decides within the scope of the domain DOMAIN B 3 4 decides within the scope of the domain DOMAIN C 5 6 decides within the scope of the domain GOVERNANCE · Enablement: frame and facilitate agent usage by agents · Ownership per domain DIGITAL PLATFORM Existing IS · APIs · Data · Business services · Read & Write Agents are the communication points between domains. Value emerges from the mesh.