Locking written as a verb, with no object left behind
The page states that it locks characters' faces across every episode, syncs dialogue to lip movement and assembles everything on a timeline. Three verbs, no nouns: the tool is described by what it does rather than by what it keeps. As of 2026-09-22.
| Point | What the vendor's page states | How this file reads it |
|---|---|---|
| The sentence | Locking faces across every episode, as something the tool does | A claim expressed as an action |
| What it names | Three operations, in the order they happen | A process a reader can follow end to end |
| What it leaves out | Anything a user can point at between the operations | Verbs cannot be handed to a second person |
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.
1Verbs describe a service, nouns describe an asset
A page written in verbs is telling a buyer the work will be done for them, which is a reasonable thing to sell. A page written in nouns is telling them where the work is kept, which is what a second operator needs on their first morning.
Both can produce the same footage. They differ in what a production owns afterwards, and that is the distinction the evidence grade is recording.
2Lip movement in the same sentence is a different kind of continuity
Syncing dialogue to lip movement is continuity within a shot rather than between episodes, and it is the failure a viewer spots fastest. Putting it beside the episode-level lock bundles two problems that are solved at different scales.
The register keeps them together because the vendor did, and notes that the sentence therefore answers a short-range question and a long-range one with the same verb.
3Where this sits in the column
| Tool | What the vendor publishes on the cast |
|---|---|
| AI Drama Generator | Consistent characters listed among the outputs, with no mechanism named |
| AI Dramas | Each character saved with a name, a face and a voice style, then called by name in every script |
| Anijam | Locking characters' faces across every episode stated as an action the tool performs |
| Arcloop | Locking a face, outfit, personality and visual identity listed as a step, with no object named |
| character.app | A recurring Cast and World described as objects the series is built on |
| Crano AI | The same identity stated to hold across episodes, with stable appearance and emotional presence |
| DramaSo | Consistent characters listed among the outputs, with no mechanism named |
| Dramily | Character dynamics, scenes and props turned into reusable assets |
| Genra | Cast cards holding a face and a voice, stated to carry across every scene |
| Google Flow | Ingredients, the same images reused for a character and key objects from one clip to the next |
| invideo AI | Project memory holds character sheets and locations |
| Kling AI | Elements carry appearance and voice between generations |
| LTX Studio | Elements are reusable across projects |
| Luma Agents | Characters, products and brand elements defined once and preserved across named operations |
| Medeo | Consistency attributed to the video model the product runs on |
| Novi AI | A character created in the product, whose appearance the system locks for the whole project |
| OpenArt | Leads stated to stay the same across every episode, face, wardrobe and chemistry |
| Pexo | Hyperframe, named as what locks a face, wardrobe and voice across every episode |
| PopShort AI | Characters, scenes and props stored as reusable production assets, from Episode 1 to Episode 50 |
| SceneMixer | Reference sheet per character, crops injected into every segment |
| Showrunner Studio | Sets, characters and canon stated to persist across the whole series |
| StoryShort | Casting consistent characters listed as a step, with no mechanism named |
| Topview | Characters and scenes stated to be built before video generation, to help continuity |
| TrendShort | Locking identity, wardrobe, face and emotional range listed as a step |
| Vidu | One 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 castThe page describes locking characters' faces across every episode, syncing dialogue to lip movement and assembling everything on a timelinean action without a stored object
- Cross-episode castLocking identity, wardrobe, face and emotional range is listed as a step in the workflowa listed instruction
5Sources
Read from the drama generator page at anijam.ai, checked 2026-09-16. The whole column is on cross-episode cast and this vendor on every column is on Anijam; where the line falls between documented, claimed and absent is under how read. This vendor's other readings: the assembly step, the shape of the deliverable. Other readings of the same column: Crano AI, TrendShort.