EpisodeReel

Serial work: what each tool documents about continuity

Sets, characters and canon held as the show's world

The page states that the sets, characters and canon persist across the whole series, held in the product as the show's world. Canon in that list is the unusual item: it covers what has already happened, which no other reading in this column addresses. As of 2026-09-22.

Appearance and events are different continuitiesSets and characters can be compared with a reference. Canon is what has already happened, and a contradiction inside it cannot be checked against any frame.AppearanceCanonWhat it coversSets and charactersWho knows what, who is goneHow a failure showsA changed room or faceKnowledge nobody was givenHow it is caughtBy comparing framesBy reading before writingOne page on this file names the second at all
Fig. 1 Bundling all three into one named world suits a writers room and hides how each one fails.
Showrunner Studio 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 sentenceSets, characters and canon stated to persist across the whole seriesDocumented, at the scale of a series
What it namesA show world, containing three kinds of thing at onceOne object a writer can reason about, not three settings
What it leaves outHow a contradiction inside canon is resolvedThe interesting failure mode, and it is unaddressed

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.

1Canon is continuity of events, not of faces

Every other reading in this column is about appearance. Canon is about what is true in the story: who knows what, who is dead, which door was locked in episode three. A generated series breaks on that as readily as it breaks on a jawline, and it breaks less visibly.

Holding it in the product is a larger claim than holding a face, because a face can be compared to a reference image and a fact about episode three cannot be compared to anything.

2A world is a convenient container and a vague one

Bundling sets, characters and canon into one named thing suits how a writers' room actually works. It also means a reader cannot tell whether the three are stored alike, edited alike, or fail alike, and those differences decide what a correction costs.

The register records the bundle as published rather than splitting it into three cells the vendor never wrote.

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 Showrunner Studio 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 sets, characters and canon are stated to persist across the whole series, held in the product as the show's worldpersistence stated for a seriesShowrunner Studio, home page / recorded 2026-09-22
  • 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

5Sources

Read from the home page at showrunnerstudio.com, checked 2026-09-22. The whole column is on cross-episode cast and this vendor on every column is on Showrunner Studio; 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: Kling AI, Luma Agents.