From sentence to cut: how Studio's pipeline actually works
Five stages, five places to stop. The pipeline is rigid on purpose — the rigidity is what lets the picture stay coherent.
The first thing every filmmaker who tries a generative tool notices is that the tool wants to start at the wrong place. Most tools start at the prompt. Studio starts at the project.
A film has a structure. Premise, world, cast, look, rules — these come before any single frame. If the model hallucinates a different lead actor in scene 12 than in scene 3, the audience leaves. If the warmth of the kitchen at dusk in act one is gone in act three, the audience leaves. Continuity is the whole job. The pipeline below is built to make continuity structural, not vibes.
The five stages
Studio gates the workflow into five stages. Each one approves what comes next; you can revisit a completed stage but you can't skip ahead.
- Setup. The first conversation: title, idea, length, tone. Three minutes.
- Core. Studio drafts the bibles — synopsis, atmosphere, cast, world, rules. You approve each section before the next is offered. The Core is the shared memory every downstream prompt reads from.
- Sequence. Script and storyboard fused, scene by scene. Read the screenplay, lock the keyframe, approve. Identity anchors keep the cast canonical.
- Timeline. Render in 10-second blocks with DP-grade controls — T-stop, shutter angle, ND, LUT. This is where the film is composed, frame by frame.
- Render. Watch it through, grade the picture, export the deliverables.
Why gates
The gating is the part that wins arguments with the model. Without it, the AI builds a film one prompt at a time and forgets what it told you in the last one. With it, every prompt downstream of the Core sees the Core; every prompt downstream of the Sequence sees the approved keyframes. The continuity is enforced architecturally, not by hoping the model will remember.
A natural consequence: the gating is also where you push back. Don't like the cast? Revise in Core. Don't like the keyframe? Revise in Sequence. By the time you hit Render, you've already made every decision the film depends on. The render stage is execution, not invention.
What this gives you
Coherent films, not collections of cool shots. Films you can show your editor without apologising. A workflow that scales from a 30-second short to a multi-episode series, because the structural memory carries across.
It's slower than "prompt and pray." That's the trade. The films are better.