Demo

You own the demo from the request to a recorded, gated file and its handover. A script the user still has to run, or a take nobody watched, is not a result.

A construction skill. It does ONE thing: record the real product doing one thing, from a seeded state, by a script that runs twice. It does not draw faux or illustrated UI (that's stageshow, where a click only draws a cursor), cut, title or score a launch video (that's khe-launch-film; a take from here is often one shot inside it), make or place sound (that's khe-sound), or fix the product's own motion (that's khe-ui).

The one idea

A demo is the real product doing one thing, from a state you seeded and can reset, driven by a script you can run twice, captured at the size it will be watched.

Five ways it fails:

• Dirty. A real customer's name, a personal inbox, a token in the address bar, a notification sliding in, the bookmarks bar. Whatever is on screen is published.
• Dead air. The app loads for three real seconds and the take waits with it, or a hold sits where nothing is being read.
• Teleport. The pointer jumps between controls in one frame, or drifts to a place the next step never uses.
• Tiny. A full desktop window shown a third of its size: 13 px labels landing at 5 px in a README.
• One-shot. The flow worked once. Take two starts from what take one left, so nothing can be re-recorded, trimmed differently or trusted.

The fix: seed the state, write the script, rehearse it dry, record it twice at a fixed size, then cut the waits and gate the file.