Lecture deck

One claim per screen, one picture that shows the mechanism, one caption, and everything else in the notes. The deck is built from Python screen modules against a theme, rendered to PNG for checking, and checked for register before it leaves.

When you get a request

1. Ask for or infer the room: who, how many, where, how long, what they already know, who speaks and who runs the room. If a run of show exists (a host's timings), take it as given.
2. Write storyboard.md first, using reference/storyboard-template.md. Goal, argument as numbered claims, run of show with modes, then one entry per screen with its picture and its bridge. Read the headers alone as an argument; then the bridges alone. Fix order here.
3. For anything over ten screens, critique the storyboard before building (flow, audience level, whether each picture explains its claim, coverage of the brief). Fold the changes in.
4. Scaffold and build the screens (reference/workflow.md, reference/kit-api.md). For a long deck split screens into modules and build them in parallel.
5. Render every screen and look at every contact sheet. Fix overflow, clipping, unreadable text, pictures that decorate instead of explain.
6. Run the register check with --dump and read the text flat. Fix, re-render what changed, repeat until clean.
7. Deliver the HTML, name what is placeholder (dates, names, a platform that may not be ready), and say how to present it (arrows, N, O, B, F, Print).

The rules that make it good