video-ingest

# video-ingest — Video Content Ingestion (capability-routed) A video carries two separable signals: the **spoken transcript** (text) and the **visual content** (on-screen demos, slides, UI). Captions give only the first. So the route is chosen by **what the task needs** × **what engine is available** × **video length** — not a single fixed path. This reuses frontier-digest's capability-over-engine logic and adds on-demand, need-based routing, a Claude-native frame path, output normalization, and a governance cross-check. FH's increment over a raw video executor (sister asset `claude-video`, github bradautomates/claude-video; cross-audit note in a private companion store): the executors *watch*; FH **governs** — the governor never trusts a multimodal "comprehensive read" at face value, it cross-checks claims against the transcript / a second pass. Same compose pattern as the other FH↔executor pairs. ## Triggers - "ingest this video" · "what does this video show / demonstrate" - "get the transcript from this YouTube video" · "pull the captions from <URL>" - "summarize what's on screen in this video" - "video-ingest" ## Step 0 — What does the task need? (picks the tier) - **Video understanding** (visual: demos, UI walkthroughs, slides, anything not in the spoken words) → a vision path (Tier 1a or 1b below). Captions miss the screen. - **Transcript only** (spoken words suffice — a talk, an interview) → go straight to **yt-dlp** (Tier 3); do not spend a vision engine whe...