CreatorMotion · Quadrant Positioning

Define horizontal as [leftMeaning,rightMeaning] and vertical as [bottomMeaning,topMeaning]. Prepare up to six labeled items with numeric x/y positions, using the normalized zero-to-one range illustrated by the package. Keep the same definitions when comparing versions of a map.

Choose positions from an explicit rationale and distinguish measured data from subjective judgement. The code applies the supplied coordinates directly without clamping or classification. Do not change positions merely to improve label spacing or make an option look stronger.

Keep labels short and inspect the full object footprint near axes and plot edges. The drawn horizontal divider is not at y=0.5 under the current coordinate mapping, so do not assume the visible cross is an exact half-scale threshold. No presenter, raster image or matte is needed.

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 label and coordinate placement in actual MP4 frames. Inspect overlaps and glyph meanings, since icons follow input order rather than item semantics. Keep supporting text at least 24 px and preserve separate axis/label/item reading beats. Explain quantitative thresholds separately if the application requires them.