Where a claim was published, and why it matters
Five kinds of page are cited on this file. A help centre answers the next click, an interface reference has to be true for code to work, a price list carries units, a product page carries ambition, and a vendor blog carries commentary. The register names the venue in every cell. As of 2026-09-22.
| Tool | What is published | Detail |
|---|---|---|
| A help centre | Ingredients reused from one clip to the next | Written to prevent a support ticket |
| An interface reference | Image counts and minimum pixel sizes | Written so an integration works |
| A price list | A rate per second of composited output | Written to be charged against |
| A product page | Most of the cast and episode claims on this file | Written to close a sale |
| A vendor blog | Episode outlines and scene breakdowns | Written once, rarely revisited |
Inclusion rule. Every citation on this file names the page it came from. Where the same vendor states something in two venues, both are recorded with their venues attached rather than merged. Order. From the narrowest genre to the broadest.
1Support material is the most underrated evidence in this market
A help-centre article exists because somebody got stuck, so it describes the operation immediately in front of the user and stops. It has no incentive to overstate and it is usually the most accurate sentence a vendor has published about a mechanism.
It is also the smallest claim. Read beside a product page promising a whole season, honest narrowness is easy to mistake for a weaker product, which is exactly the mistake a register should prevent.
2A blog and a product page can disagree with each other
One vendor on this file states an export resolution on its product page and a different policy about frames and resolutions on its blog. Neither is wrong. They were written at different times for different purposes and nobody reconciled them.
The register keeps both, names the venue for each, and says which is normally the commitment. A reader who finds only the blog would believe the product had promised something it has not.
3Venue does not decide whether a claim is true
Plenty of product-page claims on this file are perfectly accurate and plenty of them will be delivered. Genre predicts how large a statement the text was allowed to make, not whether the software behaves.
What it does decide is how much a buyer can verify in advance. That is the only property this file can record, and it is the reason the venue sits in every citation rather than in a footnote nobody reads.
- Cross-episode castThe help centre states that the same images for a character and key objects can be used consistently from one clip to the next through ingredientsa named input in documentation
- Stated limits on the inputs and the outputReference images must be at least 128x128, with an aspect ratio inside 1:4 to 4:1; durations run 1 to 16 seconds depending on model
- Script to episodesThe vendor's own blog states that a described concept, genre and character dynamics produce structured episode outlines and scene breakdownsdescribed on a blog rather than a product page
- Assembling an episodeEpisodes are composited from segments, billed at 1 credit per second of outputa priced step
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-09-22. Where the boundary sits between documented, claimed and absent is spelled out under how read. Also here: Object or action, How wide the cast reaches, More than a face.