The same room in every episode
Six tools in the register say something about places staying the same across a series: a built world, scenes as stored assets, sets that persist, locations held in memory. One documents the mechanism, a location entry with its own image from which every scene set there is generated, with time of day and weather written on top. As of 2026-10-13.
| Tool | What is published | Detail |
|---|---|---|
| character.app | A recurring Cast, World and connected Scenes behind a series | The world named as a built object |
| Dramily | Scenes turned into reusable assets so a new episode keeps continuity | Stored per project |
| invideo AI | Locations described as held in agent project memory | An outcome, no mechanism |
| PopShort AI | Scenes stored as reusable production assets | Reused throughout the series |
| SceneMixer | A location entry with an image every scene there is generated from | Time of day and weather written per segment |
| Showrunner Studio | Sets persist across the whole series | Held as the show's world |
Inclusion rule. Tools whose pages mention locations, sets, scenes or a world as something kept across episodes. Statements about characters alone are on the cast question. Order. Alphabetical by tool.
1A room is a reference, like a face
Returning to the same kitchen in episode one and episode nine is a continuity test the audience takes without trying: the window, the table and the tiles either match or they do not. Most tools here describe the result. One describes the object behind it, a location entry with an image that every scene set there is generated from, in any episode.
2What changes on top of a fixed room
A fixed room still has to look like morning in one scene and a storm at night in another. The documented split is the same one used for characters: the room comes from its image, and the time of day and the weather are written per segment and change on top of it. The room does not drift because nothing about it is regenerated from words.
3Claimed and documented, again
Locations held in an agent's memory is a statement about an outcome; a stored scene asset or a location image is a statement about a mechanism. The register keeps the two apart for places as it does for faces, because only one of them tells a production what to check when a room comes out wrong.
- Cross-episode castThe product is described as building a recurring Cast, World and connected Scenes behind a phone-first seriesnamed reusable objects
- Cross-episode castCharacter dynamics, scenes and props are described as turned into reusable assets so a new episode keeps the visual continuitynamed reusable assets
- Cross-episode castCharacter sheets and locations are described as held in agent project memoryvendor claim
- Cross-episode castCharacters, scenes and props are stated to be stored as reusable production assets, reusable throughout the series to help maintain consistency from Episode 1 to Episode 50stored assets with a stated span
- Cross-episode castThe sets, characters and canon are stated to persist across the whole series, held in the product as the show's worldpersistence stated for a series
- The same room in every episodeA location is an entry with its own image, and every scene set there in any episode is generated from that image; time of day and weather are written per segment on top
- Script to episodesOne upload is analysed into characters, scenes, props and episode structurein one pass
4The words this register uses
Terms with a page of their own, each recording what vendors publish about it, include segment and shot, reference image, character consistency, storyboard script, scene plate, novel to video, AI short drama and vertical micro-drama.
5Sources
Each cell above traces back to a vendor page named in the register, read 2026-10-13. Where the boundary sits between documented, claimed and absent is spelled out under how read. Also here: Endings and openings, Keeping a cast, Splitting a script.