Video Continuity, Canon, and Branch Lineage
Persistent narrative objects across shots, edits, generations, and community canon
A video project contains several truths:
- exact media bytes;
- logical shot and scene identity;
- character/object continuity;
- current edit;
- generated candidates;
- accepted canon;
- alternate branches;
- public/community decisions.
These must remain separate.
Continuity state
A recurring object can carry:
identity
appearance
wardrobe
damage
location
possession
emotion
lighting
relationships
last evidence
Every observation links to exact media intervals.
Candidate versus canon
A generated clip is a candidate. A creator, room vote, or declared canon policy may accept it. “Latest render” does not equal canon.
Branches
A branch records parent, fork event, included edits, audience, status, and merge rules. Personal runs, room-voted continuations, and creator-curated canon can coexist.
Address-stable editing
An operation targets logical objects and invariants:
replace SHOT_41
preserve EVENT_arrival
preserve character identity
preserve duration and dialogue sync
It does not rely only on timestamps.
Proof
The public surface can reveal lineage, source segments, generation settings at a safe abstraction, continuity checks, and acceptance receipt.
The graph helps a world remain coherent across edits without pretending that model generation is authoritative.
Source register
- N11-S01 — Content-addressable video/OOC-V corpus.
fractal-video.zip - N11-S02 — VideoWorlds canon corpus.
VideoWorlds project folder - N11-S03 — X-Splora production packet notes.
Pasted markdown.md