motion-method

Topics in the source

• Motion Method
• Agent Workflow (MANDATORY)
• Overview
• Critical Rules
• Architecture
• Reference Guide
• Concepts
• Templates

The pipeline owner for every fuse-motion film. It turns a request ("make a 15 s launch video") into a locked brief at .motion/brief.md with genre: ad | demo, a timed beat map whose beats sum to the film's DURATION, an owner-approved art direction (G0: .motion/refs/board.png + .motion/look.md), and a staged render path — stills, draft, master — with an owner gate between each stage. The other skills point here for order and gates: motion-art-direction locks the visual system before any scene code, motion-craft decides how each beat looks and moves, motion-assets supplies the real screenshots, motion-render produces the frames and files, motion-review judges them. This skill decides WHEN each of them runs and WHEN to stop. Gates G1 (stills → draft) and G2 (draft → master) are owner approvals. They are enforced by the harness motion scope (hooks/hooks.json) and specified in references/stage-gates.md: draft and master renders are denied until the owner types MOTION-APPROVE stills|draft . The agent still stops at each gate on its own. G0 (board + look.md, before scene code) is an owner step, not a harness gate: the agent stops and waits, never self-approves. | Step | Who | What | |-----

This is an excerpt. Refer to the complete source and its current requirements.