EpisodeReel

Serial work: what each tool documents about continuity

Definitions preserved through localisation and iteration

The page states that characters, products, logos and brand elements can be defined, and that the agent is instructed to preserve them across variations, video generation, localisation and iterations. The list of places is what makes this reading different from a bare promise. As of 2026-09-22.

Four operations a definition is told to surviveVariations, video generation, localisation and iterations are each named as a place where a defined character, product or brand element must be preserved.VariationsAlternate takes of thesame ideaThe same defined subjectThe common caseGenerationThe shot itselfThe definition, as aninstructionWhere most pages stopLocalisationA second market versionThe same subject againWhere a run driftsIterationsRevisions after reviewThe definition, stillRarely addressedOne defined character, product or brand elementWhat each stage would otherwise put at risk
Fig. 1 Localisation is the stage where a face quietly becomes somebody else, and few pages admit it exists.
Luma Agents on the cross-episode cast, in the wording the page uses. Read 2026-09-22.
PointWhat the vendor's page statesHow this file reads it
The sentenceDefined characters and brand elements preserved across four named stagesDocumented, with the stages enumerated
What it namesA definition, and the four operations it must surviveA scope written as a list rather than as an adverb
What it leaves outWhat preserve means when two definitions conflictAn instruction to an agent is not a constraint on one

Inclusion rule. Three points per reading: the sentence as the vendor published it, the thing that sentence names, and what it declines to settle. Nothing here is inferred from an interface or a demo. Order. From the published sentence, to what it names, to what it leaves open.

1Naming localisation as a place the definition holds is unusual

A season made for two markets is generated twice, and the second pass is exactly where a face quietly becomes somebody else. Listing localisation among the operations a definition survives addresses a failure most pages in this column do not admit exists.

Whether it holds is not something a page can settle. What the page does is tell a producer which stages the vendor believes it has covered, which is where to look first when it does not.

2An agent instructed to preserve is softer than a stored reference

Instructing a system to keep something the same and supplying that something on every call are different guarantees. The first can be overridden by a later instruction in the same conversation; the second cannot, because it is not an instruction.

The register records this as documented because the object and the stages are both named. It is worth reading the verb carefully all the same.

3Where this sits in the column

What the vendor publishes on the cast, entry by entryEvery entry on the cast column, with this one marked.What the vendor publishes on the cast, entry by entryWhat the vendor publishes on the castAI Drama Generator — What the vendor publishes on the cast: Consistent characters listed among the outputs, with no mechanism namedAI Drama GeneratorAI Dramas — What the vendor publishes on the cast: Each character saved with a name, a face and a voice style, then called by name in every scriptAI DramasAnijam — What the vendor publishes on the cast: Locking characters' faces across every episode stated as an action the tool performsAnijamArcloop — What the vendor publishes on the cast: Locking a face, outfit, personality and visual identity listed as a step, with no object namedArcloopcharacter.app — What the vendor publishes on the cast: A recurring Cast and World described as objects the series is built oncharacter.appCrano AI — What the vendor publishes on the cast: The same identity stated to hold across episodes, with stable appearance and emotional presenceCrano AIDramaSo — What the vendor publishes on the cast: Consistent characters listed among the outputs, with no mechanism namedDramaSoDramily — What the vendor publishes on the cast: Character dynamics, scenes and props turned into reusable assetsDramilyGenra — What the vendor publishes on the cast: Cast cards holding a face and a voice, stated to carry across every sceneGenraGoogle Flow — What the vendor publishes on the cast: Ingredients, the same images reused for a character and key objects from one clip to the nextGoogle Flowinvideo AI — What the vendor publishes on the cast: Project memory holds character sheets and locationsinvideo AIKling AI — What the vendor publishes on the cast: Elements carry appearance and voice between generationsKling AILTX Studio — What the vendor publishes on the cast: Elements are reusable across projectsLTX StudioLuma Agents — What the vendor publishes on the cast: Characters, products and brand elements defined once and preserved across named operationsLuma AgentsMedeo — What the vendor publishes on the cast: Consistency attributed to the video model the product runs onMedeoNovi AI — What the vendor publishes on the cast: A character created in the product, whose appearance the system locks for the whole projectNovi AIOpenArt — What the vendor publishes on the cast: Leads stated to stay the same across every episode, face, wardrobe and chemistryOpenArtPexo — What the vendor publishes on the cast: Hyperframe, named as what locks a face, wardrobe and voice across every episodePexoPopShort AI — What the vendor publishes on the cast: Characters, scenes and props stored as reusable production assets, from Episode 1 to Episode 50PopShort AISceneMixer — What the vendor publishes on the cast: Reference sheet per character, crops injected into every segmentSceneMixerShowrunner Studio — What the vendor publishes on the cast: Sets, characters and canon stated to persist across the whole seriesShowrunner StudioStoryShort — What the vendor publishes on the cast: Casting consistent characters listed as a step, with no mechanism namedStoryShortTopview — What the vendor publishes on the cast: Characters and scenes stated to be built before video generation, to help continuityTopviewTrendShort — What the vendor publishes on the cast: Locking identity, wardrobe, face and emotional range listed as a stepTrendShortVidu — What the vendor publishes on the cast: One to seven reference images supplied per callVidu
Fig. 2 Every entry on the cast column, with this one marked.
The cross-episode cast column with Luma Agents marked. Rows read between 2026-09-12 and 2026-09-22.
ToolWhat the vendor publishes on the cast
AI Drama GeneratorConsistent characters listed among the outputs, with no mechanism named
AI DramasEach character saved with a name, a face and a voice style, then called by name in every script
AnijamLocking characters' faces across every episode stated as an action the tool performs
ArcloopLocking a face, outfit, personality and visual identity listed as a step, with no object named
character.appA recurring Cast and World described as objects the series is built on
Crano AIThe same identity stated to hold across episodes, with stable appearance and emotional presence
DramaSoConsistent characters listed among the outputs, with no mechanism named
DramilyCharacter dynamics, scenes and props turned into reusable assets
GenraCast cards holding a face and a voice, stated to carry across every scene
Google FlowIngredients, the same images reused for a character and key objects from one clip to the next
invideo AIProject memory holds character sheets and locations
Kling AIElements carry appearance and voice between generations
LTX StudioElements are reusable across projects
Luma AgentsCharacters, products and brand elements defined once and preserved across named operations
MedeoConsistency attributed to the video model the product runs on
Novi AIA character created in the product, whose appearance the system locks for the whole project
OpenArtLeads stated to stay the same across every episode, face, wardrobe and chemistry
PexoHyperframe, named as what locks a face, wardrobe and voice across every episode
PopShort AICharacters, scenes and props stored as reusable production assets, from Episode 1 to Episode 50
SceneMixerReference sheet per character, crops injected into every segment
Showrunner StudioSets, characters and canon stated to persist across the whole series
StoryShortCasting consistent characters listed as a step, with no mechanism named
TopviewCharacters and scenes stated to be built before video generation, to help continuity
TrendShortLocking identity, wardrobe, face and emotional range listed as a step
ViduOne to seven reference images supplied per call

Inclusion rule. Every entry on this file appears in the column below, including the ones whose vendor says nothing on this step. The marked row is the entry this page is about. Order. Alphabetical by tool name.

4The wording itself

  • 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
    The help centre states that the same images for a character and key objects can be used consistently from one clip to the next through ingredientsa named input in documentationGoogle Flow, help centre / recorded 2026-09-22

5Sources

Read from the product page at lumalabs.ai, checked 2026-09-22. The whole column is on cross-episode cast and this vendor on every column is on Luma Agents; where the line falls between documented, claimed and absent is under how read. This vendor's other readings: the split into episodes, the shape of the deliverable. Other readings of the same column: Genra, AI Dramas.