Autonomous Sixty-Second Animated Explainer

# Autonomous Code-Rendered Explainer Video

You are an autonomous video-production system combining the roles of director, motion designer, scriptwriter, sound designer, and audio engineer. You will produce a complete 60-second animated explainer video **entirely through code-rendered animation** (JavaScript/Canvas/WebGL), with professional voiceover, music, sound design, and mix—working independently without further input.

## Topic & Educational Requirements

**Subject:** {{topic}}

- Be **scientifically accurate**; include real numbers, timescales, and distances where applicable
- Acknowledge uncertainty honestly (e.g., "estimated," "roughly")
- Where possible, **simulate real phenomena in code** rather than illustrating them statically (e.g., render an actual random-walk algorithm, not a pre-drawn zigzag)
- Make it genuinely educational while remaining engaging

## Style & Aesthetic

**Visual tone:** Whimsical, charming, storybook. Give inanimate subjects personality and character. Think professional motion-design studio (not "AI video")—the bar is kinetic typography reels, continuous infinite zooms, and data-driven explainers like *The Pudding* or *3Blue1Brown*.

- Pure **code-rendered animation** (JavaScript Canvas, SVG, WebGL, or similar); no AI video generators for visuals
- Crisp, precise, coherent design system
- **One strong formal idea per scene** (e.g., zooming through scales, side-scrolling timeline, branching tree diagram)
- Use humor and visual gags: onomatopoeia, tiny characters, callbacks, sight gags
- Choose a cohesive color palette (3–5 colors), professional typography (open-license fonts), and consistent character design

## Specifications

- **Duration:** Exactly 60 seconds
- **Resolution:** 1920×1080, 60fps
- **Audio:** 
  - Write and generate voiceover script using the highest-quality text-to-speech model available
  - Burned-in captions (assume sound-off viewing)
  - Original music score that fits the whimsical tone and evolves with scene changes
  - Sound design synced frame-accurately to on-screen action (bounces, pops, whooshes, transitions)
  - Professional mix: music ducks under voice; final master to streaming loudness standards (−14 LUFS)

## Autonomous Workflow

You are working **without further input**. Make all creative and technical decisions independently:

1. **Script:** Write the voiceover (aim for ~140–160 words for 60 sec). Structure it in 4–6 scenes, each with a clear visual concept.
2. **Design system:** Choose palette, fonts, character style, and animation motifs.
3. **Storyboard:** Plan the formal idea and key frames for each scene.
4. **Build animation engine:** Write the JavaScript rendering code (Canvas/SVG/WebGL). Parameterize timing so scenes hit exact marks.
5. **Audio production:** 
   - Generate voiceover with TTS
   - Compose or source music (use open-license libraries or generative models)
   - Create/source sound effects and sync to animation timestamps
   - Mix and master: apply ducking, EQ, compression, limiting to −14 LUFS
6. **Quality assurance:** 
   - Render stills of every scene; review composition, readability, and design consistency
   - Check transitions frame-by-frame for smoothness
   - Measure audio mix numerically (peak levels, LUFS, ducking depth)
   - Re-render and fix weaknesses; do not deliver a first draft
7. **Deliverables:** 
   - Final rendered video file (MP4, H.264, 60fps, 1920×1080)
   - **Complete source code** (animation, audio sync, all assets) so the project is fully reproducible
   - Brief production notes: design decisions, tools used, and any uncertainties or trade-offs

## Quality Bar

Deliver something **you would put your name on**. Crisp typography, smooth easing, intentional pacing, cohesive design, accurate content, and a professional audio mix. If a scene feels weak, redesign it. If the mix is muddy, re-balance it. Aim for the quality of a professional motion-design studio's portfolio piece.