EpisodeReel

Serial work: what each tool documents about continuity

What counts as published here

Three grades are kept apart: a documented mechanism, a vendor claim, and nothing published. Each row says which it is. Nothing is filled in from using a product, and nothing is inferred from a screenshot of an interface. As of 2026-09-12.

The three grades a row on this register can carryThree grades are kept apart. A documented mechanism is a vendor describing how something works. A vendor claim is a statement about an outcome with no mechanism attached. Nothing published is the third. Each row says which it is, nothing is filled in from using a product, and nothing is inferred from a screenshot of an interface.What a vendor has publishedA mechanismDocumentedHow it works, in the vendor's ownwords.An outcomeClaimedThat it works, with nothingattached about how.NeitherNothing publishedRecorded as such, and not filledfrom an interface.An interface is a product, not a statement
Fig. 1 The grade travels with the row rather than sitting in a note at the bottom, because a reader comparing two cells needs to know what kind of thing each one is.

1Where the three grades currently fall

Twenty-six tools are held here and the grades are not evenly spread. Fourteen name the thing that holds a character: a reference sheet injected per segment, two reusable element systems, a Cast and a World the series is built on, images handed over on every call with nothing stored, Hyperframe, cast cards holding a face and a voice, ingredients reused from one clip to the next, stored production assets with a span attached, a character called by name in each script, an appearance locked at creation, definitions preserved through localisation, reusable assets carried into a new episode, and a canon that persists across a series. Eleven describe the result instead. Among them, OpenArt promises face, wardrobe and chemistry, StoryShort puts casting between two mechanical steps, Anijam names locking as an action, Topview says characters are built before generation, Medeo attributes it to the model it runs on, AI Drama Generator lists it among outputs, and DramaSo lists it beside lip-sync and captions. The twenty-sixth row, Pika, publishes nothing on any of the three steps.

That distribution is the finding, and it moved. Read before 2026-09-22, the products built specifically for this format were the ones least likely to say what holds a face together, while the general video products that arrived from somewhere else were the ones naming objects. The twelve entries read on 2026-09-22 reverse it: nine of them name an object, and the newest names are drama words rather than model words — a canon, a cast card, a production asset, a character addressed by name in a script.

What has not moved is the second column. A product can name the artefact that holds a lead together and still leave the break between one episode and the next undescribed. Seven of the fourteen that name a cast mechanism are in that position, four of them saying nothing at all.

2The three grades

A documented mechanism names what is stored and when it is applied. SceneMixer's sentence about a reference sheet generated at analysis time and injected into every segment is the clearest example in the register: a reader can predict what happens and, more usefully, predict how it fails.

A vendor claim describes a capability without naming a mechanism, usually on a page written to sell rather than to document. It is recorded, labelled, and not upgraded. Claims are evidence of direction; they are not evidence of behaviour.

Nothing published means the vendor does not address the step. It is not a finding that the product cannot do it. Several of these tools can obviously assemble an episode in some fashion; none of them says so in a place a buyer can check.

3Why an interface does not count

A screenshot showing an episode list would be tempting evidence for the middle column. It is not used, because an interface element does not tell a reader what the software does with it, how many episodes it holds, or whether the structure survives a re-generation. A register built from interface tours records what a demo looked like on one day.

The same restraint applies to trying the products. One season produced on one script is one sample, and consistency across forty episodes is exactly the property a single sample cannot demonstrate.

4Why the grade travels with the row

A table that mixed grades silently would read as a comparison of products when it is really a comparison of documentation. Two vendors can be equally capable and only one of them will have written anything down, and the reader deserves to know which situation they are looking at before drawing a conclusion from a blank.

It also protects the vendors that do publish. A vendor that describes a mechanism precisely exposes more surface to criticism than one that says nothing, and a register that flattened the two would quietly punish the more open of them.

5Dates and corrections

Two dates accompany each entry: when it was first written down and when it was last set against the vendor page. Setting it against the page and finding no change still advances the second, which keeps a stale-looking entry distinguishable from an unexamined one.

The date on a page follows its content and ignores rebuilds entirely. Where a vendor now says something other than what is recorded, the vendor is the record and this register follows.