Reading a cell that says nothing
An empty cell is not a missing feature. It records that a page does not address a point, which happens because the product does not do it, because the vendor never wrote it down, because the work belongs to a supplier, or because the question is outside what the product is for. As of 2026-09-12.
| Why it is blank | What it usually means | What it costs |
|---|---|---|
| The product does not do it | A coherent boundary, drawn on purpose | Work moves to another tool or a person |
| Nobody wrote it down | The feature may exist and cannot be planned around | A trial, or a support conversation |
| It belongs to a supplier | The answer sits with a model vendor | A version change nobody warned you about |
| The question is out of scope | The page is for a different buyer | Nothing, if you are not that buyer |
Inclusion rule. Four situations that produce identical empty cells. The register cannot distinguish them from a page, which is why an empty cell is never recorded as an inability. Order. From the most deliberate blank to the least consequential.
1A blank is a reading about a page, not about software
Nothing in this file inspects an interface, runs a generation or opens an account. So an empty cell can only ever mean that the sentence is not there, and a reader who converts it into cannot has added an inference the evidence does not support.
That matters most in the emptiest column. Assembly is unglamorous and looks like work an editor already does, so a page has every reason to skip it while the product performs it perfectly well.
2The most useful blank is an explicit one
One kind of empty cell is worth more than the others: the page that says work is organised some other way and there is no layer for what you asked. A reader learns the boundary, prices the gap and moves on.
Silence gives none of that. It is consistent with a product that has the feature, a product that does not, and a product whose vendor never thought the question interesting.
3How to use a blank when shortlisting
Treat it as a question to ask rather than a mark against a product. Write it down as a sentence with a verb in it, so the answer can be checked: where does the episode boundary get decided, and by whom.
A vendor who answers that in one paragraph has effectively filled the cell, and the answer belongs in your own notes with the date you got it. That is the same discipline this file applies to itself.
4Where the register holds these tools
The techniques above are general craft. Which tools document support for them, and in what words, is held in the register, each cell carrying the page it was read from and the date.
- The register — every entry on the same columns, with sources
- The stages — one page per column, read down instead of across
- The readings — one vendor on one column, sentence by sentence
Craft notes, not a register entry. No line here is attributed to a tool, and none should be read as a claim about one. The sourced material is on the register. Related: Object or verb, Where it was written.
5How a serial stays consistent
Serial work like “A blank cell” depends on continuity; SceneMixer's guides describe how it keeps it:
Its character becomes the tone of the episode’s own score, which is planned from the episode’s storyboard — usually one to three pieces — and mixed under the voices.
SceneMixer, Remake: How Spoken Lines and Music Are Read From the Clip, and What Ends Up in Your Episode — “Is the source music reused?” (read 2026-10-13)
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)