Month 3 — Agentic AI + DSA Begins (Wk 9–12)
Weeks 9–12 · Days 57–84
🎯 Theme: Agentic AI — Build agents that plan, reason, and take actions autonomously
Active Tracks: AI (Agents) · Communication · System Design · DSA (STARTS!)
🎯 Month 3 Goals
- Build a working ReAct agent
- Build a multi-agent pipeline
- Build and deploy a custom MCP server
- Solve 30 DSA problems (arrays → graphs)
- Polish 5 STAR behavioral stories
📋 Month 3 Milestone
✅ ReAct agent built + MCP server live + multi-agent pipeline built + 30 DSA problems + 5 STAR stories
🧠 Week 9 — The ReAct Loop: Your First Agent
One line: ReAct = Reason + Act. The agent thinks about what tool to use, uses it, observes the result, thinks again — looping until the problem is solved.
🎯 Analogy: ReAct agent = a detective. Sherlock does not just answer immediately. He reasons ("I need to check the lab"), acts (goes to lab), observes ("fingerprints found"), reasons again ("check the suspect database"), acts again — until he solves the case.
🔑 The ReAct Loop (Visual)
User: "What is the capital of France and what is 25°C in Fahrenheit?"
[THOUGHT] I need two tools: one for facts, one for unit conversion.
[ACTION] search("capital of France")
[OBSERVATION] "Paris is the capital of France"
[THOUGHT] Now I need temperature conversion.
[ACTION] convert_temp(25, "C", "F")
[OBSERVATION] "77°F"
[ANSWER] "The capital is Paris. 25°C = 77°F."
🔑 Key Terms
| Term | Meaning |
|---|---|
| Thought | LLM reasons about what to do next |
| Action | LLM calls a tool |
| Observation | Result your code returns after running the tool |
| Trajectory | The full sequence of thought → action → observation steps |
| Stopping Condition | When the agent decides it has the final answer |
🏗️ Build: ReAct agent with 4 tools (search, calculator, weather, time zone). Give it multi-step questions: "Is it warmer in Chennai or Paris right now? By how many degrees?"
🧠 Week 10 — Multi-Agent Systems
One line: Instead of one LLM doing everything, you split work across multiple specialized agents — each an expert in one domain — that pass work to each other.
🎯 Analogy: A hospital. One doctor does not do everything. The GP refers to a specialist → specialist runs tests → lab sends results → GP gives diagnosis. Multi-agent = a medical team working together, not a solo doctor doing everything.
🔑 Common Multi-Agent Patterns
| Pattern | How it works | When to use |
|---|---|---|
| Orchestrator + Workers | One agent breaks the task and assigns to workers | Complex tasks with clear sub-tasks |
| Pipeline | Agent A → Agent B → Agent C in sequence | Data processing workflows |
| Debate | Two agents argue a point, third judge decides | Fact-checking, decisions |
| Parallel Specialists | Each agent works on one domain simultaneously | Research + writing + QA at same time |
🔑 Key Terms
| Term | Meaning |
|---|---|
| Orchestrator | The manager agent — plans, delegates, collects results |
| Worker Agent | Specialist agent with one specific job |
| Handoff | Passing task context from one agent to the next |
| Shared Memory | A common store all agents can read from and write to |
🔑 Agent Handoff Flow (Visual)
[Orchestrator] receives: "Write an article on RAG"
│
├──► [Research Agent] searches web ──► findings
│ │
├──► findings ──► [Writer Agent] ──► draft article
│ │
└──► draft ──► [QA Agent] ──► verified output ──► FILE SAVED
🏗️ Build: Research pipeline — Orchestrator receives a topic → Research Agent searches the web → Writer Agent drafts an article → QA Agent checks facts → final output saved to a file.
🧠 Week 11 — MCP: Model Context Protocol
One line: MCP is a standard protocol for connecting LLMs to external data sources and tools — like USB-C, but for AI apps. Any LLM, any data source, one standard.
🎯 Analogy: Before USB-C, every device needed a different charger — a mess. MCP = USB-C for AI. Any LLM (Claude, GPT, Gemini) connects to any data source (your database, Google Drive, GitHub, Slack) using the same standard interface.
🔑 MCP Architecture
[Claude / LLM] ←→ [MCP Client] ←→ [MCP Server] ←→ [Your Data / Tool]
🔑 Key Concepts
| Term | Meaning | Example |
|---|---|---|
| MCP Server | Exposes your data and tools via a standard interface | A Python server wrapping your database |
| MCP Client | The LLM-side connector (built into Claude Desktop) | Claude Desktop reads your MCP server |
| Resource | Read-only data the LLM can access | Your files, database rows, API responses |
| Tool | A function the LLM can call | run_sql_query(), list_files() |
| Prompt | Pre-built prompt templates the LLM can use | /summarize_document command |
💻 Minimal MCP Server (5 lines)
from mcp.server.fastmcp import FastMCP
mcp = FastMCP("MyServer")
@mcp.tool()
def get_user_data(user_id: str) -> dict:
"""Fetch user info from the database"""
return {"id": user_id, "name": "Arumugam", "plan": "Pro"}
if __name__ == "__main__":
mcp.run()
🏗️ Build: MCP server that exposes 3 tools from your own data (read local files, query a SQLite DB, get system info). Connect it to Claude Desktop and test it.
🧠 Week 12 — Advanced RAG & Vector Search
One line: Basic RAG does a simple vector search. Advanced RAG adds smarter chunking, hybrid search, re-ranking, and query rewriting to get dramatically more accurate answers.
🎯 Analogy: Basic RAG = Google in 2000 (keyword match only). Advanced RAG = Google in 2024 (semantic understanding, page rank, spell correction, personalization, result re-ranking). Same idea, massively better results.
🔑 Advanced RAG Techniques
| Technique | Problem It Solves | How |
|---|---|---|
| Hybrid Search | Pure vector search misses exact keywords | Combine keyword search (BM25) + vector search |
| Re-ranking | Top 3 results may not be the most relevant | Use a cross-encoder to re-score retrieved chunks |
| Query Rewriting | User's question is vague or ambiguous | LLM rewrites the query before searching |
| Parent-Child Chunks | Small chunks retrieved, but need more context | Retrieve small chunk, inject its full parent paragraph |
| HyDE | No good match exists for the query | Generate a hypothetical answer, search with that instead |
🔑 Hybrid Search (Visual)
Query: "What does the CEO earn?"
BM25 (keyword): finds "CEO", "earn", "salary" — exact word match
Vector Search: finds "executive compensation" — semantic match
Hybrid result: BOTH types merged → much better recall
🏗️ Build: Upgrade your Week 3 PDF bot with hybrid search + re-ranking. Test accuracy on 20 questions before vs after — you should see a clear improvement.
📅 Week Pages — Detailed Daily Checklists
- Week 9 — The ReAct Loop: Your First Agent
- Week 10 — Multi-Agent Systems
- Week 11 — MCP: Model Context Protocol
- Week 12 — Advanced RAG & Vector Search