What the engine actually does
You arrive at the Engine with an idea in plain language. Not a prompt, not a string of keywords weighted with colons — a sentence a creative director would say out loud in a room. The Engine’s work is to take that sentence seriously: to interpret it, structure it, and translate it into the exact dialect each image and video model speaks.
Think of it as the first assistant director you have always wanted. You state the intention; it breaks the intention down into subject, environment, light, camera, and composition, then briefs every department. It does not invent the campaign for you. It makes your campaign producible.
This distinction matters because most tools in this territory are generators — you pull a lever, something appears, and you reverse-engineer whether it was what you meant. The Engine works the other way. It builds the direction first, in a form you can read, argue with, and override, and only then composes the prompts.
From sentence to Blueprint
The moment you begin typing, the console starts reading. As your concept takes shape it surfaces live signals — EMOTION, GARMENT, TONE, ENVIRONMENT, REFERENCE, and their kin — showing you, in real time, what the Engine believes it has understood. If the signals are wrong, your sentence is ambiguous. Fix the sentence, not the machine.
On submission, the interpretation is resolved into a UniversalSchema — the Blueprint. This is a structured creative document: who or what the subject is and how it holds itself, what surrounds it, how the light behaves and from where, what glass is on the camera, how the frame is composed, what the palette permits. Every field is filled deliberately, and gaps are back-filled from a disciplined template so nothing ships half-specified.
The Blueprint is the campaign’s single source of truth. The summary, the prompts, the shot list, the moodboard, and the previz frames are all downstream of it. Change the Blueprint and everything downstream changes with it.
One direction, twenty dialects
A finished Blueprint is composed into platform-ready prompts through adapters — one per model, more than twenty in all. Midjourney, the Flux family, Imagen, Ideogram, Recraft, Seedream and Nano Banana Pro on the still side; Veo, Kling, Runway, Sora, Luma, Pika, Wan and Minimax for motion.
Each adapter knows its model’s temperament — what it rewards, what it ignores, where it drifts — and phrases the same creative direction accordingly. The marketing adapters compose for conversion: clean edges, negative space held for type, a hero moment at the three-second mark. The cinematic adapters compose for atmosphere. The direction never changes; only the dialect does.
This is why you select models at the end of the brief rather than the beginning. The model is a distribution decision, not a creative one. You built the world first; the adapters simply make sure each model receives it intact.
Between submit and delivery
When you submit, the console moves from compose to generating, and a short sequence runs in order. The concept is interpreted, references are detected and read for their visual signature, the Blueprint is built, resolved, and validated, and the prompt pack is written. The Engine then composes a prompt set for each model you selected.
Alongside the prompts, the Engine writes its own restatement of your idea — the campaign summary — and checks the direction for internal contradictions. If your requested emotion argues with your campaign type or output format, it names the tension and offers resolution paths rather than quietly averaging them into mush.
What arrives at the output phase is not an image. It is a directed campaign: summary, Blueprint, prompt pack, per-model prompts, and, depending on tier, the moodboard, shot list, and full creative direction document. The frames come later, and they come cheaper because this work came first.
How to work with it
Treat the Engine as a collaborator with excellent craft knowledge and no taste of its own. Taste is your contribution. The more precise your intention, the more of it survives the journey from sentence to schema to prompt to frame.
Read the summary before you read the prompts. If the summary describes a campaign you would not sign, the prompts do not matter yet — go back to the brief and sharpen the idea. The Engine is fast enough that revising the direction costs you a minute, where revising finished frames costs you the afternoon.
And resist the urge to write prompts at it. It is built to be briefed, not operated. The directors who get the most from it write the way they would speak to a trusted first AD: concretely, confidently, and once.