Character Reference Binding

1. Activation & Scope

  • Status: Inactive by default.
  • Activation Command: Activated strictly upon explicit user command (e.g., “Use character reference mapping”, “Bind actor references”, “Include multimodal character mapping”).
  • Scope: Governs how reference tags (@actor, @image, @audio) are assigned, bound to narrative personas, and structured within the script without contaminating downstream prompt blocks.

2. Reference Binding Syntax in [INTENT]

Bind multimodal assets directly to character personas exclusively in the opening definition:

  • Format: @actor1 as NAME, [brief profession / archetype / trait] (or @image1 as NAME...)
  • Examples:
    • @actor1 as SAMIRA, an exhausted artist hiding deep depression
    • @actor2 as FELIX, her gentle, reliable long-time friend
    • @image1 as MARK (voice: @audio1), a frustrated junior mathematics professor
  • Mandate: Always assign a concrete character name and a clear profession, archetype, or role to every referenced material.

3. Strict Scope Rule: Tag Isolation in [INTENT] Only

  • Intent-Only Declaration: Use @actor / @image tags exclusively inside [INTENT].
  • Downstream Usage: In all subsequent blocks—[LOGIC], [AESTHETIC], [OPENING], and [EXECUTION]—refer to characters strictly by their established character names (e.g., Samira, Felix, Mark, Robert).
  • Never Repeat Reference Tags: Never write @actor1 or @actor2 inside [LOGIC], [AESTHETIC], [OPENING], or [EXECUTION]. Once bound in [INTENT], the name is the sole canonical identifier across the entire script.

4. Placement Standards

Reference declarations can be structured in one of two ways based on scene complexity:

Standard Approach (Inline in [INTENT])

For standard scenes (1–3 characters), embed bindings directly into the flowing introductory sentence of [INTENT]: [INTENT] Create a cinematic drama scene featuring @actor1 as SAMIRA, an exhausted painter, and @actor2 as FELIX, her loyal studio partner, inside a rain-soaked laundromat...

Dedicated Block Approach ([CHARACTERS] or [REFERENCES])

When directing large ensembles (4+ characters) or complex character sheets with distinct reference attributes, insert a dedicated block before [AESTHETIC] or [OPENING]:

[CHARACTERS]
@actor1 as EVAN: 30s explorer, weathered features, weary posture.
@actor2 as FELIX: 20s scholar, wire-rimmed glasses, gentle demeanor.
@image1 as THE BEAST: Colossal petrified skeletal stag with obsidian antlers.

(Even when using a [CHARACTERS] block, downstream blocks [LOGIC], [AESTHETIC], [OPENING], and [EXECUTION] must use only the character names Evan, Felix, The Beast).

5. Multimodal Assignment Rules

  1. One Explicit Role Per Material: Assign each reference material to exactly one narrative subject. Do not overload a single asset across multiple active characters.
  2. Cardinality Alignment: A single-person reference image must represent only one person on screen. Use multi-person references only when the reference image itself depicts an established group.
  3. Preserve User Reference Labels: Never alter user-supplied reference identifiers (e.g., if user writes @actor1, preserve @actor1 exactly).
  4. Declaration of Unused Materials: If multiple reference assets are provided but only a subset are active in the scene, list unused assets under an [Unused Materials] block or footnote to prevent downstream AI hallucination.

6. Directorial Integration & Reference Exhibits

  • intent.md — Structural block specification for [INTENT] and reference tag isolation.
  • block_rules.md — Open Block registry and optional [CHARACTERS] block placement.
  • seedance25_dialogue_script.md — Verified production script demonstrating @actor1 as SAMIRA and @actor2 as FELIX in production.
Back to top