Prepare a reproducible motion production handoff

Use manifest fields for project name, source revision, entry point, tool/runtime versions, asset filenames, asset hashes where available, font files and weights, audio files, frame rate, duration, dimensions and output destination. Include the approved copy and any data source versions as separate inputs.

An illustrative entry might read “Study: three-space route; source: recorded revision; duration: 30 seconds; rate: 30 frames per second; output: specified MP4 file.” Replace “recorded revision” with the real identifier before delivery. Placeholder values are useful in a template but cannot serve as evidence of reproducibility.

Record whether timing is frame-based or time-based, how scenes meet at their boundaries and whether the final endpoint is included. If procedural motion uses randomness, record a fixed seed or the method that makes output repeatable. List external inputs that could change, such as remote assets or live data.

Copy required assets into the approved package when permissions and the workflow allow it, or provide stable authorized retrieval instructions. Do not rely on a producer’s local font installation or an undocumented browser cache. A successful render on one machine is not sufficient information for another producer to reproduce it.

Write ordered checks: confirm inputs, run the documented render command or supported workflow, inspect output metadata, decode named reference frames, compare approved text and values, play the full file with sound, then inspect known risk intervals. Record expected observations rather than vague instructions to “check quality.”

For the illustrative route study, reference checks could include the marker entering each space from the left, all three labels on the final map and no visual jump at the scene joins. Those are proposed criteria. Actual pass records must identify the inspected artifact and reviewer, not simply repeat the criteria.

Package the approved reference, final output, manifest, verification notes and open issues together. State which versions were actually checked. If captions or a restrained-motion variant remain pending, list them explicitly rather than letting a general approval imply that every deliverable exists.

Ask the receiving producer to perform a small reconstruction test using the documented inputs. Record any missing dependency and update the manifest. When a later revision changes an asset or font, update its identifier and rerun affected checks. The goal is a traceable relationship between source, output and evidence, not an archive full of files whose roles are unclear.