import{c as t,Q as a,j as i,m as s}from"./chunks/framework.BPKcPtvA.js";const u=JSON.parse('{"title":"Module 8: Capstone — Production Multi-Agent System","description":"","frontmatter":{},"headers":[],"relativePath":"modules/m8-capstone.md","filePath":"modules/m8-capstone.md","lastUpdated":1780488246000}'),n={name:"modules/m8-capstone.md"};function r(l,e,o,d,h,p){return a(),i("div",null,[...e[0]||(e[0]=[s(`

Module 8: Capstone — Production Multi-Agent System

Overview

Build, deploy, and evaluate a complete production-grade multi-agent system. Choose from three project options, or propose your own.


Project Options

Option 1: Brand Monitor (Intermediate)

Build a multi-agent system that monitors how LLMs mention a brand across multiple AI services.

Agents:

Requirements:

Option 2: Code Review Pipeline (Intermediate-Advanced)

A plan → build → review → verify chain with CI/CD integration.

Agents:

Requirements:

Option 3: Strategic Decision Board (Advanced)

An 8-agent CEO board with adversarial debate, fact verification, and execution planning.

Agents:

Requirements:


Capstone Phases

Phase 1: System Design (60-90 min)

Deliverable: One-page architecture document including:

Template:

markdown
# System Design: [Project Name]

## Architecture
[ASCII diagram or mermaid]

## Agent Roster
| Agent | Model | Tools | Domain | Memory |
|-------|-------|-------|--------|--------|

## Data Flow
[How agents communicate, what state they share]

## Security
[L-level, hooks, verifier, damage-control rules]

## Cost Estimate
[Per-session estimate with model pricing]

Phase 2: Agent Implementation (2-4 hours)

Build each agent:

Phase 3: Integration (1-2 hours)

Wire agents together:

Phase 4: Security Hardening (1-2 hours)

Apply security layer:

Phase 5: Testing & Evaluation (1-2 hours)

Phase 6: Deployment (1-2 hours)

Phase 7: Review & Iterate (1 hour)


Deliverables Checklist

[ ] Architecture document (one page, with diagram)
[ ] All agent source code with system prompts
[ ] Mental model files for each agent
[ ] Security configuration (damage-control rules)
[ ] Verifier agent (if applicable)
[ ] Golden dataset (10+ test cases)
[ ] Test results (pass@k at k=1, k=3, k=5)
[ ] Cost analysis ($/task, optimization opportunities)
[ ] Security audit (which L-level, what gaps remain)
[ ] Retrospective (max 1 page)

Pass Criteria

CriterionMinimumTarget
System runs without manual intervention
All agents have domain-locked permissions
Each agent has mental model file
pass@k (k=3) on golden dataset>60%>80%
Cost analysis within 2x of optimal
Security audit identifies ≥2 improvements
Observability captures all tool calls
Architecture document submitted

Grading Rubric

AreaWeightPoor (0)Good (1)Excellent (2)
Architecture20%No diagram, unclear designDiagram present, mostly clearClear diagram, justified choices
Implementation25%Agents don't workAgents work on happy pathAgents handle errors gracefully
Security20%L1 onlyL3+ with damage-controlL4+ with verifier
Testing15%No evalpass@k computedpass@k + cost analysis + grind detection
Documentation10%MinimalArchitecture + setupArchitecture + setup + retrospective
Cost Optimization10%Single modelCascade routingCascade + verified savings
`,54)])])}const g=t(n,[["render",r]]);export{u as __pageData,g as default};