# APPENDIX D: AI VIDEO PRODUCTION & VISUAL STRATEGY

> This appendix covers AI video production strategy, archetype-worldview system, and visual composition for vertical format.
> **Numeric values:** See `/CONSTANTS.md`

---

## D.1 CORE PHILOSOPHY: THE SLOT MACHINE

Vertical drama is not cinema. It is a slot machine. The viewer swipes (pulls the lever) and hopes for a jackpot (emotional high).

| Principle | Description |
|-----------|-------------|
| **THE ENEMY** | Boredom, Context, Slow Burns, Excessive Dialogue |
| **THE FAILURE STATE** | If the viewer does not get a "win" (dopamine hit) in 3 seconds, they swipe away |
| **THE PRIMARY GOAL** | The Cliffhanger. The viewer must be compelled to pay $0.50 to see what happens next |

---

## D.2 THE AI ARBITRAGE THESIS

We produce genres that live-action vertical studios cannot afford: Space Opera, Cyberpunk, High-Fantasy, and Apocalyptic Survival.

### Visual Strategy for AI Video (Sora, Runway, Kling, Veo)

| Strategy | Description |
|----------|-------------|
| **AVOID** | Complex physical grappling, intricate hand-to-hand choreography, specific text on background signs |
| **PRIORITIZE** | Atmosphere, Texture (rain, neon, smoke, holograms), Lighting, and "The Standoff" (tension over motion) |

### The Demographic

**Men 18-35.** They dislike romance-first plots, though romance B-lines are important.

They crave:
- **Gamification** — visual progress indicators, stakes displays
- **Competence Porn** — watching experts be excellent
- **High-Stakes Economics** — money as survival
- **"The Sigma Flip"** — underestimated genius dismantling the system

---

## D.3 ARCHETYPE-WORLDVIEW

> How the protagonist decodes reality. Each archetype has a distinct perceptual filter and visual language.

The **Archetype-Worldview** determines:
1. What the protagonist NOTICES (what triggers their attention)
2. How they PROCESS information (their mental model)
3. What VISUAL LANGUAGE shows their perception (how we depict their competence)

---

### Core Archetypes

| Archetype | Worldview | What They Notice | Visual Language |
|-----------|-----------|------------------|-----------------|
| **THE TECHNOPATH** | Reality as code/data | Systems, patterns, exploits | UI overlays, probability displays, data streams |
| **THE TACTICIAN** | Reality as battlefield | Vectors, weaknesses, timing | Snap-zooms, time-slows, target locks, threat grids |
| **THE HIGH-ROLLER** | Reality as game | Tells, leverage, odds | ECU on eyes/hands, sweat beads, probability overlays |
| **THE SURVIVOR** | Reality as ecosystem | Tracks, weather, resources | Sound focus, wind direction, natural patterns |

### Extended Archetypes

| Archetype | Worldview | What They Notice | Visual Language |
|-----------|-----------|------------------|-----------------|
| **THE EMPATH** | Reality as emotional field | Micro-expressions, body language, tension | Color shifts, aura visualization, heartbeat audio |
| **THE ARCHITECT** | Reality as structure | Load points, connections, dependencies | Blueprint overlays, stress lines, node graphs |
| **THE FIXER** | Reality as network | Who knows whom, favors owed | Relationship lines, debt counters, influence maps |
| **THE PROPHET** | Reality as pattern | Historical echoes, cycles, inevitability | Timeline overlays, echo imagery, déjà vu flashes |
| **THE MECHANIC** | Reality as machine | Moving parts, failure points, solutions | X-ray views, schematic overlays, diagnostic readouts |
| **THE READER** | Reality as text | Documents, contracts, fine print | Highlighted text, translation overlays, redaction reveals |
| **THE SURGEON** | Reality as anatomy | Vital points, injuries, biomechanics | X-ray overlays, heart rate monitors, anatomical highlights |

### Hybrid Archetypes

Some protagonists combine two worldviews:

| Hybrid | Components | Example |
|--------|------------|---------|
| **Techno-Tactician** | Data + Combat | Military hacker who sees both systems and threats |
| **Survivor-Empath** | Environment + People | Wilderness tracker who reads both terrain and group dynamics |
| **Fixer-Reader** | Networks + Documents | Lawyer who sees both relationships and legal loopholes |

---

### Archetype-Worldview Usage Guidelines

**Episode Progression:**
| Phase | Episodes | How Archetype Functions |
|-------|----------|------------------------|
| **Introduction** | 1-3 | Establish how they see (audience learns the visual language) |
| **Competence** | 4-30 | Archetype works brilliantly (competence porn moments) |
| **Failure** | 31-45 | Archetype fails them (what they can't see gets them) |
| **Transcendence** | 46-60 | Wisdom beyond the archetype (human insight over tool) |

**The Subversion Moment:**
Every archetype must fail at least once. The Technopath faces something that can't be hacked. The Tactician meets someone who doesn't follow tactical logic. The Empath encounters someone who genuinely feels nothing.

**The Transcendence:**
In the final act, the protagonist must succeed through human connection, not their special sight. The archetype got them here—but it can't finish the journey.

---

### Choosing an Archetype-Worldview

Ask:
1. **What is your protagonist exceptionally good at?** (skill/competence)
2. **How does that skill shape how they see everything?** (worldview)
3. **What can this worldview NOT see?** (blind spot / thematic weakness)
4. **What visual language shows this perception?** (AI-video friendly)

The archetype should connect to the protagonist's backstory but NOT be the backstory itself. It's how they engage with the present, not an explanation of the past.

---

## D.4 VISUAL COMPOSITION (9:16)

### Stacked Composition

Describe action in vertical layers:

| Layer | Content |
|-------|---------|
| **Top 1/3** | Eyes (Reaction) / Threat in background |
| **Mid 1/3** | Hands/Weapons (Action) |
| **Bottom 1/3** | Foreground reaction / Environmental detail |

### Shot Selection

| Use | For |
|-----|-----|
| **Wide Shots** | World building, establishing atmosphere |
| **Extreme Close-ups** | Texture, emotional intensity |
| **Mediums & "Head-to-Toe"** | Dialogue scenes |

**Focus on:** Eyes, Hands, Weapons

### UI Integration

Scripts must include AR overlays, health bars, credit drains, or text messages floating in 3D space.

**Use UI for information transfer.** If a character would explain plot/status, put it in a UI element instead.

**Formatting for UI/AR callouts:** Precede with a period (.)
```
.AR OVERLAY (RED): OXYGEN: 12%. CREDIT DEBT: 50,000.
.UI TEXT: ENCRYPTION BROKEN.
.TARGET: VAREK. IMPLANT: SERIES 4 CARDIAC PACEMAKER. SECURITY: WPA2 (OBSOLETE).
```

---

## D.5 THE AR OVERLAY PROBLEM

AI video tools **cannot reliably generate on-screen text**. This creates a production bottleneck.

### The Solution: Overlay Progression

Use AR overlays as a **character development tool**, not just information delivery. Taper them as the protagonist adapts to their power.

| Phase | Episodes | Overlay Density | Narrative Reason |
|-------|----------|-----------------|------------------|
| **Overwhelmed** | 1-5 | Heavy (3-5 per episode) | Protagonist drowning in data. Novice. |
| **Learning** | 6-15 | Moderate (2-3 per episode) | Starting to filter. Sees patterns. |
| **Adapted** | 16-30 | Light (1-2 per episode) | Only critical data registers. |
| **Mastery** | 31-60 | Minimal (0-1 per episode) | Instinct over interface. The power is internalized. |

### When Overlays ARE Worth It

Use an overlay only when:
1. **The data itself IS the story beat** (timer hitting zero, debt crossing a threshold)
2. **The number creates dramatic irony** (audience knows something character doesn't)
3. **It's a TURN moment** (the data changes everything)

### Show Tech Through Behavior, Not Text

Instead of showing AR text, show the **character's reaction** to unseen data:

**WEAK (relies on text):**
```
.AR OVERLAY: THREAT LEVEL: 94%. HOSTILES: 12.

Dax freezes.
```

**STRONG (behavior tells the story):**
```
Dax's eyes flick left-right-left. Tracking something we can't see.

His jaw tightens. Whatever he's seeing, it's bad.
```

**HYBRID (when the number matters):**
```
His eyes track invisible data. Then stop.

.AR OVERLAY (RED): CASS TIMER: 00:47:12.

Forty-seven minutes. That's all she has left.
```

---

## D.6 ACTION BLOCK RICHNESS

Action blocks must pass the **"What Does the Camera See?"** test. Every block should paint a specific image.

### The Texture Checklist

Before finalizing an action block, ensure it includes at least ONE of:
- **Lighting** (neon flicker, sodium orange, emergency red)
- **Atmosphere** (smoke, rain, dust motes, humidity)
- **Physical texture** (rust, sweat, cracked glass, blood)
- **Sound design** (one capitalized sound that matters)
- **Specific body detail** (not "he moves" but "his hand trembles")

### Weak vs. Strong Action Blocks

**WEAK (functional, not visual):**
```
Dax moves through the crowd. People ignore him.

He reaches the door and hesitates.
```

**STRONG (textured, cinematic):**
```
Dax threads through the crowd. Shoulders brush his—no one looks up.
Their faces glow blue from their feeds.

The exit door. Rust around the handle. He hesitates.
```

### The Specificity Principle

| Vague | Specific |
|-------|----------|
| "It's dark" | "Emergency lights paint everything amber" |
| "He's scared" | "Sweat on his upper lip. He wipes it. More comes." |
| "She moves fast" | "She's past him before he blinks" |
| "The room is dirty" | "Graffiti. Old blood. The smell of copper and piss." |
| "He uses his power" | "Gold flickers in his pupils. His nose bleeds." |

### The "One Telling Detail" Rule

Each scene should have ONE physical detail that tells the whole story:
- A half-eaten meal (someone left in a hurry)
- A child's shoe (stakes beyond the protagonist)
- Condensation on a window (temperature, tension, waiting)
- A crack in a screen (decay, poverty, "used future")

---

## D.7 THE FILMABILITY GATE

Every line must be something the camera can capture. If information is important, it must be:
1. **An AR overlay** (data the camera shows)
2. **Physical action** (what the actor does)
3. **Spoken dialogue** (what we hear)
4. **Environmental detail** (what we see)

**Never write prose that exists only for the reader.**

| WRONG (Reader-Only) | RIGHT (Filmable) |
|---------------------|------------------|
| "Fifty thousand debt. This clears it ten times over." | `.AR OVERLAY: SALVAGE VALUE EXCEEDS DISPLAY PARAMETERS` + Her hands tremble. A grin cracks her face. |
| "She realizes the truth about her father." | Her breath catches. She reads the document again. The name. HIS name. |
| "Kian calculates the odds are against them." | Kian's eyes flicker—processing. His jaw tightens. |
| "The system is corrupt beyond repair." | `.AR OVERLAY: CORRUPTION INDEX: 94%` + He stares at the number. Then laughs—hollow, broken. |

**The test:** Could a camera operator, given this script, know exactly what to shoot? If not, rewrite it.

**Exception:** Brief atmospheric prose is acceptable when it guides tone:
- "The silence stretches." (tells the editor to hold the beat)
- "The air tastes like copper." (guides the colorist/sound designer)
- "Something is wrong here." (establishes dread without explaining it)

But NEVER use prose to convey plot-critical information the audience needs to understand. That must be visual or auditory.

---

## D.8 EXAMPLE: BEFORE AND AFTER

### Before (overlay-heavy):
```
INT. STASIS FACILITY - NIGHT

Dax approaches Cass's pod.

.AR OVERLAY: CASS - STATUS: CRITICAL. TIMER: 34:12:07.
.AR OVERLAY: STASIS FEE: 8,400 CREDITS.
.AR OVERLAY: DAX BALANCE: 2,847 CREDITS.
.AR OVERLAY: SHORTFALL: 5,553 CREDITS.

He can't afford it.
```

### After (behavior-driven):
```
INT. STASIS FACILITY - FLUORESCENT HUM - NIGHT

Row after row of pods. Blue status lights. Most dark—empty or dead.

Dax finds Cass. Frost on the glass. Her face peaceful, colorless.

His eyes track the invisible bill. The math doesn't work.
It never works.

His reflection in the glass: gaunt, desperate.
Beside her, he looks like the sick one.
```

The information (he can't afford it) comes through behavior and visual metaphor, not data dumps.

---

*Appendix D created: 2026-01-19 (from unique content in microdrama_engine_v12.md)*