Every character-consistency guide says the same thing: use reference images. Teams follow the advice and still watch their protagonist drift across scenes — different face in scene nine, wrong jacket in scene twelve. References help, but consistency is not a prompting trick. It is an identity-governance problem spread across dozens of scenes and several contributors.
Why reference images alone fail
- References multiply: each scene generates new near-canonical images that compete with the original.
- State is unrecorded: nobody wrote down which jacket, which lighting, which injury the character carries.
- Contributors differ: three artists interpret the same reference three ways without a canonical checklist.
- Approvals blur: was scene nine approved against the character bible or against scene eight?
The identity stack
Maintain one canonical identity record per character, product, or environment. Attach approved references with version dates. Record scene state changes such as costume, setting, and condition. Link each scene to the identity through lineage, then review new scenes against the record. The Character continuity governance workflow shows how.
Scene production protocol
- Open the canonical identity record, not last week’s render.
- Confirm current state (wardrobe, setting, condition) before generating.
- Generate with approved references pinned; record any new reference as a candidate, not a replacement.
- Review the scene against the canonical checklist, then against adjacent scenes.
- Link the scene asset to the identity with its state snapshot.
Continuity governance checks
What to verify per scene
| Check | Source of truth | Failure mode |
|---|---|---|
| Visual identity | Canonical references | Face, build, or product drift |
| State continuity | State record | Wrong wardrobe, setting, condition |
| Reference authority | Approved reference set | Rogue references competing |
| Approval basis | Decision history | Approved against the wrong baseline |
Implementation checklist
Character-consistency checklist
- Create canonical identity records for every recurring entity.
- Version approved references; never let candidates compete silently.
- Track state as data on each scene asset.
- Review against the canonical record first, neighbors second.
- Measure continuity corrections per scene over time.
What to measure in a paid pilot
Track continuity review time and corrections per scene before and after identity governance. Scope a production pilot around those measures.
Start with the workflow assessment to find where your team loses context today, read the Production Memory guide, and browse the use-case library for related workflows.
Key takeaways
- Consistency = canonical identity + approved references + state + history + lineage.
- Reference images alone drift; governance around references is what holds.
- Track state (wardrobe, setting, condition) as data, not memory.
- Review continuity per scene against the canonical record, not the last render.