Phase 11: Capstone: The AI-Native Product Engineer · 50 min · Claude Code · Python

Capstone Assembly: Reviewing the Full Arc

Months into a course-long product, the spec you wrote in Orbit 1 and the code you shipped in Orbit 3 have both kept moving — the only way to know if they still agree is to actually check, not assume.

Hiring signal: Producing an honest, gap-inclusive architecture review of your own system — rather than a polished summary that hides what's incomplete — demonstrates exactly the self-audit discipline this course has taught for specs, teams, and postings, now turned on your own capstone product.

What you will learn

Review a course-long product across all three orbits (spec, production hardening, platform/team) rather than assuming earlier work still holds
Identify concrete drift between what a spec describes and what the actual system does, months after the spec was written
Triage gaps by real risk and priority rather than treating every incomplete piece as equally urgent
Produce a comprehensive architecture document that honestly documents gaps rather than hiding them

Introduction

Capstone Assembly: Reviewing the Full Arc

A learner reaches the end of Orbit 3, confident their course-long product is finished — the spec was written carefully back in Phase 1, the harness and quality gates went in during Phase 4 and 6, the multi-agent platform work landed in Phase 8. Opening the spec directory for the first time in weeks, they find it still describes a single-agent version of the product; the multi-agent orchestration built in Orbit 3 was never captured there. Meanwhile the harness config references a tool that was renamed two phases ago and no longer exists. Nothing is broken exactly — the system still runs — but the spec, the harness, and the actual code have quietly drifted apart from each other over months of continuous building, and nobody noticed because nobody looked at all three together since Orbit 1.

Why a full-arc review is necessary, not optional, at course end

This course has taught spec-code drift detection (c12-01, c12-06), harness regression checking (c12-04), and context-audit discipline (c12-09-4) as ongoing team practices — but a solo learner building across twelve phases over months is exactly as susceptible to the same silent divergence a team is, just with "past-you" standing in for "the other engineer." The capstone review isn't a formality before the final project; it's the same audit discipline this course has taught throughout, applied to your own accumulated work instead of someone else's, and it's the only way to know whether what Orbit 1 promised is actually what Orbit 3 delivered.

Unlock the full lesson

You've read the first 2 sections. The rest of this lesson covers Reviewing all three orbits against each other, not just individually, Triaging gaps instead of treating them all as equally urgent, What the architecture document actually needs to contain, Build It — plus a hands-on lab, quiz, and project artifact.

Create a free account to unlock Phase 0 and Phase 1 of every course — no credit card.