Guide
Mobile revision aid — the whole M00 orientation on one thumb-scrollable deck. The arc from rule-based AI to production agents, the 7 building blocks, the lifecycle, the litmus test, and flash cards to check yourself before Module 1.
The 11 sections
Tap any section to jump to its reference card.
- 1The 7 Eras of AIRule-based → agentic, each era stacks
- 2Why Agents Are Possible NOWFive capabilities converged
- 3Three ApproachesScript → FastAPI → Agent
- 4What IS / ISN'T an AgentWho decides next: your code or Claude?
- 5The 7 Building BlocksBrain, Tools, Memory, Plan...
- 6The Agent LifecycleDesign → Build → Protect → Observe → Deploy
- 7How Agents Actually WorkThe universal while-loop
- 8Common MisconceptionsMyth vs truth
- 9Market StatsNumbers to keep in your pocket
- 10Flash CardsTap-to-reveal self-check
- 11Course Track Map7 tracks, 30 modules
The 7 Eras of AI
Each era added a capability without erasing the previous ones. Today's agents still use rules, ML, transformers, and RAG — all at once. You add a reasoning layer on top; you don't replace what works.
| Era | Added capability |
|---|---|
| 1 · Rule-Based 1948–2000s | Follow human-written rules. Brittle — every edge case needs a new rule. |
| 2 · Machine Learning 2000s–15 | Learn patterns from data. One model = one task; can't reason or explain. |
| 3 · Transformers 2017–20 | Understand context; process unstructured text. |
| 4 · Generative 2020–23 | Create content. But reactive — can't call APIs or search. |
| 5 · LLMs Mature 2023–24 | RAG solves hallucination; tiered models solve cost. Still respond, don't act. |
| 6 · Agentic ★ 2024–now | Take actions. LLM + tools + loop + memory = reasons AND acts. |
| 7 · The Frontier 2026+ | Coordinate. Multi-agent systems via MCP + A2A protocols. |
MCP = agent↔tool (Anthropic, 2024). A2A = agent↔agent (Google → Linux Foundation, 2025).
Why Agents Are Possible NOW
The headline isn't a smarter model — it's the scaffolding around it. Five capabilities went from impossible to production-ready between 2022 and 2026.
| Capability | 2022 | 2026 |
|---|---|---|
| Tool Use API | none | native |
| Structured Output | flaky JSON | schema-guaranteed |
| Context Window | 4–8K | 200K–1M+ |
| Inference Speed | 10–30s | 1–3s / turn |
| Cost / Token | $0.06/1K | $0.00025/1K |
"Five years ago you could build a chatbot. Today you can build an agent. The difference isn't a smarter model — it's the tools, context, speed, and cost around it." Cost alone dropped 240× since GPT-3.
Three Approaches
Same question — "Is Acme Corp likely to go delinquent?" — three ways to answer. The ML model never disappears; the agent just uses it.
| Input | Output | |
|---|---|---|
| 1 · Script 15 lines · ~$0 | 6 numbers, by hand | 0.823, no context |
| 2 · FastAPI 35 lines · ~$0 | {"name":"Acme"} | score; misses DBA names |
| 3 · Agent ★ 70 lines · ~$0.05 | Plain English | Narrative report, 7 filings, cites evidence |
In Approach 1 the model is the product. In Approach 3 the model is one tool the agent calls when it needs a probability — surrounded by reasoning, search, and narrative.
Every ML model your team shipped can become an agent tool tomorrow.
What IS / ISN'T an Agent
One question: who decides what happens next — your code, or Claude?
| Level | Loop? | Who decides |
|---|---|---|
| 1 · LLM Call 1 call, no tools | no | YOU |
| 2 · Workflow fixed sequence | no | YOU + Claude |
| 3 · True Agent ★ dynamic tools | yes | CLAUDE every turn |
The litmus test: replace the LLM with hardcoded responses. If the program still works the same — NOT an agent. If it breaks because Claude was deciding at runtime — it IS one.
Level 3 needs all three: Tools (act on the world) + Loop (act again) + Decisions (choose from findings).
The 7 Building Blocks
Like parts of a body — drop any one and your agent stops being trustworthy. Most tutorials teach only blocks 1–2.
| Block | Job | Track |
|---|---|---|
| 1 Brain | LLM reasons & decides | M01–04 |
| 2 Tools | Call APIs, DBs, files | M05–07 |
| 3 Memory | History + RAG retrieval | M08–11 |
| 4 Plan | Decompose, order, retry | M12–15 |
| 5 Guardrails | Validate I/O, escalate | M16–18 |
| 6 Eyes | Log, trace, monitor | M19–20 |
| 7 Home | Deploy, scale, cost | M21–22 |
Brain + Tools = 2 of 7. An agent that works on your laptop but can't be trusted in production is a prototype, not a product.
The Agent Lifecycle
Building an agent isn't "write code and ship." Five stages, each adding a critical layer.
- DesignScope, tools, data access. (Tracks 1–2)
- BuildDefine tools, engineer prompts, wire the loop, add RAG. (Tracks 2–4)
- ProtectValidate I/O, cap loops, add human-in-the-loop. (Track 5)
- ObserveTrace every tool call, log decisions, score outputs. (Track 6)
- DeployFastAPI/Docker, Cloud Run/Lambda, cost + rate limits. (Track 7)
⚠ "I'll add guardrails later" costs 4× more. Build safety in from the start — even a simple max_turns=10 counts.
How Agents Actually Work
An agent is your code calling Claude's API in a loop. No magic runtime — you are always in control.
# THE UNIVERSAL AGENT PATTERN user_asks_a_question() while claude_wants_a_tool: reply = send_to_claude(question + history) if reply.stop_reason == "tool_use": result = run_tool(reply.name, reply.args) history.append(result) # one iteration else: return reply.text # final answer
The while loop is the entire agent. Claude replies with a tool_use block (run this) or end_turn (final answer).
Every call is stateless — you resend the full history each time. Between calls, nothing "thinks." Same loop runs on a laptop, behind FastAPI, or in a cron job.
Common Misconceptions
Market Stats to Memorize
When a peer asks "is agentic AI real or hype?" — keep these in your back pocket.
Quick-Reference Flash Cards
Tap to reveal the answer. If you can answer all six, you're ready for Module 1.
tool_use, run the tool and loop back → if end_turn, return the answer.Course Track Map
7 tracks, 30 modules — building block by building block.
| Track | Block | Modules |
|---|---|---|
| 1 | Brain — how LLMs think | M01–04 |
| 2 | Tools — the hands | M05–07 |
| 3 | Memory — RAG | M08–11 |
| 4 | Plan — ReAct | M12–15 |
| 5 | Guardrails | M16–18 |
| 6 | Observability | M19–20 |
| 7 | Deploy | M21–22 |
"In five years most APIs will still be FastAPI and most ML models still pickle/ONNX. The change is Layer 3 — the reasoning that decides how to use them. That's what this course teaches."
Open the full study guide on desktop
The desktop version is the complete, print-ready study guide — the full era timeline, all comparison tables, the 12 flash cards, and the course roadmap laid out for review or printing.
Open the full study guide on desktop → Print-ready reference · 11 sections + roadmapM00 Study Guide · Building AI Agents with Claude