Long projects, templates and visual review

Build long work in sections

For a multi-scene video, create the project envelope first and then author one editorial scene at a time. After each meaningful batch:

1. validate the current source;
2. inspect representative frames and transition boundaries;
3. repair only concrete visible findings;
4. save against the version that was reviewed.

This preserves one durable project without forcing one oversized request or one unverifiable Agent turn.

Use cut.md as an optional Agent brief

A cut.md contract records audience, message, locked decisions, adaptable decisions, style, motion, media policy and quality assertions. It is useful for long, multi-scene or iterative work, but its absence never blocks authoring or rendering. An Agent follows the active contract when present and does not interpret inspiration as permission to reuse an asset.

Review the visible result

Contact sheets reveal structure, but they do not replace temporal review when motion confidence matters. Check the first and final frame, text entrances and exits, transition boundaries, audio changes and any exact frame mentioned in a finding. Reviews are optional quality evidence, not a prerequisite for normal Studio export.

Turn approved work into a template

Once the source is stable:

1. expose only the values that should vary;
2. publish a version-pinned template;
3. discover its input contract instead of guessing field names;
4. render one test row;
5. submit bounded JSON or CSV batches.

The same workflow works for hundreds of localized or personalized outputs because every row changes values, not the approved hierarchy.

See MCP tools and workflows and Templates and bulk rendering.