Field notes
Build a workflow around the model
Turn an impressive first draft into a repeatable production process.
Rari’s essay treats video creation as a system around the model. This guide develops an original review process around that idea: make inputs inspectable, review the story before the render and keep the evidence needed for the next revision. The Actova source package provides a concrete example of production artifacts.
What to know before you begin
What to take from the essay
In Motion Engineering: Build a Video Studio Around Opus 5.5, rari argues for a production system around the model. The essay connects the brief, inspectable references, story beats, rendering, sound and review. Read the original for the author’s complete explanation.
Our practical review sheet
Before production: can you point to the exact asset behind every product claim? Before animation: does each still frame communicate one idea? Before delivery: can a new viewer understand the story without your explanation? Record the answer and the next change, not just a score.
Keep a reusable package
Our suggested handoff contains the brief, asset manifest, source project, render settings and final exports. Keep a short revision log with timecodes. The next film should reuse the verified typography and export setup while getting its own story.
THE COMPLETE WALKTHROUGH
From input to delivery, step by step
01Make the brief a decision document
List the audience, the one promised outcome, the placement and the evidence for each claim. Add exclusions: what the film will not attempt to explain. A useful brief prevents the next prompt from expanding the project every time a new idea appears.
02Translate references into decisions
For each reference, name the feature you want to study: type scale, pacing, framing or a transition. Separate that from the creator’s identity, footage and product claims. Give the agent inspectable examples and ask it to explain the proposed design choices before building.
03Keep review artifacts small and useful
A still answers whether the composition works. A short clip answers whether the motion works. A contact sheet exposes repetition across the film. The encoded file proves the delivery. Use each artifact for the question it can answer instead of asking one long preview to prove everything.
04Write notes that can be acted on
Replace “the scene is weak” with the frame, symptom and desired change. For example: at the second product reveal, the screenshot is unreadable; crop to the active panel and hold it longer. Keep successful elements named so the next revision preserves them.
05Treat variations as separate deliveries
A new aspect ratio, language or product can change line length, emphasis and timing. Review each version rather than assuming a template guarantees quality. Save the shared design rules, then document the deliberate deviations for each output.
Five production gates
Use this editorial plan as an editable working document, adapting it to the actual assets and placement.
| Gate | Review artifact | Pass condition |
|---|---|---|
| Brief | Audience, promise, source assets | One clear message |
| Design | Three representative stills | Readable visual hierarchy |
| Motion | One short clip | Timing supports the message |
| Film | Contact sheet and full playback | No redundant scenes |
| Delivery | Encoded files in every format | Files and source are usable |
A complete request to adapt
This is an original example for this tutorial. Replace the placeholders with your task and retain the preparation, review and delivery requirements. Ask the agent to identify missing inputs before production.
Act as a production reviewer for this video project. Inspect the brief, assets, storyboard and current export. For each issue, give the scene or timestamp, visible symptom, proposed change and what to preserve. Separate factual errors, readability problems and optional taste changes. Review stills first, then a short motion test, then the full encoded file. Keep a revision log with decisions and remaining issues.Where the process can get stuck
How many review rounds are enough?
Use acceptance criteria, not a fixed number. Stop when the facts, readability, output and intended message pass. More rounds without a named problem can dilute a coherent design.
Can the model review itself?
It can surface useful issues, especially when given frames and explicit criteria. A human still needs to verify the message, evidence and final experience. Save the reviewer’s observations, not just a numeric score.
What should become a reusable skill?
Keep stable procedures: asset intake, file structure, review steps and export checks. Treat project-specific copy and branding as inputs. A useful skill preserves decisions while allowing a different story.
APPLY IT TO YOUR PROJECT
Finish one small, reviewable output
Walk through the process with your own inputs. Save the first output and specific review notes: what works, what needs changing and how to reproduce it. Once the small test passes, extend the duration, complexity and delivery variants.
References & editorial notes
Consult the original projects for current capabilities, eligibility and setup. Exercises, timings, sample requests and review advice are Hermes editorial work. Creator outputs and teaching illustrations are labeled where shown.