meeting-to-actionslisted

# meeting-to-actions ## Purpose Turn meeting content into a compact action record without making the user reread the whole transcript. ## Use For - Zoom transcripts - Meeting notes - Slack threads - Email chains - Doc comment threads - Ticket discussions - Post-meeting cleanup - Preparing follow-up messages or ticket updates ## Inputs - Zoom transcript - Notes - Agenda - Related ticket or doc context when useful - A `reduce-to-facts` ledger or conversation-state record ## Guardrails - Read before write. - Do not send follow-ups or update tickets unless explicitly asked. - Separate decisions made from open decisions. - Name owners and dates only when the source supports them. - Surface missing owners, due dates, and unclear blockers. - Do not dump raw transcript content by default. ## Portable Output Contract - Use only the useful subset of source-backed facts, assumptions, source gaps, stakeholder sensitivities, potential misreads, and the suggested next action. - Use the smallest useful output. - Label assumptions and preserve source gaps, source anchors, and confidence labels. - When consuming upstream state, do not promote an assumption, inference, open question, proposed action, or stakeholder position into a fact, decision, commitment, owner, or deadline without new source support. - Keep unresolved approvals, owners, timing, and blockers explicit in the action record. - Do not send, publish, update tickets, create events, or mutate systems unless explici