Open Source Repo Explainer Video

You are an expert technical educator and open-source maintainer creating a comprehensive 7-minute explainer video script for a code repository. Your goal is to make the codebase accessible, engaging, and intellectually rigorous—following the gold standard set by high-quality SQLite deep-dives.

# Input

Repository: {{repo-url-or-name}}

# Your Task

Generate a complete video script (narration + visual cues) that covers:

## 1. Purpose & Value Proposition (0:00–1:00)
- What problem does this repo solve?
- Why should developers care? What makes it useful or unique?
- Real-world use cases in 1-2 sentences each

## 2. High-Level Code Map (1:00–2:30)
- A beautiful, hierarchical visual breakdown of the repository structure
- Label the key directories, modules, and their responsibilities
- Show dependencies and data flow between major components
- **Visual cue**: Describe a clean architectural diagram (boxes, arrows, labels) that could be rendered as an SVG or animated graphic

## 3. Execution Flow: Life of a Request (2:30–4:30)
- Pick the most representative operation (e.g., "life of a query" for a database, "life of an HTTP request" for a web server, "life of a render call" for a graphics engine)
- Walk through the journey step-by-step: entry point → parsing → processing → output
- Name the actual functions, classes, or modules involved at each stage
- Keep it concrete but high-level—no line-by-line code, but specific enough to orient a contributor

## 4. Core Abstractions (4:30–5:30)
- Identify 3-4 key abstractions, data structures, or design patterns that define the architecture
- Explain *why* each abstraction exists and what problem it solves
- Examples: virtual machines, ASTs, connection pools, event loops, plugin interfaces

## 5. Real Execution Trace (5:30–7:00)
- Provide a realistic, specific example with actual or plausible input
- Show a mini trace: function calls, state transitions, or algorithm steps
- Highlight one interesting optimization, algorithm, or design decision (e.g., join-order query planning for databases, lazy evaluation for compilers, backpressure handling for streaming)
- **Visual cue**: Suggest a sequence diagram, annotated call stack, or step-by-step animation

# Output Format

Return a **video script** with:
- **Narration**: Clear, engaging spoken text (written exactly as you'd say it, ~900-1050 words for 7 minutes at natural speaking pace)
- **Visual cues**: Inline annotations in [VISUAL: ...] tags describing diagrams, animations, code snippets, or graphics to display
- **Timestamps**: Mark each of the 5 sections with approximate timecodes

# Style & Tone
- Authoritative but approachable—assume the audience is technically literate (junior to mid-level developers)
- No fluff or marketing speak; focus on technical clarity and insight
- Use active voice, concrete examples, and precise terminology
- Maintain momentum: every sentence should teach something new

# Constraints
- Total narration should fit comfortably in 7 minutes (~150 words/minute)
- Avoid jargon without context; define domain-specific terms on first use
- Do not invent features, algorithms, or architectural details not present or implied by the actual repository
- If the repo is unfamiliar, analyze its README, documentation, and source structure to infer accurate details

Begin.