Reference Identity™

CONTINUITY & IDENTITY

Reference Identity™

Automatic Cast Consistency

Write the story. Your cast appears.

Written StoryDetectCreateApprovePersist
“Cast consistency begins in the prose, not in a prompt.”

What This Layer Does

People want themselves—and the characters they imagine—inside their films. The usual workflow asks them to build each character by hand, then remember to attach that character to every prompt. StoryDirector starts with the written story and does the work automatically.

Reference Identity detects the cast, creates an identity for each role, and brings those identities into Director Review. A creator can approve, customize, regenerate, or replace an identity with a photo. Upload your photo once, and the story can cast you.

Approval creates a durable lock. The identity travels with every eligible shot, survives the cut from one generation to the next, and can return in another story through the cast library. Detection. Identity creation. Element locking. Every-shot persistence. No prompt engineering required.

Receives

  • Cast detected directly from the written story
  • Character context and role relationships
  • Creator approval, customization, or regeneration
  • Optional one-click photo upload
  • Approved identities from the cast library

Produces

  • Reviewable identity candidates for detected cast
  • Creator-approved identity state
  • Registered reference lock for eligible generation
  • Every-shot identity persistence
  • Reusable cast-library identity across stories

Engine Output Example

REFERENCE IDENTITY — Lifecycle excerpt
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

DETECT    Story cast resolved
CREATE    Identity candidate prepared
REVIEW    Creator decision recorded
LOCK      Approved reference registered
ATTACH    Eligible shots receive identity
PERSIST   Cast-library record retained

[Representative lifecycle. Reference payloads and persistence schemas redacted.]

Representative structure from a StoryDirector compilation. Sensitive grammar is intentionally omitted.

Why This Matters

Director's Notes

Manual character systems can hold a likeness when a creator builds the character and tags every generation correctly. StoryDirector removes that prerequisite. It understands who belongs in the film from the story itself, creates the identity workflow, and keeps the approved cast present without asking the creator to become a prompt engineer.

Consistency is the visible result. Automatic casting from prose is the deeper advantage.

Technical Specifications

Classification

Automated cast detection + creator-approved identity + deterministic persistence

Creator Control

Approve, customize, regenerate, upload a photo, or reuse a cast-library identity

Dependencies

StoryCore™, DirectorLogic™, Director Review, cast library

Outputs to

Shot planning, generation preflight, every eligible dispatch

Persistence

Approved identities remain available across shots and stories

Related Layers

Experience Reference Identity™ in action.