Vizard Agent

How to deliver a graphics layer to someone else's exact spec

Last updated 2026-10-10 · 2 min read

Give Vizard Agent the spec as a list and ask for each clause to be verified on the delivered file. Transparency is checked on the actual pixels rather than the codec flag, duration on the frame count rather than the container, and audio by whether a silent track exists at all.

What do you type into Vizard Agent?

Paste the spec, whole. Don't summarise it or tidy it up: a specification is written to be unambiguous, and paraphrasing one puts back exactly the ambiguity it was written to remove. Then add the fallback, such as rendering on pure black if neither ProRes 4444 nor WebM with alpha is possible, so Vizard Agent isn't left to guess.

Canvas 1080×1920, exactly 19.0 seconds, 25fps, fully transparent background, no audio, text only, all text inside the central 80% of the frame height.

What does Vizard Agent actually do?

It verifies each clause on the file it is about to hand over rather than on the command that produced it. An encoder can accept a flag and not honour it, and that gap is where almost every spec failure lives. Fixing one clause can also break another, so the earlier checks are re-run after every fix. In the session behind this article it:

When does this not work well?

When the spec is internally impossible. A duration that isn't a whole number of frames at the required rate cannot be met, and Vizard Agent will say so rather than round silently. Not every pipeline can produce every alpha format, so without a fallback the job stops there. Clauses like "on brand" or "premium" are reviewed by eye, not verified.

Common questions

What if alpha is not available? Give a fallback in the spec. Vizard Agent will not choose one for you.

How exact is "exactly 19 seconds"? To the frame. Vizard Agent reports the frame count as the proof.

Why does a silent audio track matter? Because some pipelines treat it as a real stream. The spec said none, so Vizard Agent removed it.