CreatorMotion · Hub Routing

Prepare concise inputs, hub and outputs. At most five inputs and four outputs are shown. Explain what the intermediary actually does and how the outputs relate to it; labels and connections are supplied structure, not discovered relationships.

Set reverseOrder to choose the presentation order. False brings the input side forward first; true introduces outputs earlier. The input list stays on the left and outputs on the right, and path geometry still runs through the same hub. The flag changes timing rather than exchanging roles.

Reuse the supplied hub-image and output-N rasters or replace named slots through --images MAP.json, using paths relative to that map. For an optional presenter, set presenter true and supply --media RECORDING.mp4; both are required. Bring footage covering the 6.4-second visible interval and inspect the strong crop/zoom in the corner. No matte is used by this implementation.

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. Check every curve, active image key and endpoint label in the MP4. Review the presenter’s crop as well as the uncropped source, and keep supporting text at least 24 px. Preserve the intermediary’s outgoing relationships rather than reducing the shot to a single destination.