Verification
Prove the happy path
- Can choose server vs client intentionally
- Can explain layout/page routing
- Can identify where code executes
- Can debug a hydration or environment-boundary mistake
Phase 03 · Lesson 12
Mastery Capstone Lab
Learning contract
What you should be able to do after this
- Explain Mastery Capstone Lab without relying on framework buzzwords.
- Connect the lesson to the phase outcome: Build the Next.js application shell while understanding App Router routing, layouts, Server Components, Client Components, environment boundaries, and rendering behavior.
- Reproduce the relevant behavior and verify it with evidence.
- Diagnose at least one representative failure instead of guessing.
Figure 3.12 — TaskFlow boundary map
Route request
App Router match
layout/page Server Component
optional server fetch
Client Component island
browser interaction
Instructor workflow: predict first → implement the smallest slice → run it → inspect evidence → break one assumption → diagnose → explain it back. Do not copy the whole code block before understanding the first failing boundary.
Mastery Capstone Lab
This is the transfer exercise for Phase 03: Next.js Fundamentals. The detailed lessons are now closed-book reference material. Your task is to prove that the phase outcome can be reproduced from requirements, repository evidence, and debugging—not by copying a finished implementation.
Target artifact A navigable TaskFlow web shell with route groups/layouts, server-first composition, selective client interactivity, and verified environment handling.
Acceptance criteria - Write the behavior and constraints before implementation. - Identify the owning layer and every boundary crossed. - Implement the smallest complete vertical slice. - Verify the happy path from outside the implementation. - Demonstrate at least one expected failure path. - Run the phase-relevant quality checks. - Review the diff for accidental duplication, leaked responsibilities, missing validation/authorization, and hidden environment assumptions.
Evidence packet Save the command/request used, expected result, actual result, one failure reproduction, the fix, and a short explanation of why the final responsibility belongs where it does. This packet is more valuable than a screenshot of a green page because it demonstrates repeatable engineering reasoning.
Stretch Change one requirement after the first implementation. Measure which files must change. If a tiny domain change causes unrelated layers to move, use that evidence to discuss coupling before adding another abstraction.
Executable lesson studio · next
Now turn the explanation into engineering skill.
A guided lesson proves you can follow. A capstone proves you can transfer the model to a requirement with fewer cues.
By the end, you should be able to
- Build the Next.js application shell while understanding App Router routing, layouts, Server Components, Client Components, environment boundaries, and rendering behavior.
- Produce a reproducible evidence packet for success and failure.
- Defend the architecture and identify one improvement without overengineering.
Figure 3.12B — Mental model
Route request
App Router match
layout/page Server Component
optional server fetch
Client Component island
browser interaction
Code-along sequence
One coherent change at a time
- 01
Generate the web app in the monorepo and verify the development server from the correct workspace.
- 02
Create nested routes and a shared layout, then predict which layouts persist across navigation.
- 03
Build one component as a Server Component and identify exactly why it can remain server-only.
- 04
Add one Client Component for interaction and explain what 'use client' changes in the dependency graph.
- 05
Add server-only and public environment values and prove which can reach the browser bundle.
- 06
Use browser DevTools and terminal logs to distinguish server rendering from client execution.
- 07
Run the phase mastery checklist without looking at the provided implementation.
- 08
Perform a short architecture review and document one trade-off you consciously accepted.
txtCapstone evidence packet
Requirement -> implementation diff -> verification -> controlled failure -> diagnosis -> final proofDo not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Break it on purpose
Build debugging memory
- Adding 'use client' too high in the tree
- Accessing browser APIs from Server Components
SymptomInvestigation path
You can only continue by copying the reference
Return to the mental model and acceptance criteria. Rebuild one smaller slice from first principles before reopening the source.
Everything seems to work but proof is weak
Choose an external observer: HTTP client, browser, database query, test runner, health endpoint, or deployment log, and capture deterministic evidence.
Closed-reference challenge
Can you transfer the idea?
Extend the phase artifact with one requirement not used in the guided example while preserving the same ownership rules and verification strategy.
Explain-back
Answer these without reopening the solution
- What did you build without a transcript?
- Which boundary caused the most reasoning effort?
- Which failure gave the strongest evidence?
- What shortcut did you deliberately avoid?
- What would you automate before repeating this in a team?
Lesson studio
Turn the reading into skill
Do it
Use browser DevTools and terminal logs to distinguish server rendering from client execution.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Break it safely
Using effects for work that belongs in server rendering or a data layer
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Explain it back
Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Exit ticket
Before marking complete
Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.