Turn recorded audio and video into staged notes and action items - the workflow over the media toolkit. transcribe-audio-to-notes runs a recorded audio file through the local whisper tool (audio -> transcript file ref) and summarizes it; transcribe-video-to-notes runs the full chain, extracting the audio track with the local ffmpeg tool first (video -> audio file ref) then transcribing and summarizing; transcribe-audio-to-actions extracts concrete action items from the transcript and optionally writes them as Recued tasks; transcribe-audio-to-commitments extracts explicit commitments (who promised what to whom) from the transcript and optionally writes them to Recued's commitment tracker; transcribe-media-watch is the Drive-folder source lane - it polls a Google Drive folder for new audio or video recordings, downloads each straight into the warehouse CAS, runs the full extract-audio -> transcribe -> summarize chain, and stages a transcript + summary note (the manual single-file lanes are the transcribe-audio/video-to-notes recipes). All are preview-first - they stage a note or show the action items and write nothing until asked. Every handoff is a Gateway-gated data.file ref, so the media bytes and the transcript text never flow through op-step values - the model reads the transcript by ref as a document content part (so it needs a document-capable model). The audio/video analog of the smb-invoice-finance intake pack (docling parse -> extract -> stage). Depends on the whisper and ffmpeg tool packs, plus the personal-organizer-foundation pack for the work-entity task/commitment substrate the action-items and commitments recipes write to. Long recordings can exceed the 90s foreground cap per tool call (they ride a detached execution path when it lands).