11.1e — Create PT: Build Day 4 + List Check
Last build day before the writing/recording days (11.2a). Today: freeze, audit, and the ritual this whole year trained you for — the requirements checklist, done out loud, with witnesses. A PT that passes the audit twice cannot be surprised on submission day.
The audit ritual — partner swap, read-aloud verification. One of you points, one of you checks the rubric language:
| Requirement | Evidence, on screen or in code | Pass? |
|---|---|---|
| List participating in program function | Where is it added to, removed from, or traversed — IN the behavior path? | ☐ |
| Procedure with ≥1 parameter | Name it, show the signature, show the call passing values | ☐ |
| Algorithm: sequencing + selection + iteration | Point at one line for each of the three | ☐ |
| The CALL | Where does a call trigger the algorithm from the program's actual behavior? | ☐ |
| Input → behavior → output | Trace one user input to one visible output | ☐ |
| Video plan under 60s | Rehearse with a stopwatch: demo path intact? | ☐ |
Partner's signature on your CPT_PLAN.md, and yours on theirs. This is 8.6's review ritual, aimed at College Board instead of your teacher.
Freeze means freeze. After today: no new features, no refactors, no "small improvements." Every change after this point risks the demo path — and your WR answers must describe the FINAL code, not the aspirational one.
WR installments (draft all five installments in CPT_PLAN.md — prompts here):
- WR1: the program's purpose, plus one specific example output and how it shows what the program does. Name the actual text or number your program produces — "it works" scores nothing.
- WR2a: the algorithm, explained (your 11.1c paragraph)
- WR2b: the development story — describe ONE difficulty you faced and the fix. TODAY's bug-hunt findings ARE this answer: write one down while you still remember the debugging session.
- WR2c: BOTH halves of the row — the list (what it stores, how the program uses it) and the procedure with its parameter, arguing how it manages complexity (your palette class, the UnityEvents, the singleton...).
- The video script: the demo path as a numbered shot list.
Socratic: Freeze, Audit, and What You Cut
- You read the requirements out loud with witnesses. Which requirement was hardest to point at in your own code, and why was that one hard?
- Freezing means something you wanted to build does not get built. What did you cut, and what would it have cost you to keep it?
- The audit passed twice. What would a third person, who had never seen your program, fail to find?
Checkpoint — before moving on, you must be able to:
- Pass the six-row audit with a partner's signature
- Explain every requirement by pointing at your own code
- Show all four WR drafts (plus the video script) in the plan file
- Resist new features until submission (the freeze discipline)
Reference Docs
Need a deeper explanation? These pages cover the same concepts:
- Create PT guide — the audit rows explained
- Written Responses — the four prompts
Saved on this device only — the Dashboard tracks your progress.