I built a Rive-ready scenario plan for a placeholder car animation, with a browser mock that drives it. A 384-frame, 16 s source at 24 fps is planned as 9 named timelines that tile it with 0 gaps and 0 overlaps. All 12 transitions are measured from the car's own path: 9 join with no jump in position or heading, and 3 restarts are declared 12-frame cross-fades. A breadth-first pass proves all 3 outcomes reachable over 5 routes with 0 dead ends, and a 7-input by 9-timeline validity matrix and 3 host events are exported as one contract for app and web. In the mock a drawn car drives the same graph: it holds at each decision, branches on the inputs, skids when the rain input is on, cross-fades on every restart and reports each event as it plays; an auto tour drives all 5 routes, and one full drive is rendered to an 18.8 s MP4. No Rive file is included: the Rive file is built in the Rive editor from the client's MP4, to these same names.