CreatorMotion · Pipeline to Output Fan

Prepare concise inputs and a nonempty outputs list. The implementation displays at most three inputs and five outputs; extra entries are ignored. Use a chain that accurately describes the sequence you want to explain, rather than treating the arrows as proof of a real process.

Reuse the bundled source-N rasters or replace each active slot through --images MAP.json. Relative paths resolve beside the map and unnamed defaults remain. Source paper objects require their images; there is no blank substitute. Match material to the labels and follow the image policy.

Keep output names short enough for their shared lower row. Output glyphs follow array position rather than being selected from the label meaning. No presenter or matte is used. If changing source count, inspect the fixed source positions and the common fan-out origin rather than assuming the whole scene automatically recenters.

From the extracted package, prepare Node.js 22+, FFmpeg and HyperFrames CLI 0.8.30. Run node scripts/create.mjs --out PROJECT --data CONTENT.json --style white-yellow, substituting another documented palette if wanted. Read the motion specification and image policy before adapting the scene; use semantic --overrides for deliberate style changes.

Inspect the editable project at entry, each motion handoff and final hold, then render with the command printed by the generator. Check the resulting frames for text collisions, correct numbers and readable contrast. Keep at least 1.2 seconds for the final reading when editing, and compare all four palettes with identical content after structural changes. Narration, music and assembly into a longer film remain separate work. Inspect the chain before, during and after compaction, then check every output route and label in actual MP4 frames. Keep supporting text at least 24 px on the documented canvas. Preserve the group transformation: replacing it with unrelated cards would lose the connection between source chain and outputs.