Reading the scope of a reusable cast object
Every reusable character has a boundary, whether or not the page states one. Inside a scene, inside a project, inside a series, or anywhere in the account: four spans that a single tick in a comparison column would record as identical. As of 2026-09-12.
| The boundary | What it is good for | Where it bites |
|---|---|---|
| One scene | The gap a viewer notices first | Episode two onwards |
| One project | A single series, cleanly isolated | The second series starts from a rebuild |
| One series | A long run with sets and canon | A spin-off, or a shared universe |
| Every project | A recurring lead across titles | One careless edit reaches signed-off work |
Inclusion rule. Four boundaries a reusable object can have, with the practical consequence of each. The table describes the arrangements rather than any vendor's implementation of them. Order. From the narrowest boundary to the widest.
1A wider scope is not automatically better
A lead held once and reused by every title is cheaper and more consistent, and it is also a single point of failure. Editing a shared object propagates into work that has already been approved, and nobody notices until a viewer does.
A project-bounded object has the opposite profile. Nothing leaks and nothing is inherited, so the second production pays for a rebuild it could have avoided.
2Ask about editing before asking about scope
Scope only matters if the object can change. An immutable character locked at creation has no propagation risk at any scope, and it also means the first version is the one that ships.
Almost no page addresses revision. It is the question that decides what a correction costs and it is left for a support conversation on every page read for this file.
3Write the boundary into your own notes
Where a vendor states a scope, record the sentence. Where a vendor does not, record that too, and assume the narrowest reading until somebody puts a wider one in writing.
Assuming the convenient reading is how a studio discovers in month four that its recurring lead was a project asset. The cost of that discovery is a second pass over every reference already made.
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: The frame comes first, Grades of evidence.
5One pipeline's continuity
Serial work like “Scope of an object” depends on continuity; SceneMixer's guides describe how it keeps it:
Sheets are generated inside a project, from the cast that analysis found, because their purpose is to be reused by that project's shots.
SceneMixer, AI Character Sheet Generator — “Can I generate a sheet without a script?” (read 2026-10-13)
Each character in a SceneMixer project is one entry with one approved image.
SceneMixer, The Same Face in Every Shot (read 2026-10-13)