motion-craftlisted

# Motion craft There is no shortage of instruction on how to animate a thing. What is usually missing is the step before it: deciding what the thing *is*, and making it. The chain runs in one direction and most pages break at the same link: ``` beat → what it must show → what asset that needs → how that gets made → how it is wired ``` Steps one and two come from `story-direction`. Step five is ordinary engineering. **Step four is where pages go generic.** An agent that knows fifty scroll techniques and has no way to make anything worth scrolling through will reach for what it can draw in markup — a diagram, a hairline grid, a spec table — and call the restraint deliberate. Three consecutive runs on the same project did exactly that, each one arriving at dark ground, a display serif with one italic accent word, and no imagery, while a fully installed generator sat unused on `PATH`. Restraint is a choice you make *after* you know what the alternative would have looked like. Before that it is just the default with better manners. ## Motion has to beat its own fallback Every moving thing on a page has a still version: the frame it would show if the motion never loaded. Ask what that still costs you. If the beat still lands without the movement, the movement is decoration and the still is the design. This is not a purist position, it is what shipping pages actually do. Apple's product pages give every scroll-driven video a **three-second load timeout** and a static