A product launch video, built from the real site.
A launch film in this engine is not written from a description of the product. It is built from CAPTURE: the real UI, the real logo, the real palette, carried into motion. The taste already exists on the site; the film's job is to reflect it, never redesign it.
The route: market a real product, from a URL.
The engine's own routing table sends a request to "market or show a real product, company or site from a URL" to the brand-launch template, ahead of an explainer, a UI morph or a music video. Only a reference rebuild, where a film must match an existing video, ranks above it.
guides/ROUTING.md, row 2One message per beat, 15 to 40 seconds.
The beat list comes first, each beat with a timestamp, one message and the real capture that proves it. The hook is the promise, under 12 words on the first frame. Then one move per beat: the hook word becomes the product, a cursor does one real thing, the key output lands big, then a second surface, a stat you can source, and the wordmark. Under 15 seconds, a launch film is one continuous action instead.
prompts/brand-launch-from-url.mdThe moves a launch film is built from.
A click doing its job, a zoom to one part of the UI, a number proved, the product handed to the brand. Open a move for its snippet and notes.
What a launch film may not invent.
Every screen in the film is a capture of the real site or app, cropped, never a placeholder card. The palette, fonts and favicon come from a kit read off the site itself, and nothing else is used. A feature you did not see on the site is a feature the film must not show, so crawl past the homepage: the feature worth showing is often one click past the hero.
prompts/brand-launch-from-url.md · scripts/brand/kit.mjsStart from the launch template.
bin/vawe new starts from the brand-launch template unless you name another: a starter page and a brief whose questions each carry a default.