Skip to content

How checkpoints work ​

Every segment ends at a checkpoint: a short, concrete check that you reached the part's end state. Each checkpoint has a matching fallback baseline, a known-good version you can switch to so you start the next part in the right place.

Try it yourself first, then switch ​

The order is always the same:

  1. Try the lab yourself. This is where the learning happens.
  2. Check the checkpoint at the end of the part.
  3. If you're not there, switch to the baseline and continue with everyone else.

You will not fall behind

The baselines exist so a single tricky part never derails your whole day. Switching is normal and expected, not a failure.

Baselines at a glance ​

Every baseline is a file in the baseline/ folder of the workshop repo, on the branch you already have (main). Catching up is one copy command — no branch switching needed.

Getting the repo

If you haven't forked and cloned the workshop repository yet, do that first:

  1. Go to dundermifflin.nl/repo and click Fork (top right on GitHub).
  2. Clone your fork:
bash
git clone https://github.com/<your-github-username>/dm-ws.git
cd dm-ws

All the baseline files listed below are already in the repo, no separate download needed.

PartSegmentFallback baseline file
1Framing & first agentbaseline/01-1-first-agent.py
2Context engineeringbaseline/02-1-context-map.md
3Memorybaseline/03-1-order-memory.py + baseline/03-2-agent-memory.py
4Writing useful specs & personasbaseline/04-1-spec.md
5MCP fundamentalsbaseline/05-1-mcp-design.md
6Build the MCP serverbaseline/06-1-mcp-server.py
7Agent Framework & first MCP-connected agentbaseline/07-1-connected-agent.py
8Native tools & A2A handoffbaseline/08-1-a2a-agent.py
9Human-in-the-loop & condition checkerbaseline/09-1-hitl-agent.py

How to switch ​

Copy the baseline file to the repo root under the working name the segment uses — each segment's Fallback baseline section gives you the exact command. For example, to catch up at the end of Part 6:

powershell
copy baseline\06-1-mcp-server.py mcp_server.py
bash
cp baseline/06-1-mcp-server.py mcp_server.py

Expected output: the file appears in the repo root; run the segment's checkpoint command to confirm you're back on track. Your own work stays untouched — the copy only overwrites the working file the next part builds on.

Still stuck after switching? ​

If the baseline itself doesn't run, it's an environment issue, not your code. Head to Troubleshooting or switch to the observe path in Defaults & paths for the rest of the part.