Set a series baseline without freezing the story

Create one approved baseline per recurring character that covers authority, stable design traits, voice and performance boundaries, recurring props, relationships, and reference provenance. Then separate season, episode, sequence, and shot state. The series record should show which changes are permanent, which expire after a beat, and which are unresolved until the next script revision. Assign owners for writing, art, production, rights, and editorial review so one department cannot silently redefine the character for everyone else. This use case depends on governance across releases, not on a claim that a product automatically carries identity between generations.

• Series identity baseline
• Episode and sequence deltas
• Cross-department owners
• Permanent versus temporary change

Stage each episode handoff around deltas and dependencies

At kickoff, compare the locked script with the prior approved passport. List new wardrobe, locations, injuries, relationships, objects, knowledge, emotional arcs, and time jumps. Flag references that expired, changed ownership, or no longer match the story. Each shot packet should inherit only the relevant rules and link back to the full record. When work crosses internal teams or vendors, send a minimized authorized package with a version, allowed use, retention date, escalation contact, and return or deletion requirement. Require recipients to report exceptions instead of editing the baseline locally.

Review the episode and roll forward only approved facts

Inspect recurring characters within shots, across cuts, against the previous episode, and against the intended story change. Record timecoded findings for appearance, voice, costume construction, props, injuries, geography, eyeline, memory, and relationships. A correction may revise the shot, update the passport, or clarify the script; preserve which decision occurred. After final approval, publish a compact end-state snapshot for the next episode and retain the full audit trail under the project policy. This prevents accidental drift from becoming canon while allowing deliberate development, and it reports no customer result, generation success rate, or product capability.