CourseAI System Design: The Complete Course · Module 16: Capstone · part 107 of 107
Part 107 · Module 16: Capstone

Lab: The Northdesk design review, proved in one run

547 min read·
Module 16 · Capstone lab · About 90 minutes · Needs: the labs of Modules 1 to 15 (or nothing: Step 1 rebuilds them). CPU only; a Groq or Gemini key only for the one optional hosted call

What you are building

HOW IT WORKS One repository in, one design out northdesk-platform/ Modules 1 to 15 10 proofs one run, one table DESIGN.md ten steps P-02, P-06 in full README, WHAT_BROKE root pages 135 tests pass with NORTHDESK_BUNDLE set
What this lab builds. The repository the earlier labs left (grey) is proved by ten proofs in one run (blue), and their numbers fill DESIGN.md, two full practice designs and the root pages (green).

It is Monday 15 February 2027, project week 16, and Helen and Gareth review the design today. Fifteen labs left one repository, northdesk-platform/. This lab proves every part of it in one run and hands over one document, DESIGN.md, at the repository root.

The document follows a published practice. Malte Ubl, in "Design Docs at Google" (Industrial Empathy, 6 July 2020), describes the usual sections: context and scope, goals and non-goals, the design with a system-context diagram, alternatives considered, and cross-cutting concerns such as security, privacy and observability. He says design docs "should be sufficiently detailed but short enough to actually be read by busy people", and that the author should re-read one later and ask what was right and what was wrong. DESIGN.md maps his sections onto the ten steps; the ADRs are its alternatives considered.

Nothing in this lab calls a model unless you switch on Step 4's one call. Open a new Colab notebook, module-16-capstone.ipynb, and run each cell in order.

The rest of this course is yours to keep

This course is bought on its own, once, and stays readable afterwards, including the parts added to it later.

Or open everything with a plan