DirectorLogic™

CORE PIPELINE LAYER

DirectorLogic™

Cinematic Reasoning

Every frame has a reason.

Story InputStoryCore™BeatMap™DirectorLogic™BioFrame™ProdScale™
“Cinematic decisions are not random. Every shot exists because the story demands it.”

What This Layer Does

DirectorLogic is where narrative structure becomes cinematic direction. This layer takes the beat skeleton from BeatMap and applies the full weight of StoryDirector's cinematic intelligence: shot role classification, camera grammar selection, physics activation decisions, emotional progression chaining, and visual blocking specifications.

DirectorLogic orchestrates the sub-systems that produce production-grade shot specifications. It calls VAOE for blocking, MOMA for escalation governance, LO for camera grammar distribution, ID for physics consequences, and KI for action intensity scoring. The output is a complete shot plan where every shot carries: a classified role (ENVIRONMENT_ESTABLISH, ESCALATION_TRIGGER, IMPACT_EVENT, etc.), camera specifications (focal length, stability, movement type, intensity), emotional state (enter → shift → exit), physics consequences, and continuity anchors.

This is where StoryDirector's intelligence is most visible. DirectorLogic is not generating content — it is reasoning about how content should be presented cinematically.

Receives

  • Beat skeleton from BeatMap™
  • Narrative constraints from StoryCore™
  • Film Grammar Profile (from story type + camera style selections)

Produces

  • Shot role classification per shot (11 possible roles)
  • Camera specifications per shot (focal length mm, stability rating, movement type, intensity, complexity)
  • Emotional progression per shot (enter state → shift → exit state)
  • Physics activation flags per shot
  • Continuity anchors between shots
  • Visual blocking specifications (via VAOE)
  • Escalation curve enforcement (via MOMA)
  • Camera grammar distribution (via LO)

Engine Output Example

DIRECTORLOGIC — Shot Plan (19 shots compiled)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

SHOT 7 — ESCALATION_TRIGGER
Duration: 5s | Location: desert road, eastern Syria
Camera    42mm lens | Handheld stability (6/10)
Movement  Push-in at 5/10 intensity | Complexity: 2/10
Motion    Dynamic action + dramatic weather
Lighting  Natural + motivated sources | Night

Emotional State
  Enter: determined → Shift: alarmed → Exit: resolute

Continuity  Vehicle position consistent with Shot 6
Physics     Dust displacement, suspension compression on impact
Action      "The convoy accelerates through the checkpoint"

Orchestration Modules Active:
  VAOE ✓  MOMA ✓  LO ✓  ID ✓  KI ✓

Actual engine output from a StoryDirector story compilation.

Why This Matters

Director's Notes

Without DirectorLogic, you have beats without direction — a story outline, not a shot plan. DirectorLogic is what makes StoryDirector a directing intelligence layer rather than a formatting tool. Every shot in the plan has a classified role, a justified camera choice, and an emotional trajectory. A DP reading this output could block the scene. A 1st AD could schedule the day. That's the standard DirectorLogic produces.

Technical Specifications

Classification

Deterministic (all orchestration is rules-based after V5.2)

Introduced

Engine 3.0.0, major upgrade in 5.2.0 (Cinematic Orchestration)

Dependencies

BeatMap™, StoryCore™; orchestrates VAOE, MOMA, LO, ID, KI

Outputs to

BioFrame™, Prompt Builder, Video Generation Pipeline

Determinism

Fully deterministic — same beats + same profile = identical shot plan

Related Layers

Experience DirectorLogic™ in action.