Video editing · Deliverables

One master in.Every platform out.

Lock the cut, export one master, and hand the rest to an agent. It reads the delivery spec from a note and the client’s safe-zone guide from the Reference card, renders each version with ffmpeg in a terminal card — crops, captions, loudness — ticks them off a checklist and measures every file before it says done. It asks before it replaces anything.

An older render is in the way. Allow the replacement when it asks.

A 30-second spot to four deliverables: a broadcast master, YouTube, a vertical cut with captions and a square — loudness to spec, checked at the end.

The spec is a note

Formats, loudness targets and file names live in a note you edit once per client — the agent follows it on every job.

Safe zones respected

The client’s guide sits in the Reference card, so captions on the vertical cut stay clear of the platform’s buttons.

Measured, not assumed

After rendering, the agent runs a loudness pass on every file and reports the numbers it measured.

Nothing silently replaced

If a file with that name is already there, the agent stops and asks before overwriting it.

Video editing · Deliverables

From the locked cut to the upload folder

One agent, four cards.

01
Read
The spec and the safe-zone guide.
02
Probe
The master’s format and loudness.
03
Render
Each deliverable, ticked off.
04
Check
Loudness of every file.

Masters from the editor you already use

Premiere ProDaVinci ResolveFinal Cut ProAvid Media Composer
Related scenarios

More in Video editing

Other live scenarios from the same shelf — and a few close relatives.

Browse all 40 scenarios

Leave the export queue to an agent

It measures what it renders and asks before replacing a file.

Download for WindowsWindows 10 / 11 · 64-bit

macOS and Linux are coming later.

The first-run wizard installs an agent CLI, Git and the dictation model for you — or skips each step.