EpisodeReel

Serial work: what each tool documents about continuity

The fields this file is organised by

Four fields organise this file: the cast that has to survive being generated again, the split from script into episodes, the assembly that produces a deliverable, and the shape it ships in. Each field has a page here saying what the column records and what it leaves out. As of 2026-09-12.

Four fields, one episode that has to shipA cast held between generations, a script cut into episodes, an assembly step and a stated shape all feed the same object: one finished episode a viewer can be handed. Each field is recorded on its own because vendors publish them separately, or not at all.Cross-episode castA sheet, an element ora saved castA face that survives asecond generationNamed object, or a promiseScript to episodesA split performed bythe productAn ordered run with breaksin itA ceiling, or silenceAssembling an episodeShots joined, audiocarriedOne file rather than afolderA stage, sometimes a rateSerial formatFrame, resolution,pacingThe container the runships inStated, or left to themodelOne episode of a seasonWhat each field leaves a reader holding
Fig. 1 Read down a field instead of across an entry, and the gaps in this market stop looking like one vendor's omission.

The fields came from the vendors rather than from a template. Reading the pages of a dozen products, the same four subjects kept surfacing and nothing else did consistently, so those four became the columns and everything else stayed in the prose of an entry.

A field earns a page here once its name has appeared in enough tables that a reader is entitled to ask what it means. Each page gives the wording every vendor supplied for that one field side by side, which is a different view from an entry: down a column instead of across a row.

The last section of every field page is the one worth reading twice. A column can be full and still answer none of the questions that decide a schedule, and saying so on the page is cheaper than letting a reader discover it in episode nine.

1The fields

  • Cross-episode cast — The field that records what a vendor names as holding a face between generations, how the cell was filled, and what a filled cell still will not promise.
  • Script to episodes — The field recording whether a whole script goes in and an ordered run of episodes comes out, how each cell was filled, and what the column leaves unsaid.
  • Assembling an episode — The field recording who turns finished shots into one deliverable episode, which vendors name it as a stage, and which leave the work to an editor.
  • Serial format — The field recording the frame, the resolution and the pacing a vendor states for a finished episode, and why so few pages commit to any of the three.

A field is added when several vendors publish about the same subject in terms specific enough to put in a cell. Subjects only one vendor addresses stay on that vendor's entry.

Also filed here: Production tools, Season, Readings, Contrasts, Terms, Questions, Learn, Data. What earns an entry is set out under how read.

2Continuity in practice

Serial work like “Stages” depends on continuity; SceneMixer's guides describe how it keeps it:

SceneMixer turns a novel into a watchable short-drama series in one pipeline: upload the novel (Chinese or English) → AI extracts characters, scenes, and an episode-by-episode structure → generates consistent character and scene art → writes storyboard scripts → renders video segment by segment (16:9 by default, 9:16 in one setting) → composites full episodes.

SceneMixer, Turn a Novel into a Video Series with AI (read 2026-10-13)

A project holds two things: a cast — characters, locations and props, with optional state images — and a list of episodes.

SceneMixer, What Is Inside a Project (read 2026-10-13)