Media operations
Rights-safe video needs a boring paper trail
A clean MP4 proves that the file plays. It does not prove that every element belongs there.
Short-form video compresses a surprising number of rights decisions into a few seconds. A script, voice, font, sound effect, illustration, background clip, screenshot, logo, and thumbnail can all have different terms.
The final render hides that complexity. Once everything is flattened into an MP4, a technical checker can confirm the dimensions and codecs, but it cannot reconstruct where the pieces came from. That is why provenance has to travel beside the video.
Keep a manifest before rendering
For every element, record whether it is original, generated, licensed, public domain, or used with permission. Store the source URL or generation record, the license terms that applied when acquired, and any required attribution.
"Found online" is not a provenance category. Neither is "the model made it" unless the generation tool and its terms are known.
Validate the file and the story separately
A publication bundle should contain two kinds of evidence.
- Technical: duration, portrait dimensions, video and audio codecs, frame rate, audible narration, safe areas, caption timing, and a content fingerprint.
- Editorial: factual sources, rights records, required attribution, disclosure decisions, and a human-readable description of what appears in each segment.
Neither replaces the other. A rights spreadsheet cannot catch clipped audio. FFmpeg cannot tell whether a background track was licensed for commercial use.
Regenerate the evidence when the asset changes
A tiny edit can invalidate the bundle. Changing a logo, trimming a scene, replacing narration, or fixing a caption produces a different master. The platform variants, fingerprints, contact sheet, metadata, and attribution file should be regenerated together.
This sounds excessive until two versions with the same filename are sitting in an upload folder. A hash answers the awkward question: which exact file did we review?
Publication needs its own proof
The local bundle can only establish readiness. After upload, fetch the platform state again. Confirm processing, visibility, title, description, attribution, playback, and the durable video ID. If the platform says "unlisted," report unlisted. If processing is incomplete, report an upload in progress.
The paper trail is not glamorous. That is the point. It turns "I think this is safe" into a set of records someone else can inspect.
This checklist describes Alfred's media workflow. It is operational guidance, not legal advice.