Every AI video tool publishes the same content: how to write a better prompt. How to use their latest model. How to generate a beautiful four-second clip.
Nobody publishes how to produce a three-minute sequence where the character looks the same in every shot, the lighting matches across scenes, and the final assembly holds together as a coherent piece instead of a collage of disconnected clips.
That gap is not an oversight. Single-shot generation is what the tools sell. Multi-shot production is what the tools cannot do alone. Publishing the methodology means admitting that the model is one step in a longer process, not the entire process. Tool vendors have no incentive to publish that.
This is how a Deterministic Cinema pipeline actually works.
Stage One: Shot Planning
A film set starts with a shot list. So does a Deterministic Cinema pipeline.
The shot list defines every frame the final sequence needs: camera angle, subject position, environment, lighting, action, duration. It also defines the relationships between shots. Shot 3 follows Shot 2 with a match cut. Shot 7 returns to the environment established in Shot 1. Shot 12 uses the same character in a new location with consistent wardrobe.
This is the stage most prompt-led workflows skip entirely. The operator jumps straight to generation, writing each prompt from scratch, carrying continuity notes in their head or in a spreadsheet. By shot four, the notes are incomplete. By shot eight, the continuity has drifted beyond recovery.
The shot plan is not creative overhead. It is the document that makes the rest of the pipeline possible. Without it, every subsequent stage operates blind.
What the shot plan produces:
- A numbered list of every shot with visual specifications
- Continuity dependencies between shots (which shots share characters, environments, or lighting)
- A generation order that respects those dependencies (you cannot generate Shot 7 before Shot 1 if Shot 7 references Shot 1’s environment)
Stage Two: Character Locking
Character consistency is the single most common failure in multi-shot AI video. Every generation model produces characters stochastically. Without explicit control, the same text prompt generates a different face, build, and wardrobe in every clip.
Character locking solves this by defining each character once and injecting that definition into every shot prompt that features them.
The lock includes:
- A reference image (or set of reference images) that establishes the character’s visual identity
- A text description that supplements the image with details the model might interpret loosely: hair color, clothing specifics, distinguishing features
- Consistency markers that flag which attributes are non-negotiable (face structure, wardrobe color) and which have tolerance (exact pose, hand position)
The lock is created before any video generation begins. It is tested in isolation: generate three static images of the character in different poses and environments. If the character holds across those three tests, the lock is ready. If it drifts, the reference images or text description need adjustment before the pipeline proceeds.
This is where Deterministic Cinema diverges from prompt-led workflows most sharply. A prompt-led operator re-describes the character in every shot and hopes for consistency. A locked pipeline injects the same reference automatically and enforces it.
Stage Three: Scene Generation
Scene generation is the stage where the AI model actually runs. It is one stage out of five. In prompt-led workflows, it is the only stage.
Each shot is generated using three inputs:
- The shot specification from the shot plan (camera angle, action, environment, duration)
- The character lock for every character in the shot
- Continuity context from previously generated shots (lighting, environment details, time-of-day progression)
The continuity context is what separates this from single-shot prompting. Shot 5 knows what Shot 4 produced. It knows the lighting was warm, the environment was an office interior, and the camera was at eye level. It does not re-invent the scene from a text description. It extends the scene that already exists.
Generation happens in dependency order, not shot order. If Shot 10 references an environment established in Shot 2, Shot 2 generates first regardless of its position in the final sequence.
A film set has a pipeline. A prompt has a prayer.
Stage Four: Review Gates
Review gates are the quality control mechanism that prevents bad generations from cascading into assembly.
After each stage, output is reviewed against the specifications:
Post-character-lock review. Do the test images match the character description? Does the character hold across multiple poses? If not, the lock is revised before generation begins.
Post-generation review, per shot. Does the shot match the specification? Is the character consistent with the locked reference? Does continuity hold with the previous shot? If any check fails, the shot is regenerated before the pipeline moves forward.
Pre-assembly review. All shots reviewed in sequence. Does the visual flow hold? Are there continuity breaks that individual shot reviews missed? This is the equivalent of dailies review on a traditional set.
The review gates are what keep discard rates low. Prompt-led workflows report 75% discard rates for brand-critical output because failures are discovered at the end, after assembly, when the entire sequence is visible. By then, fixing one shot means re-evaluating every shot that depends on it.
In a stage-gated pipeline, failures are caught where they happen. A bad character lock is caught before generation. A bad generation is caught before assembly. The cost of failure is one re-generation, not a sequence rebuild.
Stage Five: Assembly
Assembly is where individual shots become a sequence. This stage is straightforward if the previous four stages did their job. It is a disaster if they did not.
Assembly includes:
- Shot ordering per the shot plan
- Transition handling (cuts, dissolves, match cuts as specified)
- Audio sync if the sequence is timed to a soundtrack or voiceover
- Final continuity check across the assembled sequence
The final output is a sequence that holds together because every component was controlled from shot plan through generation through review. The assembly does not fix continuity problems. It reveals whether the pipeline caught them.
Why Nobody Else Publishes This
Tool vendors publish single-shot tutorials because that is what their product does. A generation model produces one clip at a time. The model does not know about the shot before it or the shot after it. The model does not maintain character references across clips. The model does not enforce continuity.
Everything above the model, the shot planning, the character locking, the continuity enforcement, the review gates, is production methodology. It is the layer that turns a generation tool into a production system. Publishing it means acknowledging that the tool alone is not enough, which is a difficult position for a tool vendor.
For brands evaluating AI video production, the question is not which model produces the best individual clips. It is whether the production partner has a pipeline that produces reliable sequences. The pipeline is the product. The model is a component.
If your production needs multi-shot consistency, character continuity, and deadline-driven delivery, the starting point is a structured production brief that defines the sequence before generation begins. The brief is available at capabilities.
How many shots can a Deterministic Cinema pipeline handle? +
There is no technical ceiling on shot count. The pipeline scales linearly because each shot inherits context from the locked references, not from the operator's memory. A 30-shot sequence takes longer than a 5-shot sequence, but the consistency does not degrade.
Does this work with any AI video model? +
The pipeline is model-agnostic. Character locking, continuity context, and review gates sit above the generation model. The model produces the frames. The pipeline controls what goes in and what gets approved.
What is the discard rate inside a Deterministic Cinema pipeline? +
Significantly lower than prompt-led workflows, which report 75% discard rates for brand-critical output. The review gates catch failures between stages, so bad generations do not cascade into assembly.
How does this differ from traditional video post-production? +
Traditional post-production edits footage that already exists. This pipeline generates footage within defined constraints. The stage gates serve the same function as dailies review on a film set: catch problems before they reach the edit bay.