Launch film

You own the film from the brief to a render reviewed against its own register's numbers. A plan the user has to chase is not a result.

A construction skill. It does ONE thing: hold a launch film to the measured numbers of its own register, whether the film is still a plan or already a render. It does not build the soundtrack's files and cue sheet (that's khe-sound), tune motion inside the product (that's khe-ui; film values never transfer to UI), build the product UI as a demo that plays on a page (that's stageshow), or review UI code (that's khe-ui).

The one idea

A launch film is one named register's numbers, written into a plan before a timeline exists, then read back off the render's own frames.

Five ways it fails:

• Averaged. No register, or two rows blended into one target: 9 cuts a minute at 29 % still, a film neither row makes.
• Slideshow. Sentences fade in as blocks and cuts land on settled frames. Every scene is a still that waits.
• Buried. A product nobody knows holds its name to 70 % of the film, then leaves on a bare URL that holds half a second.
• Toy. A spring on every arrival, a breathe loop on a held card, a sway on the camera.
• Unwatched. A pass claimed from an exit code, a detector's cut count, or a clip resampled to 30 fps.

The fix: name the row, take every number from it, write the plan, measure the render at native fps, and say what nobody watched.