Character sheets held in project memory, with the memory undescribed
The page describes character sheets and locations as held in agent project memory. Memory is a location rather than a mechanism: nothing states what a sheet is, whether a user can see one, or what happens to it when a project is reopened weeks later. As of 2026-09-12.
| Point | What the vendor's page states | How this file reads it |
|---|---|---|
| The sentence | Character sheets and locations held in agent project memory | A claim, with a place named |
| What it names | Memory, scoped to a project | A container, not the thing inside it |
| What it leaves out | Whether the sheets are visible, editable or durable | All three decide what a correction costs |
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.
1Memory is the most borrowed word in this column
It arrived from conversational assistants, where it means the system will act as though it remembers. Applied to a season it has to mean something stronger, because a production needs the artefact to exist on a Tuesday six weeks later.
The page does not say which of the two senses is intended, so the register records the claim and the word, and declines to upgrade it to a mechanism.
2Locations alongside sheets widens the claim without firming it
Including locations is right: a series needs its rooms to persist as much as its faces. It also doubles the amount of undescribed material, since neither the sheet nor the location has a stated form.
One paragraph naming the object, its lifetime and whether a user can open it would move this reading into the documented group. The register will move it on the day that paragraph exists, with the date it was read.
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 castCharacter sheets and locations are described as held in agent project memoryvendor claim
- Cross-episode castA full-body reference sheet is generated per character at analysis time, and its face and body crops are injected into every segment featuring that charactera stated mechanism
5Sources
Read from the microdrama page at invideo.io, checked 2026-09-12. The whole column is on cross-episode cast and this vendor on every column is on invideo AI; where the line falls between documented, claimed and absent is under how read. This vendor's other readings: the split into episodes. Other readings of the same column: Anijam, Arcloop.