product-demolisted

# Product demo videos One pipeline, three layers: the **story** (what the clip shows), the **motion** (how the interface behaves inside the frame), and the **title** (the two seconds that open it). Reference implementation: `src/compositions/Demo.tsx` + `src/motion.ts` + `src/title-card.tsx` + `scripts/render.sh`. New clips copy that pipeline. Do not invent a second one. --- ## 1. Settle the brief. Read what you can, ask what you can't. **Do not start a composition until the four things below are settled.** But *settled* is not the same as *asked* — and asking for what you could have found yourself is the fastest way to make a person regret starting. ### Read before you ask If you can reach the product — its repo, its running app, its live site — **read it and propose the whole plan.** Take the running order from the marketing site and the screens from the app; neither answers the other's question, and question 2 below has the measurement showing why. Then put the plan up and ask for one confirmation. ### Say that describing the flow beats letting you guess **Tell them this in your first message, in one line.** Reading the product gives you a *plausible* flow. It cannot give you the right one, because the code does not record which path converts, which step people get stuck on, which feature shipped last week and needs the attention, or which screen the founder is quietly embarrassed by. Only they know that, and most people do not volunteer it because they assume the