demo-recorderlisted

# Demo Recorder Follow this state machine: `INTAKE -> BRIEF_APPROVED -> PREFLIGHT -> NARRATION_READY -> SHOT_READY -> CAPTURED -> ASSEMBLED -> VALIDATED` Do not skip states. After approval, continue through validation unless a permission, credential, or app state blocks execution. Keep updates to: current state, artifact, blocker. **Default product-video rule:** tutorials, demos, walkthroughs, troubleshooting videos, and release recaps must show the real application being used. Capture the actual user flow—navigation, clicks, typed input, uploads, selections, and visible results—as live footage. A screenshot, generated slide, static image, or frozen frame is never a substitute for app-feature footage. It is permitted only for a user-approved non-product section such as a title card, transition, or closing card. ## 1. Intake Reuse supplied facts. Ask once, in one compact message, only for missing decisions: - type: tutorial, demo, walkthrough, pitch, troubleshooting, or release recap - audience; outcome or call to action - must-show and must-avoid content, especially private data - runtime, video count, and output format - narration: live, OpenAI, ElevenLabs, or macOS `say` - style: practical, polished, sales-oriented, or exploratory If the user delegates a choice, propose a default in the brief. Never re-ask answered questions. Tailor the structure: | Type | Structure | | --- | --- | | Tutorial | orient -> numbered steps -> verify result | | Demo | outcome -> key ac