
Design production-ready AI agent systems that survive real enterprise, not toy demos. Own autonomy, state, topology, and human oversight as architectural decisions framed by Meridian Atlas.
See how an agent uses the perceive, reason, act, observe loop to read context, call tools, and use results. Atlas' demo explains tool execution and agent trace debugging.
Explore the ReAct interleaved reasoning and acting loop, its thought-action-observation cycle, strengths in adaptivity and traceability, and its limits without a plan or a reviewable artifact.
Define a tool layer as the trust and integration boundary, using four-layer contracts—typed schema, semantics with idempotency and side effects, model-friendly errors, and narrow verbs for safe, bounded calls.
Wrap legacy systems with a five-stage pipeline: agent to facade to adapters to systems, as an anti-corruption layer that normalizes results and defines retryable versus permanent errors.
Atlas preserves continuity with a memory architecture of compaction, selective retrieval, threat identity, and deliberate forgetting. It uses checkpointer and Chroma to keep threads resumable without repeating the customer.
Demonstrates how to equip an agent with real short-term and long-term memory, preserving state across sessions by checkpointing to disk and memory store, enabling continuity.
Teams accumulate tools and prompts sprint by sprint, creating a twelve-tool monolith that degrades reliability and debugging becomes hard, underscoring the need for deliberate decomposition and an orchestrator-worker pattern.
Implement ci-cd for agents by wiring evals and traces into four gates—pre-merge, pre-deploy, canary, and feedback loops—to catch regressions before shipping.
Explore four governance touchpoints—least privileged tools, data protection, EU AI Act obligations, and change governance—integrated into Atlas architecture to ensure secure, compliant agent systems.
Explore how architecture decision records preserve Atlas' design choices by documenting loop patterns, integration layers, state ownership, topology, and autonomy with evidence, review, and a living index.
This course contains the use of artificial intelligence.
AI agents are moving into production, and someone has to architect them. This course is for that person. Instead of teaching one framework's API, it teaches the architecture decisions that determine whether an agent system survives contact with the enterprise: when to use a workflow instead of an agent, which loop pattern fits which task, where the tool boundary sits, what state to persist and who owns it, when one agent should become many — and when it absolutely should not — where humans must stay in the loop, and how agents are tested, traced, and versioned like real software.
You learn by building. Across 8 hands-on labs (LangGraph + Ollama, all local, no API keys), you design and evolve Atlas, the agentic claims platform of Meridian Insurance Group — a realistic enterprise with legacy systems, compliance obligations, and impatient stakeholders. You implement ReAct and plan-and-execute side by side and measure the difference, expose enterprise systems through typed tools and MCP, give your agent durable memory across sessions, refactor a monolithic super-agent into an orchestrator/worker crew, add interrupt-based human approval gates, and build the eval suite and tracing that catch a regression before it ships. The capstone assembles everything into a production-shaped system defended before an architecture review board — with a reference architecture document and ADR set you can reuse at work.
By the end you'll have a decision framework for every major agentic design choice, a working reference implementation, and the vocabulary to review any agent design with confidence.