Technical Documentation: rohitg00/ai-engineering-from-scratch
ℹ️ Provenance: Multi-Tier Ingestion · CodeWiki Reference
Overview (README.md)
Implement model internals, retrieval pipelines, and agent runtimes. Test them, inspect failures, and keep the code and evaluation results.
Start learning · Choose a path · Try a lab · Build a project · Browse the curriculum
Free, open source, MIT. Learn on the website, with a coding agent, or by running local code.
542 lessons. 20 phases. Python, TypeScript, Rust, Julia.
Read in your language
Sponsors
Learning paths
| Route | Starting lesson |
|---|---|
| Model foundations | Setup and tooling |
| LLM systems | Prompt engineering |
| Agents and delivery | The agent loop |
Compare career paths · Prerequisites and study time
Gradient descent
Twenty starting points follow gradient descent on a quadratic loss. The graph shows their positions and mean loss after each update.
Adjust the learning rate in the lesson · Compare GD, momentum, and Adam in code
Projects
Three projects with staged starters, reference implementations, and local graders. Run commands from the repository root after setup. Starters fail until you implement the stages.
01 · Retrieval Evaluation Lab · Python · Ranking metrics and regression checks
A candidate improves mean NDCG while one query ranks its most relevant evidence lower. Build a query-by-query comparison that reports the regression and can fail a release check.
Use Python 3.10+. Review RAG and model evaluation. Implement ranking validation, precision and recall, rank-sensitive metrics, then system comparison.
python3 scripts/project_test.py retrieval-evaluation-lab \
--init learning-artifacts/retrieval-evaluation-lab
python3 scripts/project_test.py retrieval-evaluation-lab \
--stage 1 --path learning-artifacts/retrieval-evaluation-lab --strict
python3 scripts/project_test.py retrieval-evaluation-lab \
--all --path learning-artifacts/retrieval-evaluation-lab --strictKeep: a reproducible comparison with per-query deltas and the judgments used to score them. Metrics describe those judgments; they do not establish answer correctness.
Start the project · Inspect the reference · Run on your own inputs
02 · Agent Trace Debugger · TypeScript · Trace parsing and timing
A supplied trace still takes 100 ms, but total token usage rises by 200 and one span starts failing. Separate overlapping child work from parent execution time, then produce a report that exposes the change.
Use Node.js 22.18+ and Python 3 for the grader. Implement JSONL parsing, parent validation, interval arithmetic, then an inspectable timeline.
python3 scripts/project_test.py agent-trace-debugger \
--init learning-artifacts/agent-trace-debugger
python3 scripts/project_test.py agent-trace-debugger \
--stage 1 --path learning-artifacts/agent-trace-debugger --strict
python3 scripts/project_test.py agent-trace-debugger \
--all --path learning-artifacts/agent-trace-debugger --strictKeep: the input trace, an HTML timeline, and a JSON regression report. Preserve exclusive per-span token counts so parent and child usage are not counted twice.
Start the project · Inspect the reference · Explore timing interactively
03 · Tool Call Firewall · Rust · Role checks and approval receipts
A write changes after review, or an approval is replayed. Validate the call envelope, check the caller's role and path, then consume an approval bound to the exact request and content.
Use Rust and Python 3.10+. Review tool schema design and security boundaries. The caller application supplies identity; the model proposes an operation.
python3 scripts/project_test.py tool-call-firewall \
--init learning-artifacts/tool-call-firewall
python3 scripts/project_test.py tool-call-firewall \
--stage 1 --path learning-artifacts/tool-call-firewall --strict
python3 scripts/project_test.py tool-call-firewall \
--all --path learning-artifacts/tool-call-firewall --strictKeep: an audit receipt showing the requested operation and the policy decision. Approvals are single-use within one invocation; this project does not provide persistent authorization or an operating-system sandbox.
Start the project · Inspect the reference · Explore approval boundaries
Browse all projects · Career practice guide
Choose how to learn
On the website
Open any completed lesson on aiengineeringfromscratch.com or expand a phase under Contents. No setup, no cloning.
With an AI tutor
If Node.js, npx, and a skill-capable coding agent are already installed, your coding agent can become your tutor. A repository clone is not needed to install or read the tutor. Runnable focused-path labs need python3. Agent Skills host labs also need a selected host and a writable user or project skill scope.
npx skills add rohitg00/ai-engineering-from-scratchChoose the host and scope when the installer asks. Use start-learning in Codex, /start-learning in Claude Code, or ask your host to use the skill by name.
Tutor setup and host commands
Check the local requirements first:
node --version
npx --version
python3 --versionskills writes to the host and scope selected during installation, such as.claude/skills/, .cursor/skills/, .codex/skills/, or another supported
skills folder. Verify that the selected host discovers that exact destination.
Invocation syntax belongs to the host, not to the portable SKILL.md format:
| Host | Start the course | Start Model Context Protocol (MCP) | Start Agent Skills | Run a phase quiz |
|---|---|---|---|---|
| Codex | start-learning, or choose it from /skills |
learn-mcp, or choose it from /skills |
learn-agent-skills, or choose it from /skills |
check-understanding 13, or choose it from /skills |
| Claude Code | /start-learning |
/learn-mcp |
/learn-agent-skills |
/check-understanding 13 |
| Other compatible hosts | Use start-learning to begin the course. |
Use learn-mcp to start the Model Context Protocol (MCP) path. |
Use learn-agent-skills to start the Agent Skills Engineering path. |
Use check-understanding to quiz me on Phase 13. |
A ten-question placement quiz maps what you already know to a starting phase and
saves a personalized study plan to LEARNING.md. From there, the learn skill
teaches one lesson per session: concept, math, code, quiz. It streams lessons
straight from this repo, and the course-guide skill jumps you to the exact
lesson that covers anything you are stuck on. In Codex, invoke these skills withlearn and course-guide; in Claude Code, use /learn and /course-guide;
in other compatible hosts, ask to use the skill by name.
Only want Model Context Protocol (MCP)? Use the MCP invocation for your host. It createsMCP-LEARNING.md and follows one 17-lesson route through stateless
requests, transports, bidirectional work, security, reliability, registry
governance, and conformance evidence. The exact order and checkpoints live in
the Model Context Protocol (MCP) manifest.
Only want Agent Skills? Use the Agent Skills invocation for your host. It
creates AGENT-SKILLS-LEARNING.md and follows one coherent five-lesson route:
contract, discovery, invocation, sandbox boundaries, then release evals and
real-host portability. Start on the web with the
Agent Skills path.
The installer lists the hosts it can configure and asks where to install. If
you do not have Node.js, npx, python3, a supported host, or a writable
scope yet, use the website or read docs/en.md manually. That path teaches the
concepts, but real-host discovery, invocation, script, and uninstall evidence
remains pending until the preflight is available. Read the lessons at
aiengineeringfromscratch.com.
The learning skills
| Skill | What it does |
|---|---|
start-learning |
One-time onboarding: why you're learning, placement quiz, personalized plan saved to LEARNING.md. |
learn |
The tutor loop. Warm-up recall, then the next lesson taught interactively, then its quiz; records progress and a review queue. |
course-guide |
Topic router. "Where do I learn attention?" or "my loss is NaN" → the exact lessons, with links. |
learn-mcp |
Focused Model Context Protocol (MCP) tutor. Creates MCP-LEARNING.md, follows the 17-lesson manifest, and records wire, security, reliability, and conformance evidence. |
learn-agent-skills |
Focused Agent Skills tutor. Creates AGENT-SKILLS-LEARNING.md, teaches lessons 22, 24, 25, 26, and 27, and records real-host evidence. |
learn-reverse-engineering |
Focused Reverse Engineering tutor. Creates REVERSE-ENGINEERING-LEARNING.md, teaches Phase 13 lessons 32 to 45 on programs you build yourself, and records lab evidence. |
claude-certification |
Certification tutor. Chooses CCAO-F, CCDV-F, CCAR-F, or CCAR-P; teaches each lesson; runs labs; reviews artifacts; administers diagnostics and mocks; saves progress. |
mcpa-certification |
MCPA tutor. Follows the 34-lesson mcpa-f route on the 2026-07-28 protocol; teaches each lesson; runs labs and the wire checker; administers the diagnostic and three mocks; saves progress. |
find-your-level |
Ten-question placement quiz. Maps your knowledge to a starting phase and produces a personalized path with hour estimates. |
check-understanding |
Per-phase quiz, eight questions, with feedback and specific lessons to review. Use the Codex, Claude Code, or natural-language form in the invocation table above. |
Run local code
git clone https://github.com/rohitg00/ai-engineering-from-scratch.git
cd ai-engineering-from-scratch
python3 phases/00-setup-and-tooling/01-dev-environment/code/verify.py --route beginner
python3 phases/01-math-foundations/01-linear-algebra-intuition/code/vectors.pyThe preflight separates requirements needed now from tools needed later. Every
required failure includes the detected reason and a corrective command. Thevectors.py command is a dependency-free lesson and ends by showing that a matrix
times a vector is the operation inside a neural network layer. Save that
terminal output as your first evidence.
Use every lesson the same way
Use every lesson the same way
- Read
docs/en.mdand explain the core idea in your own words. - Type and build the important code instead of treating the code block as decoration.
- Run the lesson command from the repository root, the directory containing
README.mdandphases/. - Keep evidence: the command, working directory, exit code, meaningful output, and the artifact you changed or produced.
- Continue only when you can explain the output and make one small change without guessing.
Commands in lesson pages are paths from the repository root unless the lesson
explicitly says to change directories. If a lesson offers several languages,
run the implementation for the language you are learning.
Choose a learning path
You do not need to scan 542 lessons before beginning. Pick one goal. Each link
opens the same curriculum on GitHub or the website, and both versions use the
same lesson code.
| Your goal | Learn on GitHub | Learn on the website |
|---|---|---|
| I am new and want the complete foundation | Phase 0: Setup and Tooling | Dev Environment |
| I know Python and want math plus ML foundations | Phase 1: Math Foundations | Linear Algebra Intuition |
| I want to build production LLM applications | Phase 11: LLM Engineering | Prompt Engineering |
| I want to build agents | Phase 14: Agent Engineering | The Agent Loop |
| I want to use coding agents on real repositories | Agent-Assisted Engineering path | Agent-Assisted Engineering |
| I want to shape the right build before implementation | Product Judgment and Delivery path | Product Judgment and Delivery |
Not sure where you fit? Use the start-learning placement tutor
or the website prerequisites guide.
Compare four core domains and six career routes in the AI Engineering Learning Paths.
Focused MCP, Agent Skills, and Reverse Engineering paths
| Your goal | Learn on GitHub | Learn on the website |
|---|---|---|
| I want to build with Model Context Protocol (MCP) | Model Context Protocol (MCP) route | Model Context Protocol (MCP) path |
| I want to write and ship Agent Skills | Focused Agent Skills route | Agent Skills path |
| I want to read compiled programs | Reverse Engineering route | Reverse Engineering path |
Prerequisites and study time
Prerequisites
- You can write code (any language; Python helps).
- You want to understand how AI actually works, not just call APIs.
Where to start
| Background | Start at | Estimated time |
|---|---|---|
| New to programming and AI | Phase 0 — Setup | ~306 hours |
| Know Python, new to ML | Phase 1 — Math Foundations | ~270 hours |
| Know ML, new to deep learning | Phase 3 — Deep Learning Core | ~200 hours |
| Know deep learning, want LLMs and agents | Phase 10 — LLMs from Scratch | ~100 hours |
| Senior engineer, only want agent engineering | Phase 14 — Agent Engineering | ~60 hours |
| Only want to build production MCP systems | Model Context Protocol (MCP) path | ~23 hours 15 min |
| Only want to build production Agent Skills | Agent Skills Engineering path | ~9.5 hours |
| Only want to learn reverse engineering | Reverse Engineering path | ~32.5 hours |
The shape of the curriculum
Twenty phases stack on top of each other. Math is the floor. Agents and production are the roof.
Skip ahead if you already know the lower layers, but don't skip and then wonder why something at
the top is breaking.
%%{init: {'theme':'base','themeVariables':{'primaryColor':'#fafaf5','primaryTextColor':'#1a1a1a','primaryBorderColor':'#3553ff','lineColor':'#3553ff','fontFamily':'JetBrains Mono','fontSize':'12px'}}}%%
flowchart TB
P0["Phase 0 — Setup & Tooling"] --> P1["Phase 1 — Math Foundations"]
P1 --> P2["Phase 2 — ML Fundamentals"]
P2 --> P3["Phase 3 — Deep Learning Core"]
P3 --> P4["Phase 4 — Vision"]
P3 --> P5["Phase 5 — NLP"]
P3 --> P6["Phase 6 — Speech & Audio"]
P3 --> P9["Phase 9 — RL"]
P5 --> P7["Phase 7 — Transformers"]
P7 --> P8["Phase 8 — GenAI"]
P7 --> P10["Phase 10 — LLMs from Scratch"]
P10 --> P11["Phase 11 — LLM Engineering"]
P10 --> P12["Phase 12 — Multimodal"]
P11 --> P13["Phase 13 — Tools & Protocols"]
P13 --> P14["Phase 14 — Agent Engineering"]
P14 --> P15["Phase 15 — Autonomous Systems"]
P15 --> P16["Phase 16 — Multi-Agent & Swarms"]
P14 --> P17["Phase 17 — Infrastructure & Production"]
P15 --> P18["Phase 18 — Ethics & Alignment"]
P16 --> P19["Phase 19 — Capstone Projects"]
P17 --> P19
P18 --> P19Contents
Twenty phases. Click any phase to expand its lesson list.
Phase 0: Setup & Tooling `13 lessons`
Get your environment ready for everything that follows.
| # | Lesson | Type | Lang |
|---|---|---|---|
| 01 | Dev Environment | Build | Python |
| 02 | Git & Collaboration | Learn | — |
| 03 | GPU Setup & Cloud | Build | Python |
| 04 | APIs & Keys | Build | Python |
| 05 | Jupyter Notebooks | Build | Python |
| 06 | Python Environments | Build | Shell |
| 07 | Docker for AI | Build | Docker |
| 08 | Editor Setup | Build | — |
| 09 | Data Management | Build | Python |
| 10 | Terminal & Shell | Learn | — |
| 11 | Linux for AI | Learn | — |
| 12 | Debugging & Profiling | Build | Python |
| 13 | Python for AI Engineering | Build | Python |
Phase 1 — Math Foundations 22 lessons The intuition behind every AI algorithm, through code.
Phase 2 — ML Fundamentals 21 lessons Classical ML — still the backbone of most production AI.
Phase 3 — Deep Learning Core 13 lessons Neural networks from first principles. No frameworks until you build one.
| # | Lesson | Type | Lang |
|---|---|---|---|
| 01 | The Perceptron: Where It All Started | Build | Python |
| 02 | Multi-Layer Networks & Forward Pass | Build | Python |
| 03 | Backpropagation from Scratch | Build | Python |
| 04 | Activation Functions: ReLU, Sigmoid, GELU & Why | Build | Python |
| 05 | Loss Functions: MSE, Cross-Entropy, Contrastive | Build | Python |
| 06 | Optimizers: SGD, Momentum, Adam, AdamW | Build | Python |
| 07 | Regularization: Dropout, Weight Decay, BatchNorm | Build | Python |
| 08 | Weight Initialization & Training Stability | Build | Python |
| 09 | Learning Rate Schedules & Warmup | Build | Python |
| 10 | Build Your Own Mini Framework | Build | Python |
| 11 | Introduction to PyTorch | Build | Python |
| 12 | Introduction to JAX | Build | Python |
| 13 | Debugging Neural Networks | Build | Python |
Phase 4 — Computer Vision 28 lessons From pixels to understanding — image, video, 3D, VLMs, and world models.
Phase 5 — NLP: Foundations to Advanced 29 lessons Language is the interface to intelligence.
Phase 6 — Speech & Audio 17 lessons Hear, understand, speak.
| # | Lesson | Type | Lang |
|---|---|---|---|
| 01 | Audio Fundamentals: Waveforms, Sampling, FFT | Learn | Python |
| 02 | Spectrograms, Mel Scale & Audio Features | Build | Python |
| 03 | Audio Classification | Build | Python |
| 04 | Speech Recognition (ASR) | Build | Python |
| 05 | Whisper: Architecture & Fine-Tuning | Build | Python |
| 06 | Speaker Recognition & Verification | Build | Python |
| 07 | Text-to-Speech (TTS) | Build | Python |
| 08 | Voice Cloning & Voice Conversion | Build | Python |
| 09 | Music Generation | Build | Python |
| 10 | Audio-Language Models | Build | Python |
| 11 | Real-Time Audio Processing | Build | Python |
| 12 | Build a Voice Assistant Pipeline | Build | Python |
| 13 | Neural Audio Codecs — EnCodec, SNAC, Mimi, DAC | Learn | Python |
| 14 | Voice Activity Detection & Turn-Taking | Build | Python |
| 15 | Streaming Speech-to-Speech — Moshi, Hibiki | Learn | Python |
| 16 | Voice Anti-Spoofing & Audio Watermarking | Build | Python |
| 17 | Audio Evaluation — WER, MOS, MMAU, Leaderboards | Learn | Python |
Phase 7 — Transformers Deep Dive 16 lessons The architecture that changed everything.
| # | Lesson | Type | Lang |
|---|---|---|---|
| 01 | Why Transformers: The Problems with RNNs | Learn | Python |
| 02 | Self-Attention from Scratch | Build | Python |
| 03 | Multi-Head Attention | Build | Python |
| 04 | Positional Encoding: Sinusoidal, RoPE, ALiBi | Build | Python |
| 05 | The Full Transformer: Encoder + Decoder | Build | Python |
| 06 | BERT — Masked Language Modeling | Build | Python |
| 07 | GPT — Causal Language Modeling | Build | Python |
| 08 | T5, BART — Encoder-Decoder Models | Learn | Python |
| 09 | Vision Transformers (ViT) | Build | Python |
| 10 | Audio Transformers — Whisper Architecture | Learn | Python |
| 11 | Mixture of Experts (MoE) | Build | Python |
| 12 | KV Cache, Flash Attention & Inference Optimization | Build | Python |
| 13 | Scaling Laws | Learn | Python |
| 14 | Build a Transformer from Scratch | Build | Python |
| 15 | Attention Variants — Sliding Window, Sparse, Differential | Build | Python |
| 16 | Speculative Decoding — Draft, Verify, Repeat | Build | Python |
Phase 8 — Generative AI 15 lessons Create images, video, audio, 3D, and more.
| # | Lesson | Type | Lang |
|---|---|---|---|
| 01 | Generative Models: Taxonomy & History | Learn | Python |
| 02 | Autoencoders & VAE | Build | Python |
| 03 | GANs: Generator vs Discriminator | Build | Python |
| 04 | Conditional GANs & Pix2Pix | Build | Python |
| 05 | StyleGAN | Build | Python |
| 06 | Diffusion Models — DDPM from Scratch | Build | Python |
| 07 | Latent Diffusion & Stable Diffusion | Build | Python |
| 08 | ControlNet, LoRA & Conditioning | Build | Python |
| 09 | Inpainting, Outpainting & Editing | Build | Python |
| 10 | Video Generation | Build | Python |
| 11 | Audio Generation | Build | Python |
| 12 | 3D Generation | Build | Python |
| 13 | Flow Matching & Rectified Flows | Build | Python |
| 14 | Evaluation: FID, CLIP Score | Build | Python |
| 19 | Visual Autoregressive Modeling (VAR): Next-Scale Prediction | Build | Python |
Phase 9 — Reinforcement Learning 12 lessons The foundation of RLHF and game-playing AI.
| # | Lesson | Type | Lang |
|---|---|---|---|
| 01 | MDPs, States, Actions & Rewards | Learn | Python |
| 02 | Dynamic Programming | Build | Python |
| 03 | Monte Carlo Methods | Build | Python |
| 04 | Q-Learning, SARSA | Build | Python |
| 05 | Deep Q-Networks (DQN) | Build | Python |
| 06 | Policy Gradients — REINFORCE | Build | Python |
| 07 | Actor-Critic — A2C, A3C | Build | Python |
| 08 | PPO | Build | Python |
| 09 | Reward Modeling & RLHF | Build | Python |
| 10 | Multi-Agent RL | Build | Python |
| 11 | Sim-to-Real Transfer | Build | Python |
| 12 | RL for Games | Build | Python |
Phase 10 — LLMs from Scratch 24 lessons Build, train, and understand large language models.
Phase 11 — LLM Engineering 17 lessons Put LLMs to work in production.
| # | Lesson | Type | Lang |
|---|---|---|---|
| 01 | Prompt Engineering: Techniques & Patterns | Build | Python |
| 02 | Few-Shot, CoT, Tree-of-Thought | Build | Python |
| 03 | Structured Outputs | Build | Python |
| 04 | Embeddings & Vector Representations | Build | Python |
| 05 | Context Engineering | Build | Python |
| 06 | RAG: Retrieval-Augmented Generation | Build | Python |
| 07 | Advanced RAG: Chunking, Reranking | Build | Python |
| 08 | Fine-Tuning with LoRA & QLoRA | Build | Python |
| 09 | Function Calling & Tool Use | Build | Python |
| 10 | Evaluation & Testing | Build | Python |
| 11 | Caching, Rate Limiting & Cost | Build | Python |
| 12 | Guardrails & Safety | Build | Python |
| 13 | Building a Production LLM App | Build | Python |
| 14 | Model Context Protocol (MCP) | Build | Python |
| 15 | Prompt Caching & Context Caching | Build | Python |
| 16 | Agent State Machines — Graphs, Nodes, Checkpoints | Build | Python |
| 17 | Agent Framework Tradeoffs | Learn | Python |
Phase 12 — Multimodal AI 25 lessons See, hear, read, and reason across modalities — from ViT patches to computer-use agents.
Phase 13 — Tools & Protocols 45 lessons The interfaces between AI and the real world.
Lessons 06-18 and 28-31 form the focused
Model Context Protocol (MCP) path. Its manifest order
is 06, 07, 08, 09, 10, 11, 12, 13, 14, 15, 16, 18, 17, 28, 29, 30, 31. Start
it with the host-specific learn-mcp invocation above. Lesson 23
is its only optional capstone and also requires Lessons 19 and 20.
Lessons 22 and 24-27 form the focused
Agent Skills learning path, from package
contract through real-host release gates. Start it with the host-specificlearn-agent-skills invocation shown above; do not follow numeric next
navigation from 22 to 23.
Phase 14 — Agent Engineering 54 lessons Build agents from first principles, use coding agents reliably, and shape the work before implementation.
Each Phase 14 workbench lesson (31-42) ships a mission.md briefing the agent before it opens the full lesson docs.
Lessons 31-46 form the Agent-Assisted Engineering path.
Its manifest order combines the workbench foundation with task framing, planning,
delegation, and durable feedback. Lessons 47-54 form the
Product Judgment and Delivery path, from outcome framing
through evidence, risk, scope, measurement, staged release, and feedback ownership.
Phase 15 — Autonomous Systems 22 lessons Long-horizon agents, self-improvement, and the 2026 safety stack.
Phase 16 — Multi-Agent & Swarms 25 lessons Coordination, emergence, and collective intelligence.
Phase 17 — Infrastructure & Production 29 lessons Ship AI to the real world.
Phase 18 — Ethics, Safety & Alignment 30 lessons Build AI that helps humanity. Not optional.
Phase 19 — Capstone Projects 85 lessons 17 end-to-end products + 9 deep-build tracks. 20-40 hours per project; 4-12 lessons per track.
Deep-build tracks — multi-lesson series that build a complete subsystem from scratch.
Books and certifications
Read the core curriculum as a book
The 20-phase core curriculum under phases/ compiles into a six-volume book series. EPUB and PDF are built by CI from the same core lesson sources and attached to every GitHub release; the links below always resolve to the newest release. Volume numbers index the series, not versions: each copy carries a dated edition stamp, and older editions stay downloadable from their release.
Certification curricula are intentionally not converted into the books. Their
AI tutor state, runnable labs, interactive figures, diagnostics, and timed mocks
remain first-class on GitHub and the website.
| Vol | Title | Phases | Download |
|---|---|---|---|
| 1 | Foundations · Math, Tooling, and Classical Machine Learning | 00-02 | EPUB · PDF |
| 2 | Deep Learning · Networks, Vision, and Speech | 03, 04, 06 | EPUB · PDF |
| 3 | Language · NLP Foundations and the Transformer | 05, 07 | EPUB · PDF |
| 4 | Large Language Models · Generation, Reinforcement, Pretraining, and Engineering | 08-11 | EPUB · PDF |
| 5 | Agents · Multimodality, Protocols, Autonomy, and Swarms | 12-16 | EPUB · PDF |
| 6 | Production · Infrastructure, Safety, and Capstones | 17-19 | EPUB · PDF |
The book is the snapshot; this repository is the living edition. Every chapter ends with links back to the lesson's animated figures, quiz, and runnable code. Build locally with python3 scripts/build_book.py (pandoc required); pipeline details in book/README.md.
Prepare for Claude certifications
The Claude Certification Academy is a free,
open-source preparation program for all four official Claude certification tracks:
Associate Foundations, Developer Foundations, Architect Foundations, and Architect
Professional. Each route combines blueprint-mapped lessons, runnable labs, a
diagnostic, capstone work, and a full-length original practice exam.
Use the AI-native GitHub onboarding guide
with Claude Code, Codex, ChatGPT, Cursor, or another agent. Runclaude-certification in Codex, /claude-certification in Claude Code, or ask
another host to use claude-certification. It chooses a track, creates a
persistent route in CLAUDE-CERTIFICATION.md, teaches one step at a time, runs
the real labs, and gives artifact-based feedback. The same curriculum remains
available on the certification website.
The academy is independent study material based on public exam objectives. It is not
affiliated with Anthropic, does not reproduce live exam questions, and cannot guarantee
a passing score.
Prepare for MCP Associate (MCPA)
The MCPA Certification Curriculum is a free,
open-source preparation program for the Model Context Protocol Associate exam from the
Agentic AI Foundation, delivered through Linux Foundation Training. Its 34 lessons teach
the stateless 2026-07-28 protocol across the five exam domains: per-request _meta andserver/discover in place of the old handshake, multi round-trip requests, subscriptions,
caching, the tasks and MCP Apps extensions, OAuth authorization, and the registry and SDK
tiers. Every lesson ships a runnable standard-library lab whose transcript is checked for
the current wire shape, and the track adds a diagnostic, a capstone, and three full-length
original practice exams whose question mix follows the published blueprint weights.
Use the AI-native GitHub onboarding guide with
Claude Code, Codex, ChatGPT, Cursor, or another agent. Run mcpa-certification in Codex,/mcpa-certification in Claude Code, or ask another host to use mcpa-certification. It
creates a persistent route in MCPA-CERTIFICATION.md, teaches one step at a time, runs
the real labs, and gives artifact-based feedback. The same curriculum is available on the
MCPA track page.
This curriculum is independent study material based on public exam objectives. It is not
affiliated with the Agentic AI Foundation or the Linux Foundation, does not reproduce
live exam questions, and cannot guarantee a passing score.
The toolkit
Every lesson produces a reusable artifact. Install one in your agent or use the scripts below from the repository root.
Lesson structure and reusable artifacts
The shape of a lesson
Each lesson lives in its own folder, with the same structure across the entire curriculum:
phases/<NN>-<phase-name>/<NN>-<lesson-name>/
├── code/ runnable implementations (Python, TypeScript, Rust, Julia)
├── docs/
│ └── en.md lesson narrative
└── outputs/ prompts, skills, agents, or MCP servers this lesson producesEvery lesson follows six beats. The Build It / Use It split is the spine — you implement the
algorithm from scratch first, then run the same thing through the production library. You
understand what the framework is doing because you wrote the smaller version yourself.
%%{init: {'theme':'base','themeVariables':{'primaryColor':'#fafaf5','primaryTextColor':'#1a1a1a','primaryBorderColor':'#3553ff','lineColor':'#3553ff','fontFamily':'JetBrains Mono','fontSize':'13px'}}}%%
flowchart LR
M["MOTTO<br/><sub>one-line core idea</sub>"] --> Pr["PROBLEM<br/><sub>concrete pain</sub>"]
Pr --> C["CONCEPT<br/><sub>diagrams & intuition</sub>"]
C --> B["BUILD IT<br/><sub>raw math, no frameworks</sub>"]
B --> U["USE IT<br/><sub>same thing in PyTorch / sklearn</sub>"]
U --> S["SHIP IT<br/><sub>prompt · skill · agent · MCP</sub>"]Every lesson ships something
Other curricula end with "congratulations, you learned X." Each lesson here ends with a
reusable tool you can install or paste into your daily workflow.
| FIG_001 · APROMPTS | FIG_001 · BSKILLS | FIG_001 · CAGENTS | FIG_001 · DMCP SERVERS |
|---|---|---|---|
| Paste into any AI assistant for expert-level help on a narrow task. | Drop into Claude, Cursor, Codex, OpenClaw, Hermes, or any agent that reads SKILL.md. |
Deploy as autonomous workers — you wrote the loop yourself in Phase 14. | Plug into any MCP-compatible client. Built end-to-end in Phase 13. |
Install lesson artifacts
The lesson artifacts. The repo ships 414 skills and 100 prompts underphases/**/outputs/; install them via scripts/install_skills.py. Requires
cloning the repo. Supports tag filters, dry-runs, and per-agent layouts:
python3 scripts/install_skills.py <target> # every skill, default --layout skills (nested)
python3 scripts/install_skills.py <target> --layout skills # same as above, explicit
python3 scripts/install_skills.py <target> --type all # skills + prompts + agents
python3 scripts/install_skills.py <target> --phase 14 # one phase only
python3 scripts/install_skills.py <target> --tag rag # filter by tag
python3 scripts/install_skills.py <target> --layout flat # flat files
python3 scripts/install_skills.py <target> --dry-run # preview without writing
python3 scripts/install_skills.py <target> --force # overwrite existing files<target> is the skills directory for your agent (examples:~/.claude/skills/, ~/.cursor/skills/, ~/.config/openclaw/skills/,.skills/, or any path your agent reads).
By default the script refuses to overwrite an existing destination and exits
with code 1 after listing every colliding path. Use --dry-run to preview
collisions or --force to overwrite. Every non-dry-run run writes amanifest.json in the target with the full inventory grouped by type and
phase. Pick the layout your agent reads:
--layout |
Path written |
|---|---|
skills |
<target>/<name>/SKILL.md (nested convention, supported by Claude / Cursor / Codex / OpenClaw / Hermes) |
by-phase |
<target>/phase-NN/<name>.md |
flat |
<target>/<name>.md |
Drop the agent workbench into your own repo
The Phase 14 capstone ships a reusable Agent Workbench pack (AGENTS.md, schemas,
init / verify / handoff scripts). Scaffold it into any repo with:
python3 scripts/scaffold_workbench.py path/to/your-repo # full pack + seeds
python3 scripts/scaffold_workbench.py path/to/your-repo --minimal # skip docs/
python3 scripts/scaffold_workbench.py path/to/your-repo --dry-run # preview only
python3 scripts/scaffold_workbench.py path/to/your-repo --force # overwriteYou get the seven workbench surfaces wired up, a starter task_board.json,
and a fresh agent_state.json at schema_version: 1. From there: edit the
task, edit AGENTS.md, run scripts/init_agent.py, hand the contract to
your agent. The pack source lives atphases/14-agent-engineering/42-agent-workbench-capstone/outputs/agent-workbench-pack/.
Browse the entire course as JSON
scripts/build_catalog.py walks every phase, every lesson, every artifact on
disk and writes catalog.json at the repo root. One file, every course truth.
python3 scripts/build_catalog.py # writes <repo>/catalog.json
python3 scripts/build_catalog.py --stdout # to stdout, do not touch repo
python3 scripts/build_catalog.py --out path/to/file.jsonThe catalog is filesystem-derived, not README-derived, so counts always match
what is actually on disk. Use it for site builds, downstream tooling, or to
verify the README counts have not drifted. Schema is documented at the top of
the script.
The curriculum workflow builds catalog.json as an ephemeral, gitignored
artifact. Do not commit it. The same workflow runs audit_lessons.py as a
blocking check.
Smoke-check every lesson's Python code
scripts/lesson_run.py byte-compiles every .py file under each lesson'scode/ directory. Default mode is syntax-check only — no execution, no API
keys, no heavy ML deps required. Catches the regressions contributors
introduce most often (bad indentation, broken f-strings, stray edits).
python3 scripts/lesson_run.py # syntax-check the whole curriculum
python3 scripts/lesson_run.py --phase 14 # one phase only
python3 scripts/lesson_run.py --json # JSON report on stdout
python3 scripts/lesson_run.py --strict # exit 1 if any lesson fails
python3 scripts/lesson_run.py --execute # actually run, 10s timeout per lesson--execute runs each lesson's code/main.py (or the first .py file) with a
10-second timeout. Lessons whose entry file starts with a # requires: pkg1, pkg2 comment listing non-stdlib deps are skipped with reason needs <deps>.
The script is opt-in and not wired into CI.
Stdlib only, Python 3.10+. Set LINK_CHECK_SKIP=domain1,domain2 to override
the default skip-list (twitter.com, x.com, linkedin.com,instagram.com, medium.com — domains that aggressively block automated
HEAD/GET).
Foundational papers and protocols
- Attention Is All You Need — Vaswani et al., 2017 → Phase 7
- Language Models are Few-Shot Learners (GPT-3) → Phase 10
- Denoising Diffusion Probabilistic Models → Phase 8
- InstructGPT / RLHF → Phase 10
- Direct Preference Optimization → Phase 10
- Chain-of-Thought Prompting → Phase 11
- ReAct: Reasoning + Acting in LLMs → Phase 14
- Model Context Protocol — Anthropic → Phase 13
Contributing
| Goal | Read |
|---|---|
| Contribute a lesson or fix | CONTRIBUTING.md |
| Fork for your team or school | FORKING.md |
| Lesson template | LESSON_TEMPLATE.md |
| Track progress | ROADMAP.md |
| Glossary | glossary/terms.md |
| Code of conduct | CODE_OF_CONDUCT.md |
Before submitting a lesson, run the invariant check:
python3 scripts/audit_lessons.py # full curriculum
python3 scripts/audit_lessons.py --phase 14 # single phase
python3 scripts/audit_lessons.py --json # CI-friendly outputExit code is non-zero when any rule fails. Rules (L001–L010) validate directory
shape, docs/en.md presence + H1, code/ non-emptiness, quiz.json schema
(rejects the legacy q/choices/answer keys that caused issue #102), and
relative links inside lesson docs.
Sponsor the work
Free, MIT-licensed, 542 lessons. Thank you to the sponsors and backers who make the work possible.
See all sponsors and backers.
Want to support the work? See sponsorship options, including
hardware sponsorships, or
sponsor on GitHub.
If this manual helped you, star the repo. It keeps the project alive.
License
MIT. Use it however you want — fork it, teach it, sell it, ship it. Attribution appreciated,
not required.
Maintained by Rohit Ghumare and the community.
[@ghumare64](https://x.com/ghumare64) · [aiengineeringfromscratch.com](https://aiengineeringfromscratch.com) · [Report / Suggest](https://github.com/rohitg00/ai-engineering-from-scratch/issues/new/choose)I18n (`docs/i18n.md`)
Internationalization (i18n)
The English lessons are canonical. Translated lesson markdown is generated by the pipeline or contributed for review and never committed to main — it lives on a separate translations branch, and the site fetches it at runtime the same free way it fetches English (raw.githubusercontent.com). No Vercel functions, no KV, no per-view cost. The per-language README is maintained separately and committed to main (see below).
This pipeline covers lessons under phases/ only. Certification curricula remain English-only and are intentionally excluded from both machine translation and book generation.
The default engine is NLLB-200 (No Language Left Behind, Meta AI, 2022), an open translation model covering 200 languages, which runs inside the GitHub Actions runner with no API key and no bill. Compute is the free CI runner; there is no translation-API cost at all. Paid LLM providers (Anthropic/OpenAI) and DeepL remain available as optional higher-quality upgrades via --provider.
Pieces
The languages.json registry drives automatic lesson translation, interface translation, and the site switcher. The book builder also reads its language names. The per-language README is separate: full documents are listed in FULL_LOCALES in scripts/audit_readme_locales.py and maintained in i18n/<lang>/README.md. The block mappings in scripts/readme_translations.py remain available as drafting aids. Neither README list enables lesson or interface jobs.
| Piece | Where | Committed to main? |
|---|---|---|
| Language registry | languages.json |
Yes (one small file) |
| Lesson translation script | scripts/translate_lessons.py (prose-only walker) |
Yes |
| README maintenance + structural audit | scripts/build_readme_i18n.py + scripts/audit_readme_locales.py |
Yes |
| CI workflow | .github/workflows/translate.yml (sharded per language × phase) |
Yes |
| Translated lesson markdown | translations branch, i18n/<lang>/…/<lang>.md |
No (separate branch) |
| Translated README | i18n/<lang>/README.md, linked from the header of README.md |
Yes |
| Translated books | scripts/build_book.py --lang <code> reads the translated markdown and emits aiefs-vol{n}-{slug}-<lang>.epub/.pdf as release assets (English fallback per lesson) |
No (release assets) |
| Switcher options | site/langs.js (generated by build.js from the source/ci:true/site:true set) |
No (gitignored, like data.js) |
| Site switcher | site/lesson.html |
Yes (the UI + fetch logic) |
| Site chrome strings (navigation, sidebar, checkpoints, panels) | site/ui-strings.json (English key list + per-language overrides) + scripts/translate_ui_strings.py + site/ui-i18n.js (runtime) |
Yes (source and runtime) |
| Translated chrome strings | translations branch, i18n/<lang>/ui.json, fetched by the runtime |
No (separate branch) |
Add a language
Add one entry to languages.json, the single source of truth. Fields:
code— the tag used in filenames, URLs, and the switcher value.name— English name, used in the LLM-provider prompt.native— label shown in the switcher.nllb— the FLORES-200 code (e.g.zho_Hans,tur_Latn); required for the default NLLB provider —translate_lessons.pyexits if a requested language has none.ci-trueenables automatic lesson and interface translation and makes the language selectable on the site.site-truemakes a language selectable and enables automatic interface translation without automatically translating its lessons. Use this for contributor-maintained lessons.
The lesson matrix reads ci: true. The interface matrix and the site switcher accept either ci: true or site: true; the switcher also includes the English source. An explicit workflow_dispatch request can translate any registered non-source language, including contributor-maintained locales, so only request those locales when replacing changed lesson translations is intended.
Brazilian Portuguese (pt-BR) and Persian (fa) use the automatic pipeline. The existing Portuguese (pt) URL remains supported. Both Portuguese tags use NLLB's por_Latn model code, which does not distinguish regional varieties. Brazilian README and interface wording can be pinned explicitly; automated lesson prose still benefits from Brazilian Portuguese review.
Traditional Chinese (zh-TW) uses site: true so reviewed lessons can arrive through PRs against the translations branch without being overwritten on an English-source update. Put them at i18n/zh-TW/phases//<lesson>/docs/zh-TW.md, retaining the English code, paths, links, and metadata keys. The site falls back to English for lessons not yet published. This flag enables the interface and lesson reader; it does not add a translated-book release workflow.
The README bar is independent: it lists 33 locales plus canonical English. Regional tags such as pt-BR and zh-TW are distinct README destinations. To add a complete README translation, translate the full document, add its link to the root README, and add its code to FULL_LOCALES after the coverage and structure audit passes. Keep repository-relative targets correct from two directories deep. Do not publish partial drafts in the language bar. Its locale set must exactly match FULL_LOCALES; the maintenance command never generates or publishes partial documents.
How it runs
- A push to
mainthat changesphases/**/docs/en.md,languages.json, the interface strings, the job selector, or the translation workflow itself triggers.github/workflows/translate.yml. Certification lesson changes do not trigger it.scripts/translate_matrix.pythen reads the pushed range and starts only the jobs it can change: one job per automatic language for each phase whosedocs/en.mdchanged, every phase for a language newly markedci: true, and interface-string jobs whensite/ui-strings.jsonor its translator changed or a language is newly markedciorsite. A registry edit that changes only metadata such asdir,locale, or a name starts none. If the push also changes the code the jobs run (translate.yml,translate_lessons.pyand the modules it imports, or.github/translate-requirements.txt), or the script cannot read the range (a new branch, a force-push, a missing commit), it starts every job. A manual run keeps the requested languages and phase. - The matrix is one job per (language, phase). A full 523-lesson language run is ~27h on a CPU runner, far past the 6-hour job limit, so a per-language job always timed out before publishing. Splitting by phase keeps the largest job (phase 19, 85 lessons) near ~4.5h, well under the limit. Each job restores its language's prior output from the branch, runs
translate_lessons.py --phase, and pushes only its owni18n/<lang>/phases//slice back with a fetch-and-retry loop, so disjoint slices merge without collisions. - The site's language switcher sets
?lang=<code>;fetchLessonpulls…/translations/i18n/<lang>/…/<lang>.mdand falls back to canonical English if that translation isn't published yet. English (lang=en) is byte-identical to the pre-i18n fetch path.
Never wastes a run
Every lesson is keyed by the sha256 of its English source in a per-(language, phase) cache (i18n/<lang>/.cache/.json), written per lesson in the runner and published to the translations branch when the job finishes. So:
- The first run translates everything once. Every completed run after it re-translates only lessons whose English actually changed — everything else is a cache hit and is skipped instantly.
- A cancelled or interrupted phase job does not publish, so it loses that job's runner-local progress and the next run that includes that phase resumes it from the last published cache. Because each shard is a single phase, it comfortably finishes and publishes within the job limit. A push includes a phase only when its English changed, so after a failed or cancelled run, start the workflow manually with blank inputs to resume every phase.
Per-language README
The README is the landing page. Locales listed in FULL_LOCALES translate reader-visible prose, headings, tables, lesson titles, link labels, and image descriptions. Code, commands, identifiers, URLs, and relative destinations stay unchanged; product names, published paper titles, and established technical terms can retain their original spelling. Each full i18n/<lang>/README.md is maintained as a document so regeneration preserves editorial corrections.
All 33 non-English destinations in the README language bar are full documents. The historical block renderer remains a drafting aid; it does not publish files through the maintenance command. Add a new language only after translating the whole README, adding it to FULL_LOCALES, and updating the language bar in every locale.
When the English README changes, update the affected passages in every locale. i18n/readme-source.sha256 records the reviewed English source, excluding only the reader count, page-view count, and date in the statistics block. A changed heading, paragraph, table, link, or diagram fails CI until the translations are reviewed. After reviewing all locales, update the record and run the checks:
python3 - <<'PYTHON'
import sys
sys.path.insert(0, 'scripts')
from audit_readme_locales import SOURCE, SOURCE_DIGEST, source_fingerprint
SOURCE_DIGEST.write_text(source_fingerprint(SOURCE.read_text(encoding='utf-8')) + '\n', encoding='utf-8')
PYTHON
python3 scripts/build_readme_i18n.py --check
python3 scripts/test_audit_readme_locales.pyThe audit compares heading and prose-block counts, link destinations, explicit anchors, every linked lesson row (528 at present), programming-language labels, Markdown and HTML table structure, fenced and inline code, command examples, Mermaid topology, and numeric facts in the introduction, statistics, phase summaries, and study-time table. It rejects unchanged English prose, headings, table cells, image descriptions, diagram labels, and directory-tree descriptions, with explicit exceptions for shared technical names and language-specific spellings. These checks detect incomplete coverage and structural drift; they cannot certify fluency or nuanced technical meaning, which need editorial review.
CI runs the coverage and structure checks. The README-counts bot copies only the reader count, page-view count, and ISO date into each locale's statistics block after validation. It preserves translated wording and never regenerates full documents from the partial block map. Changes to lesson counts or other English content still require translation review before the bot can publish an update.
Site chrome
Lesson bodies come from the translations branch, but the interface around them (header navigation, the lesson sidebar toggle, "On this page", the checkpoint loop, quiz headings, the code and outputs panels, previous/next buttons, homepage and catalog labels) is static English in the page templates. site/ui-i18n.js translates that layer in the browser. header.js loads it on every page, so a page cannot silently omit it.
site/ui-strings.jsonis the only hand-maintained input.keyslists the English interface strings the pages use (the gettext model: the English text is the message id).overridespins a translation per language where a machine translation would be wrong, mostly one-word labels such as Build, Run, Prove, or Complete. Add a label by appending it tokeys; add a language by flagging itci: trueorsite: trueinlanguages.json. Neither needs a translation written by hand.scripts/translate_ui_strings.pyruns intranslate.yml(one small job perci:trueorsite:truelanguage) and writesi18n/<lang>/ui.jsonto thetranslationsbranch. For each key it takes the override if there is one, else the previously published translation (the published file records which keys were pinned, so a removed override is retranslated rather than frozen), else it translates through the same provider layer as the lessons (NLLB by default,--provider anthropic|openai|deeplas upgrades). File names, paths, commands,@handles, and the{n}count placeholder are shielded behind the same placeholders the lesson translator uses, and a key whose placeholder does not survive is left English rather than published wrong. Most runs translate nothing and never load the model.site/ui-i18n.jsfetchesi18n/<lang>/ui.jsonfrom the translations branch at runtime, the same path lessons use, and falls back to English when a language has not been published yet. It walks text nodes plusaria-label,title, andplaceholderattributes, skipping code, the rendered lesson markdown (except the panels the site injects into it), quiz content, lesson titles, and the language picker's native names. AMutationObservercovers chrome the page renders later, and switching back to English restores the original strings. A key can hold{n}where the page shows a count that the build fills from the data, such as the catalog intro: the runtime matches the text with any number in that place and carries the number into the translation, so a new phase or lesson never orphans the key. In a right-to-left language, any eligible English text the dictionary did not translate (curriculum data, glossary entries, untranslated copy) getslang="en" dir="ltr"on its element, so its punctuation and number ranges read correctly, while translated chrome keeps the page direction. Flex and grid containers are left alone so component layout still mirrors, and switching language removes the marks.- The picker dispatches an
aifs:langDOM event on change, so the runtime works on pages that have noAIFS_onLangChangehandler, such as the homepage. - Two guards run in
curriculum.yml.node --test site/test_ui_i18n.jsfails when a key no longer appears in any page or script, or when an override pins a key that is not in the list, so a copy edit names the orphaned key instead of silently dropping its translations.python3 scripts/test_translate_ui_strings.pycovers the translator's precedence (override, then published, then model), placeholder protection, and the end-to-end write.
What is protected during translation
NLLB is a sentence translator, not an instruction-following model, so the walker never lets it see anything but prose. It processes the lesson line by line: fenced code blocks, tables, image lines, and the metadata header (**Type:** … **Time:**) pass through verbatim; on every other line it protects inline `code`, $math$, image refs, full markdown links, **bold** terms, and URLs behind placeholders, translates only the plain-text fragments between them, then restores. Bold spans are kept because in this course they are almost always technical terms (Skip-gram, negative sampling) that should stay English.
This is verified mechanically: running the walker with an identity "translation" reproduces all 523 lessons byte-for-byte, so a real run can only ever change prose. If a placeholder fails to round-trip, that lesson keeps its English (fail-safe).
Cost
Default provider nllb: free. NLLB-200 runs in the GitHub Actions runner — no API key, no secret, no per-token bill. The only resource is free CI compute; the model is cached between runs and only changed lessons are re-translated (sha256 cache). Vercel cost does not change.
Optional upgrades (--provider anthropic|openai|deepl) give higher fluency at low-tens-of-dollars per full pass per language, if you later want to polish a high-traffic language. Those providers read the key from the LLM_API_KEY environment variable (DeepL uses the same variable for its auth key). NLLB stays the zero-cost default.
Quality sample
Below is 05 · 03 Word Embeddings translated through Step 1, showing that prose reads naturally while code, math, king - man + woman, technical terms, and the metadata header survive untouched. This sample is LLM-tier fluency (what --provider anthropic produces); the free NLLB-200 default is solid and fully faithful on the preservation guarantee, with slightly plainer phrasing. Upgrade a high-traffic language to an LLM provider later if you want this level of polish.
简体中文 (zh)
词嵌入 —— 从零实现 Word2Vec
词以其所处的语境为意。用一个浅层网络训练这个想法,几何结构便会自然浮现。
Type: Build · Languages: Python · Prerequisites: 阶段 5 · 02(BoW + TF-IDF)、阶段 3 · 03(从零实现反向传播) · Time: 约 75 分钟
问题 —— TF-IDF 知道
dog和puppy是不同的词,但不知道二者含义几乎相同。在dog上训练的分类器无法泛化到讨论puppy的评论。你可以靠列举同义词勉强弥补,但这在罕见词、领域术语,以及所有你未曾预料的语言上都会失效。你想要的是这样一种表示:
dog和puppy在空间中彼此靠近;king - man + woman落在queen附近;在dog上训练的模型能免费地把部分信号迁移到puppy。核心概念 —— 分布假说(Firth,1957):"要了解一个词,就看它与哪些词为伴。" Word2Vec 有两种形式:Skip-gram 给定中心词预测周围词(窗口为 2 时
cat -> (the, sat, on));CBOW(连续词袋) 给定周围词预测中心词。网络只有一个隐藏层且无非线性:输入是词表上的 one-hot 向量,输出是 softmax,训练后丢弃输出层,隐藏层权重即为嵌入。诀窍是用**负采样(negative sampling)**把对 10 万词的 softmax 转成二分类。
Türkçe (tr)
Kelime Gömmeleri —— Word2Vec'i Sıfırdan
Bir kelime, birlikte bulunduğu kelimelerden ibarettir. Bu fikri sığ bir ağ ile eğitin, geometri kendiliğinden ortaya çıkar.
Type: Build · Languages: Python · Prerequisites: Aşama 5 · 02 (BoW + TF-IDF), Aşama 3 · 03 (Sıfırdan Geri Yayılım) · Time: ~75 dakika
Problem —— TF-IDF,
dogvepuppy'nin farklı kelimeler olduğunu bilir ama neredeyse aynı anlama geldiklerini bilmez.dogüzerinde eğitilen bir sınıflandırıcı,puppyhakkındaki bir yoruma genelleme yapamaz. Eş anlamlıları listeleyerek geçiştirebilirsiniz, ama bu; nadir terimlerde, alana özgü jargonda ve öngöremediğiniz her dilde başarısız olur.
dogvepuppy'nin uzayda birbirine yakın düştüğü,king - man + woman'ınqueen'e yakın indiği bir temsil istiyorsunuz. Word2Vec bunu verdi: iki katmanlı bir ağ, trilyon token'lık eğitim, 2013'te yayımlandı.Kavram —— Dağılımsal hipotez (Firth, 1957): "Bir kelimeyi birlikte bulunduğu kelimelerden tanırsın." İki tür: Skip-gram merkez kelimeden çevredekileri tahmin eder (pencere 2 ile
cat -> (the, sat, on)); CBOW çevredekilerden merkezi tahmin eder. Ağın doğrusal olmayan aktivasyonu olmayan tek bir gizli katmanı vardır: girdi one-hot vektör, çıktı softmax'tır; eğitimden sonra çıktı katmanı atılır, gizli katman ağırlıkları gömmelerdir. Püf nokta, 100 bin kelimelik softmax'ı negatif örnekleme (negative sampling) ile ikili sınıflandırmaya çevirmektir.
Note how dog, puppy, king - man + woman, softmax, one-hot, Skip-gram, CBOW, TF-IDF, Word2Vec, and the **Type:** / **Time:** labels stay verbatim in both languages while the surrounding prose is fully localized. That preservation is enforced mechanically by the placeholder round-trip, not left to the model.
--- METRICS ---
- Files Extracted: 2
- Estimated Token Budget: ~33564 tokens
- Canonical Reference: https://codewiki.google/github.com/rohitg00/ai-engineering-from-scratch