EpisodeReel

Serial work: what each tool documents about continuity

A Cast and a World named as the things a series is built on

The page describes a recurring Cast, a World and connected Scenes as the things a phone-first series is built on. Presenting them as the foundation rather than as an outcome is a statement about how the product is arranged, and arrangements can be asked about. As of 2026-09-22.

Foundation language against outcome languageSaying a series is built on a Cast and a World tells a reader where the work lives. Saying leads stay consistent tells them what the vendor hopes they will see.A foundationAn outcomeWhat it describesHow the product is arrangedWhat the buyer should expectBefore payingCan be asked aboutCan only be trialledCovers the roomA shared WorldRarely mentionedWhat holds a face inside the Cast is one level down and unstated
Fig. 1 Neither sentence proves anything about the footage; they differ in what can be interrogated.
character.app on the cross-episode cast, in the wording the page uses. Read 2026-09-16.
PointWhat the vendor's page statesHow this file reads it
The sentenceA recurring Cast, a World and connected Scenes behind the seriesDocumented, as product structure
What it namesTwo objects and the relation between themA structure, which survives a handover to a second person
What it leaves outWhat holds a face inside the CastOne level down, and the page does not go there

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.

1Foundation language and outcome language are different evidence

Saying a series is built on a Cast tells a reader where the work lives. Saying leads stay consistent tells them what the vendor hopes they will see. The first can be interrogated before money changes hands; the second can only be trialled.

Neither sentence proves anything about the footage. They differ in how much of the product a buyer is allowed to understand in advance, which is the only thing this file can record.

2A World beside the Cast covers the second thing that drifts

Characters get the attention and rooms get the errors. A shared World that the Scenes connect to is an answer to the question of why the kitchen has a different window in episode six, and very few pages in this column pose that question at all.

How the World is represented is unstated, so the reading stops at the object. That is still one level deeper than most of the column reaches.

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 character.app 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
    The product is described as building a recurring Cast, World and connected Scenes behind a phone-first seriesnamed reusable objectscharacter.app, vertical drama maker page / recorded 2026-09-16
  • Cross-episode cast
    Character dynamics, scenes and props are described as turned into reusable assets so a new episode keeps the visual continuitynamed reusable assetsDramily, home page / recorded 2026-09-22

5Sources

Read from the vertical drama maker page at character.app, checked 2026-09-16. The whole column is on cross-episode cast and this vendor on every column is on character.app; where the line falls between documented, claimed and absent is under how read. This vendor's other readings: the split into episodes, the assembly step. Other readings of the same column: OpenArt, Anijam.