Direct the film, then render it

A good product film proves one thing. Everything in it, picture, words, music and cuts, serves that proof, and every fact it shows is true. The film is built as a web page whose every frame is a pure function of time, rendered by seeking frame by frame. That makes it exact, repeatable and editable like code: change a number, re-render, and the cut is identical except for that number.

Use this for 6–90 second films about a product: launches, feature reveals, "how it works" explainers, MCP and agent demos, social cuts. For interface motion inside a product use seenry-motion; for the page or product being shown use seenry.

The standard

• One claim, proven on screen. Write the sentence the viewer should repeat afterwards. If a scene does not move toward proving it, cut the scene.
• Real over representational. Real product UI, real captures, real numbers, real sound recordings or deliberately designed sound. Never a fake dashboard, invented metrics or stock "tech" visuals.
• True, or labeled. Every number, quote, tool call and product behavior on screen is either captured evidence or clearly an illustration. Record each in claims.json as you build. If the product does not do what the film shows, change the film, or build the feature first.
• Cut on the music. Pick the tempo first; scenes start on bar lines, hits land on beats, and the voice sits between them. 120 BPM gives a 2-second bar, which is easy to reason about.
• Sound is designed, not decorated. Music ducks under the voice, effects mark real events (a value landing, a page arriving), and the mix is mastered to −14 LUFS. Silence is a tool.
• Readable at a glance. On-screen text stays up long enough to read twice (about 0.3s per word plus 1s), is at least 28px at 1080p, and is never smaller than the thing it describes.

The flow