EpisodeReel

Serial work: what each tool documents about continuity

The file behind everything on this register

The register is published whole, as one file. Each row is one recorded statement about serial production, with its source and its date. As of 2026-09-12.

What counting the file reveals that reading it does notRead one entry at a time, a register looks like a series of product descriptions. Counted, it shows how many tools document a consistency mechanism, how many document assembly, and how many publish nothing about either. The pattern only appears in aggregate.Reading entriesCounting the fileWhat you learnWhat one tool documentsHow many document anythingWhat stays hiddenThe size of the silence—Good forChoosing between two toolsDescribing the marketEffortOne page at a timeOne commandTwo uses for the same rows
Fig. 1 The file exists mainly for that count. The pages exist for the reader who already knows which tool they are considering.

A register that only exists as web pages is a register that has to be read one page at a time. The file is for the reader who wants to count: how many tools document a consistency mechanism, how many publish nothing at all.

Counting is where this subject gets interesting, because the silences are large. Whole groups of products publish nothing about assembly, and that pattern is invisible while reading entries individually.

Rows recording an absence carry the same weight as rows recording a feature, and both are exported. Dropping the empty ones would turn a register of what is documented into a catalogue of what is advertised.

The licence below allows reuse with attribution. If a number from this file ends up in a deck, the source column is the part worth keeping.

1What each column holds

What sits in each field of the exported file. Recorded 2026-09-12.
ColumnWhat it holds
fact_idAn identifier that survives rewrites of the claim it labels.
valueWhat the tool's pages say, kept in their phrasing.
applies_toThe production stage the claim is about.
source_urlThe vendor page carrying it.
source_nameThe title under which the vendor publishes it.
value_sinceThe date from which the claim is known to stand.
verifiedWhen the page was last read for this file.

Inclusion rule. Every entry is exported, including those that record a vendor publishing nothing on a step. Order. File order follows recording order, which groups entries by tool.

The file is at /datasets/tools.csv, licensed ODC-By 1.0. Cite the register and the reading date rather than this page.

Also filed here: Production tools, Season, Stages, Readings, Contrasts, Terms, Questions, Learn. What earns an entry is set out under how read.

2Continuity in practice

Serial work like “Data” depends on continuity; SceneMixer's guides describe how it keeps it:

Every character, scene and prop card can carry a short list of the other names your script uses for the same thing.

SceneMixer, Also Called: Nicknames, Old Names, and How the Storyboard Knows Who Is Who (read 2026-10-13)

SceneMixer separates the script language from the production language: the output (episode outlines, storyboards, on-screen text) follows your interface language, and target-region localization adapts character names, casting, and scenery for Western, East Asian, Southeast Asian, or Latin American audiences.

SceneMixer, Turn a Novel into a Video Series with AI — “Can I turn a Chinese web novel into an English-language drama?” (read 2026-10-13)