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 "
• "summarize what's on screen in this video"
• "video-ingest"