11.2a — Create PT: Video + PPR

Video rules (read twice, then rehearse once more):

• Under 60 continuous seconds and under 30 MB, one take (edits are forbidden — one unbroken recording). Lower the capture resolution if you are over the size, do not shorten the demo.
• Must show: input happening, program behavior, output — your 11.1d demo path
• Voiceover or on-screen text explaining purpose; your face is optional, your program is not
• No names of classmates or school (privacy rule)

Recording ritual: stopwatch rehearsal → recording one → watch it → one fix if needed → recording two, done. Retaking forever is a trap; your demo path is already rehearsed. Save as MP4 and back it up in TWO places (repo folder + cloud).

The PPR (the exam-day cheat sheet you write yourself): four code segments, each in its own box (a box holds up to three screen captures, so long code is fine — capture it in order):

1. Your procedure — the name, the parameter(s) and how you use them, and the algorithm body with your three S/S/I parts visible
2. The call to that procedure (the real call site)
3. How data is stored in your list, and what the list is called (do not show an empty list being created)
4. Where that same list is used toward your program's purpose

No comments in any captured code — the Portfolio rejects the PPR for it, and a rejected PPR is a rejected section. Use 10-point font or larger, and capture at 100% zoom: if the reader has to expand a capture to read it, it does not count.

That PPR is open in Bluebook beside you for the whole written-response section on May 14 — you are not recalling line numbers, you are reading them off the screen in front of you. All four responses come from it; WR2a/2b/2c point directly into it, and WR1 draws on the purpose and outputs it anchors. Screenshot the exact lines, not from memory.