This chapter gives a working overview of Your Terminal Deliverable: The Post-Build Document, focusing on the ideas a reader needs before moving to the next chapter. The chapter moves through Learning outcomes, Opening, What the post-build document is, The five sections, walked through, and related ideas. Read it for the main argument, the vocabulary it introduces, and the practical judgment it asks you to develop. Three builds. A three-tier CLAUDE.md. The simulation running in your classroom.

The simulation had run in front of three classes by the end of the week. The first class found two failures , the missing first-interaction affordance and the touch-event handling on Chromebooks. The teacher caught both with the revision-build cycle from Chapter 12; the Generation Log in PROJECT.md Layer 2 had three new entries by Friday. By Friday afternoon, the simulation was reliable. The CLAUDE.md across all three builds had grown to 220 lines (over the 200-line guideline; the teacher made a note to prune in summer).

The post-build document is the artifact that converts the experience of the build into the capacity for the next build. The build produced a working simulation. The PROJECT.md Generation Log captured the operational lessons. CLAUDE.md absorbed the entries that should persist. The post-build document captures something different: the meta-lessons , what the build taught you about how you build. The five sections are designed to surface five kinds of knowing that emerged from the build:

One paragraph. Plain language. The kind of description you would give to a colleague who asked what you spent the last three months on. I built an interactive visualization of bubble sort for my ninth-grade CS class. Students step through the sort one comparison at a time; the simulation highlights what is being compared, what is being moved, and the growing sorted region.

Future you, at the next build. You will start the next simulation , for a different concept, a different class, a different semester. You will open the post-build document before you open the new build's blank PROJECT.md. The what I would do differently section will become the first three lines of the new build's architecture. The what I learned section will inform the new build's specifications. The document compounds. Yourself, today, as honest assessment.

This is the chapter's last apply-level exercise. The book's last exercise. Tonight. Thirty minutes. Five paragraphs. Save next to your CLAUDE.md.

A working class website built in Act One; deployed weekly. A working grading tool built in Act Two with Skills, Hooks, Subagents, the narrowing principle. A working interactive simulation built in Act Three with the three-file system; deployed in your classroom. A three-tier CLAUDE.md. Spanning all three builds. Lessons Learned section with the year's most valuable operational knowledge. A DESIGN.md and a PROJECT.md for the simulation (the second and third files of the Brutalist three-file system). A post-build document. Five sections. One page. Honest.

The book ends here. The practice continues. The next simulation. A different concept, a different unit, a different class. The framework will be faster the second time , most of CLAUDE.md is reusable; DESIGN.md is reusable or one-edit-away; the three-file process is reflex. The second simulation will take 30, 45 percent of the time the first one took.

"Post-build documents are bureaucratic." Five paragraphs. One page. Thirty minutes. The discipline is honest, not exhaustive. "I will write it when I have time." Tonight. Memory degrades fast. The document written now is the document that captures the lessons; the document written in two weeks is the document that captures your reconstructed best-guess at the lessons.

(Create) Write your post-build document for the simulation you built across Chapters 10, 12. Five sections. One page. Save as post-build-simulation-1.md next to your CLAUDE.md. (Evaluate) Read your What I would do differently section aloud. Is the reversal specific (you can name the decision and the alternative), or general (you would "improve" something)? If general, rewrite for specificity.

bell hooks (1952, 2021) , American scholar and educator whose Teaching to Transgress: Education as the Practice of Freedom (1994) argued that the teacher is a practitioner who learns alongside the student, and that the most important pedagogical artifact a teacher produces is the record of their own continuous learning, made visible to the students they teach. hooks's argument was against the teacher-as-finished-authority model , the teacher who has mastered the subject and now delivers it.

bell hooks (1952, 2021) , American scholar and educator whose Teaching to Transgress: Education as the Practice of Freedom (1994) argued that the teacher is a practitioner who learns alongside the student, and that the most important pedagogical artifact a teacher produces is the record of their own continuous learning, made visible to the students they teach. hooks's argument was against the teacher-as-finished-authority model , the teacher who has mastered the subject and now delivers it.