Acquires and verifies speech, music, effects, and ambience for this production. Use when sourcing or generating audio, arranging dialogue, or checking the finished soundtrack.
Maps the development checklists, common, design, implementation, assets, motion, shots and testing, onto the source declarations and tests that answer them in their doc comments. Use before writing or citing a development contract item.
Holds the checklists Evidence asks, in two families: development for source and tests, and story for research through the screenplay. Use before selecting, answering or citing a contract item.
Maps the story checklists, from performance research and settings through treatments, scripts and the final screenplay to naturalness, discovery and review, onto their unit and population respondents. Use before selecting, answering or citing a story contract…
Implements and tests production source, integrations, dependencies and commands. Use for code or host changes and behavioral tests; documentation owns technical writing and story owns creative bodies.
Owns production requirements, evidence answers and graph configuration. Use to adopt a requirement, configure what the graph selects, or write and audit source evidence; story owns creative answers.
Programs deterministic scene performance, staging, timing, and physical responses. Use when authoring or changing animated behavior, assembling a motion hint, or upgrading a moving instance's representation.
Keeps the project's scope and setup and carries the work after motion, conditioning, video generation, editing, encoding and handoff, to the delivered artifact. Use for project context, sustained runs, media, instruction sync and finishing; story,…