Six jobs, whether one person or six are doing them
A generated series needs six jobs done and six handovers checked. One person does all six and reviews their own work; a team splits them and has to make each handover explicit. The jobs do not change, only who closes the gate. As of 2026-09-12.
| Job | What it hands on | What the gate refuses |
|---|---|---|
| Assembly and delivery | Episode files per placement | A cut whose joins were never watched at full length |
| Reference art | Character sheets, scene plates, prop shots | A plate with a scene event baked in, or a sheet the image does not match |
| Review and continuity | An episode marked ready | An episode nobody watched end to end in one sitting |
| Segment video | Accepted clips per segment | A clip accepted without the storyboard open beside it |
| Story and parsing | Approved cast, scene and prop sheets, an episode outline | A cast sheet written in adjectives of approval |
| Storyboard | A versioned storyboard per episode | Segments with blank fields, or dialogue that does not fit its shot |
Inclusion rule. Jobs that exist in every generated series regardless of headcount. Jobs specific to one delivery route, such as app submission, are not listed. Order. Alphabetical by job.
1Working alone, review is the bottleneck
Generation runs unattended. Reading the outline, judging the sheets, checking every segment and watching the cut do not. A solo production that measures its hours usually finds that machine time is close to free and attention is the whole constraint.
The practical consequence is to batch by kind rather than by episode: review six storyboards in one sitting, generate overnight, then judge the results in one pass. Switching between jobs is what makes a day disappear.
2On a team, the gate is the thing that has to be written down
Six people doing six jobs produces five handovers, and a handover that is not written down is a handover that gets disputed. The pass criterion has to be something the receiving person can check without asking the sender what they meant.
The criteria in the table are deliberately negative. It is far easier to agree on what a gate refuses than on what makes something good, and a refusal can be checked in a minute.
3Version the storyboard, not the clips
Clips are cheap to regenerate and expensive to catalogue. Storyboards are the opposite. Lock a storyboard version before generating from it, and record which version each accepted clip came from.
Without that, a corrected segment and its earlier takes become indistinguishable a week later, and somebody assembles the episode from a mixture.
4What a solo production should copy from a team
The gates, minus the people. Writing the six refusals on one page and reading them before moving on catches most of what a second pair of eyes would, and it costs nothing.
The part that does not transfer is independence. Nobody catches their own blind spot by reading their own list, which is why a solo production benefits more from one outside viewing per episode than from any further process.
5What a team should copy from working alone
The short loop. A team that routes every question through a gate can take a day to answer something a solo creator settles in a minute, and on a daily release schedule that is the difference between shipping and not.
The usual compromise is to make the gates strict and the path between them short: few people, clear refusals, and no approval step that exists only to be seen to exist.
Craft notes, not a register entry. No line here is attributed to a tool, and none should be read as a claim about one. The sourced material is on the register. Related: What the format demands, Testing a candidate.
6How a serial stays consistent
Serial work like “One person or a team” depends on continuity; SceneMixer's guides describe how it keeps it:
Each character in a SceneMixer project is one entry with one approved image.
SceneMixer, The Same Face in Every Shot (read 2026-10-13)
They are declared once in the segment header — who they are, where, what they are doing — and stay consistent across that scene.
SceneMixer, AI Multi-Character Scene Generator — “How do background extras work?” (read 2026-10-13)