When a vendor describes an outcome and not a mechanism
One vendor describes character sheets and locations as being held so a series stays consistent. That is a statement about an outcome with no mechanism attached, and the register records it as claimed rather than documented. One vendor publishes nothing about season-scale work at all. As of 2026-09-22.
| Tool | What is published | Detail |
|---|---|---|
| invideo AI | Claimed | Memory described, mechanism not published |
| Pika | Nothing published | No season-scale features on its pages |
| Fourteen other tools | Documented | A named object or a named artefact |
Inclusion rule. Documented means a named mechanism a reader can reason about. Claimed means an outcome asserted without one. Absent means nothing published. Order. From claimed to absent.
1The distinction is about what a buyer can verify before paying
A named object can be asked about: what is its scope, what happens when two conflict, can it be edited. An outcome cannot, because there is nothing to ask about except whether it works.
This register is built on published material, so it can only carry the first kind. Marking the second kind as claimed is not scepticism about the product; it is a statement about how much evidence exists.
2Publishing nothing is a clean position
A tool with no season-scale features and no claims about them is easy to place: it sells clips. A reader planning a series knows immediately that the structure layer is theirs to build.
That is more useful than a vague claim, and it is worth saying because an empty row looks like the weakest position on a table and often is not.
3What would move a row from claimed to documented
One paragraph naming the object, its scope and its lifetime. That is not a large ask and it is the difference between a feature a production can plan around and one it has to trial.
The register will move the row the day the paragraph exists, with the date it was read.
- Cross-episode castCharacter sheets and locations are described as held in agent project memoryvendor claim
- Season-scale featuresNothing published (as of 2026-09-12)none on the priced page
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.
5Continuity in practice
Serial work like “Claimed vs shown” depends on continuity; SceneMixer's guides describe how it keeps it:
Character consistency in AI short drama means one character keeps the same face, the same wardrobe and props, and the same art direction across the dozens to hundreds of shots in a series.
SceneMixer, AI Short Drama Character Consistency (2026): Why Faces Change Between Shots, and the Three Layers That Lock Them (read 2026-10-13)
The same way as a photographic one: the character is generated once as a reference sheet and that image is sent with every shot they are in, along with a couple of face-distinguishing notes. Shots refer to the character rather than re-describing their look.
SceneMixer, AI Animated Series Generator — “How do I keep a stylised character on model across episodes?” (read 2026-10-13)
6Sources
Each cell above traces back to a vendor page named in the register, read 2026-09-22. Where the boundary sits between documented, claimed and absent is spelled out under how read. Also here: Several markets, Vertical by default, Per call, not per cast.