FAQ
Do I Need API Keys?
No. Every lab runs without keys: the API labs fall back to a free open model, and Module 12 falls back to a small decision model you train in the lab. A result from a fallback describes that model, not OpenAI, Claude or Jev. Keys for OpenAI, Anthropic and TypeSafe let you run the commercial models themselves. See Setup.
Do I Need a GPU?
The labs are designed for Google Colab’s free tier: a T4 GPU for most labs, a CPU runtime for Labs 1, 9, 11 and 12. Each lab’s planning estimate is ten minutes of compute or less. Those are estimates. Which labs have actually been run and timed, and on which machines, is on the readiness page:
As of 2026-10-09: not yet ready to teach. 0 of 15 labs have run end to end, with their current code, on the Colab runtime they are designed for. 15 have run end to end on their real path elsewhere, on another machine or on the CI runner, and 0 more in part. On the GitHub CPU runner (newest run of each notebook, 2026-10-06), 16 of 16 notebooks passed; 9 of the passing runs used test doubles, which check that the code runs, not what the models do. 8 of 11 pieces of blocking work are open. What has run, where, and what is missing.
How Much Will the API Labs Cost?
Nothing, without keys. With keys, each API lab states its estimated cost for one full run, and prints the measured cost of your run from the token counts each response reports. The estimates are collected on the readiness page; they run from under 5 cents to under 1 USD per lab for one person, and under 2 USD per pair for the capstone on Claude.
What Are RLCD and Jev?
Jev is a decision model from TypeSafe AI: it takes typed questions and returns typed answers with probabilities, instead of generating text. TypeSafe’s documentation (read 2026-10-06) says Jev “is trained with RLCD to return calibrated decisions”, where RLCD is reinforcement learning for calibrated decisions, and that its models’ “probabilities are optimized against outcomes to reflect uncertainty”. Module 12 lists TypeSafe’s statements with their sources, separately from what third parties report.
TypeSafe has published RLCD’s name and aim, but not the method: no reward function, no algorithm, no paper and no measured calibration for Jev. Day 4 teaches calibration from the published literature, separates what TypeSafe has stated from what third parties report, and includes a small training experiment that is our own illustration of the idea, not TypeSafe’s method.
Can I Attend Only Some of the Days?
Each day builds on the one before, but the days fall into two units. Days 1 and 2 cover how the models work, from counting words to transformers, pretraining and fine-tuning. Days 3 to 5 cover how the models are used through APIs, what they are trained to want, when their answers can be trusted, and how to build systems from them. If you join on Day 3, you should already know what a transformer is and how a pretrained model is fine-tuned, which Modules 5 to 7 teach. Each notebook loads its own data, with the exceptions listed on the notebooks page.
I Found a Mistake. How Do I Report It?
Open an issue or a pull request on GitHub.