Skip to main content

Interactive Labs

Explore the trade-offs behind an ML system. Follow a continuing project, predict what a design choice will change, and use the evidence to explain your recommendation.

Start with your volume

Every volume begins with Lab 00. Choose or restore your project, try the notebook, and see how the chapter labs build toward a final discussion. No previous saved progress is required.

Volume I

Onboarding + 16 chapter labs

Start Lab 00

Explore the Volume I route
  1. 00 Welcome to your deployment project

    Choose a deployment project and practice predicting, comparing, and saving your work.

  2. 01 The system runs. Is it useful?

    Choose the next data, algorithm, or machine intervention using separate evidence of behavior and execution.

  3. 02 Where should the work live?

    Defend a conditional placement or an explicit hold by screening locality, capacity, operation, and partition obligations.

  4. 03 A late requirement makes earlier work conditional

    Trace a requirement through the lifecycle and plan a justified repair, retest, and return path.

  5. 04 Make the evidence trustworthy and deliverable

    Create a versioned data contract that supports independent evaluation and a functioning input path.

  6. 05 Open the model and inspect its state

    Explain how topology, gradient dependencies, phase, and batching change work, movement, and live state.

  7. 06 Choose structure for the task, not the label

    Choose a task-supported architecture while explaining its information assumptions and dominant resource regime.

  8. 07 Make the graph executable

    Choose an execution plan whose visibility, setup costs, backward state, and target support match the work.

  9. 08 Train to a target, not to a busy GPU

    Choose or reject a training recipe using state fit, effective batch, numerical progress, and a cause-specific bottleneck diagnosis.

  10. 09 Make fewer examples earn their cost

    Choose a selected pool or retain the full pool using learning value, coverage, complete preparation cost, and realized delivery.

  11. 10 The checkpoint is not the deployed artifact

    Choose a supported deployment artifact on a quality/resource frontier, or hold conversion when evidence is missing.

  12. 11 A faster kernel must survive the whole path

    Choose a legal mapping and resource intervention with counted traffic and an explained application-level consequence.

  13. 12 Earn the right to make a performance claim

    Decide which performance and behavioral claims are supported, contradicted, or still unresolved.

  14. 13 Serve useful work when demand arrives

    Choose a serving policy with an explicit demand envelope, waiting behavior, state fit, and lost-service accounting.

  15. 14 An update breaks the contract without crashing

    Create an evidence-based incident response with replayable lineage, feasible rollout, and tested recovery.

  16. 15 Useful for whom, under which obligations?

    Recommend release, restricted use, baseline retention, mitigation, or hold using justified obligations and observed consequences.

  17. 16 Defend one coherent deployment decision

    Integrate earlier concepts into a release, restriction, baseline, fallback, or hold decision without inventing a new score.

Volume II

Onboarding + 17 chapter labs

Start Lab 00

Explore the Volume II route
  1. 00 Choose a fleet project

    Choose a fleet track and rehearse prediction, immediate feedback, saved comparisons, and explicit saving before technical investigations.

  2. 01 Introduction

    Defend when fleet coupling is necessary and how scaling, failures, and partitions change useful work.

  3. 02 Compute Infrastructure

    Select a workload-matched accelerator, node, and rack envelope that passes capacity, movement, facility, and ownership-cost constraints.

  4. 03 Network Fabrics

    Choose a fleet fabric by matching message size, shared cuts, isolation, and failure evidence to the traffic contract.

  5. 04 Data Storage

    Place and package data so the complete input path feeds the fleet and checkpoint publication preserves restorable state.

  6. 05 Collective Communication

    Choose a semantically correct collective and compare its topology, overlap, and compression costs at a fixed useful-work target.

  7. 06 Distributed Training

    Defend a parallel training plan against memory, communication, pipeline, and time-to-target limits.

  8. 07 Preserve valid work when failures become routine

    Preserve valid work when failures become routine

  9. 08 Allocate useful fleet progress under competing claims

    Allocate useful fleet progress under competing claims

  10. 09 Recover useful progress from a busy fleet

    Recover useful progress from a busy fleet

  11. 10 Serve acceptable requests on time at a sustainable cost

    Serve acceptable requests on time at a sustainable cost

  12. 11 Decide whether and how a heterogeneous fleet should learn

    Decide whether and how a heterogeneous fleet should learn

  13. 12 Operate and change a coupled model portfolio

    Operate and change a coupled model portfolio

  14. 13 Security and Privacy

    Choose controls for an explicit fleet adversary, compare privacy and runtime costs, and bound a release claim with lifecycle evidence.

  15. 14 Robust AI

    Diagnose silent failure, bound defense and fallback decisions, replay layered poisoning response, and distinguish label coverage from generated-claim evidence.

  16. 15 Sustainable AI

    Compare fleet interventions under explicit useful-work, facility, lifecycle, and demand boundaries.

  17. 16 Responsible AI

    Make an accountable release decision from distinct fairness, observation, capacity, and data-governance evidence.

  18. 17 Fleet Synthesis

    Replay inherited evidence, diagnose a cross-layer failure, compare equal-budget repairs, and defend a bounded fleet decision.

Labs run as full pages in your browser, with the book’s navigation. The first launch downloads the runtime and dependencies and may take a few minutes.

What you will do

  1. Read and predict. Meet the situation, see the learning goals and complete route, and predict a consequence before opening an investigation.
  2. Change and compare. Change one condition and inspect the immediate feedback. Explain what improves, what costs more, and what remains uncertain.
  3. Capture and discuss. Keep contrasting evidence, defend a recommendation or hold, and say what would change your mind. Download the discussion to submit through your course’s usual system.

The book explains concepts, TinyTorch builds the machinery, these labs explore design trade-offs, and StaffML practices defending decisions. Each chapter lab develops its own concepts within your continuing project.

Saving your work

Capturing keeps a comparison fixed while you continue experimenting. Saving a discussion is an explicit action; later changes can make that saved evidence stale. The Design Ledger can retain saved decisions when browser storage is available. Keep a downloaded report for a portable record, especially when storage is unavailable. Storage does not synchronize across devices or submit work to your instructor.

LLM assistance can help with hypotheses and drafting. Your claims still need support from the experiment, including its assumptions and limits. Calculation Notes explain the governing models when you want to dig deeper.

Local notebooks and hardware

Browser labs need no local installation. To modify a notebook or run it locally, install the repository dependencies:

python3 -m pip install -r labs/requirements.txt
python3 -m pip install -e mlsysim
cd labs
marimo run vol1/lab_00_introduction.py

Install dependencies and launch once while connected before relying on offline use.

Back to top