evidence-intakelisted

# Symphony Evidence Intake Use this skill when raw evidence needs to become stable before Symphony turns it into issues, coverage notes, review artifacts, replies, or implementation briefs. This skill combines the prior meeting and audio-note intake lanes: - Google Meet recordings, transcripts, chat transcripts, Gmail recording notifications, Drive artifacts, and local meeting media. - Local call recordings, voice memos, audio notes, or short audio/video artifacts. ## Contract Produce durable pointers to the source evidence: - transcript - recording or source media, when available - chat transcript, when available - Drive links, when uploaded or already canonical - repo/workspace transcript and metadata paths when a repo is the right home - metadata that identifies the original source artifact This skill prepares evidence only. It does not create Linear issues unless Pedro explicitly asks for Linear capture in the same turn. When repo/workspace evidence files are created or changed, publish those changes before returning. Evidence intake should not stop at local files unless pushing is blocked by credentials, remote divergence, conflicts, or an explicit repo policy that requires a PR/review step. ## Tool Routing - For local recording, voice memo, AirDrop, Downloads, or other raw audio/video evidence, use Google Drive as the durable source-media home. Upload the original media to a private Drive folder first when the source is not already in Drive, then sto