teaching · a curriculum
Works in dev. Breaks in prod.
Three tracks on agent systems
Your agent works in dev. In prod it forgets, retries forever, and disagrees with itself. These are the three tracks on building, distributing, and operating agent systems, written for engineers shipping this stuff at work.
Track 01 is the foundations: transformers, RAG, tools, sandboxes, the production loop. Track 02 is what most agent material skips. Multi-agent systems are distributed systems, and there are fifty years of theory that explain exactly how they break. Track 03 is the operating-system layer underneath: scheduling, isolation, resource control for fleets of agents.
3 tracks · 17 modules · 10 lessons published · free · MIT-licensed · no signup
the three tracks
Build, distribute, operate.
The same problem from three angles. You can read in order or skip straight to whichever one matches what you’re fighting today.
Track 01LiveStart here
Build AI Agents
From transformer foundations to production agent operations.
- ·Transformer foundations and the API loop
- ·RAG: vectors, retrieval, evals, production
- ·Agentic workflows: tools, MCP, A2A, the agent SDK
- ·+ five more on agents, skills, coding, and ops
Track 02In progressNew
Agentic Distributed Systems
Your agent already is a distributed system. Here is the theory that explains why it breaks.
- ·The agent as a node: tool calls as RPC, identity, capability
- ·Time, order, and causality in async agent flows
- ·State and consensus across agents that disagree
- ·Sharding, fanout, and Byzantine sub-agents
Track 03PlannedReserved
Agentic Operating Systems
Scheduling, isolation, and resource control for fleets of agents.
- ·Agent process scheduling and priority
- ·Resource isolation: memory, tokens, compute per agent
- ·Inter-agent IPC and shared kernel services
- ·Multi-tenant agent runtimes
Coming later
how this is built
Free, runnable, opinionated.
No course platform. No paywall. Code that runs. Opinions where the field is messy.
Free and MIT-licensed
No signup, no email gate to read, nothing to buy. The repository for Track 01 is open on GitHub at the same SHA the site renders. Fork it, run it, teach a course off it.
Runnable code, not screenshots
Every code example that ships to a lesson is validated end-to-end in research/code-validation/ (Python via uv, TypeScript via tsc) before it lands. Hallucinated APIs that look plausible are the failure mode I’m most paranoid about.
Three tracks, one curriculum
Track 01 is the foundation: build agents that hold up. Track 02 is what most material skips: multi-agent systems are distributed systems, and the theory exists. Track 03 is the operating-system layer underneath, scheduled for later. You can read in any order.