EpisodeReel

Serial work: what each tool documents about continuity

Claims that belong to a supplier, not the product

Four pages on this file locate the cast inside a generative model rather than inside a production tool. Three of them are the model vendors themselves, which is the expected division of labour. The fourth is a product attributing the property to a supplier its buyer has no contract with. As of 2026-09-22.

Whose product the cast sentence is aboutA model vendor documenting its own element has drawn the boundary where it belongs. A product attributing consistency to the model underneath it has moved the answer to a supplier its buyer has no contract with.Who is the page describing?Its own model layerThe expected division of labourThe structural work stays with whoever buys it, and thesilence is the shape.A supplier's modelThe risk moves outwardNo release notes, no contract, and a face that canchange without notice.Candour and exposure arriving in the same sentence
Fig. 1 A model updated mid-run can change a face, and no page states whether a version is pinned.
Where the cast is located in each case, and whether the page is the model vendor or a customer of one. Recorded 2026-09-22.
ToolWhat is publishedDetail
MedeoConsistency attributed to the model it runs onA product pointing at a supplier
Kling AIAn element carrying appearance and voiceThe model vendor's own layer
Google FlowIngredients, and a model chosen per generationThe model vendor's own layer
Luma AgentsDefinitions preserved across named operationsThe model vendor's own layer
ViduReference images per call, nothing storedThe interface, with no layer at all

Inclusion rule. Recorded from whose product the sentence describes. A model vendor documenting its own cast layer is a different position from a product attributing consistency elsewhere. Order. The attributing product first, then the model vendors, then the interface.

1A model vendor documenting its own layer is the expected shape

Holding a face is a model-level problem and model vendors solve model-level problems. A page that documents an element or an ingredient and says nothing about episodes has drawn the boundary where it belongs, and the structural work stays with whoever buys it.

Reading the silence in the neighbouring column as an omission would be a mistake. It is the shape of the product, and this file records shape rather than scoring it.

2A product attributing the property upward transfers the risk

Saying the model does it avoids claiming credit the product has not earned, which is more than several pages here manage. It also puts the answer with a vendor the buyer cannot pin down, with no release notes and no obligation.

A model updated mid-run can change a face, and nothing on that page says whether the product pins a version. For a season assembled over weeks that is a scheduling exposure rather than a quality one.

3Choosing a model per generation is the version risk in plain sight

One help centre lists the model as one of four preferences set before each clip. A series generated across two model versions can drift for reasons no continuity mechanism will catch, and nothing about that is a defect.

It is a filing discipline the operator has to keep. Recording it here is the only way a reader learns that the risk exists before meeting it in episode nine.

  • Cross-episode cast
    Character consistency is attributed to the underlying video model rather than to the productattributed to a modelMedeo, short drama page / recorded 2026-09-16
  • Cross-episode cast
    Characters defined as elements carry their appearance and voice between generationsper elementKling AI, model guide / recorded 2026-09-12
  • Serial format
    Aspect ratio, number of outputs, model and generation length are listed as the video preferences selected before generatingexposed as a preferenceGoogle Flow, help centre / recorded 2026-09-22
  • Cross-episode cast
    Characters, products, logos and brand elements are described as definable, with the agent instructed to preserve them across variations, video generation, localisation and iterationsdefined objects and where they are preservedLuma Agents, product page / recorded 2026-09-22
  • Cross-episode cast
    No reusable character or element stored between calls is documentedwhat the documentation does not describeVidu, reference-to-video API reference / recorded 2026-09-12

4The words this register uses

Terms with a page of their own, each recording what vendors publish about it, include segment and shot, reference image, character consistency, storyboard script, scene plate, novel to video, AI short drama and vertical micro-drama.

5Continuity in practice

Serial work like “Borrowed from the model” depends on continuity; SceneMixer's guides describe how it keeps it:

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)

A producer working in German can make a series whose cast speaks Indonesian: the interface and the working documents follow the interface language, the spoken dialogue follows the project setting.

SceneMixer, AI Short Drama in 15 Languages (2026): Interface, Scripts and the Dialogue Your Cast Actually Speaks — “Can the interface be in one language and the dialogue in another?” (read 2026-10-13)

6Sources

Each cell above traces back to a vendor page named in the register, read 2026-09-22. Where the boundary sits between documented, claimed and absent is spelled out under how read. Also here: A draft before a spend, Adding an episode, Cast in a new project.