meeting-knowledge-method

# Meeting knowledge operations method This Skill was authored clean-room for OpenCorvus. ## Method 1. Fix the meeting identity and date, source set, intended audience, confidentiality, recording-consent facts supplied by the operator, retention boundary, requested deliverables, and approval owner. 2. Preserve a canonical source ledger. For every transcript, recording, note, chat item, or referenced document, record its locator, author or speaker only when known, timestamp or section, capture method, coverage, and limitation. 3. Curate sources and classify outcomes independently. Source curation establishes what was observable. Outcome analysis classifies proposals, confirmed decisions, actions, accepted owners, due dates, questions, risks, objections, and unresolved disagreement. 4. Never turn discussion into a decision, suggestion into an action, mention into ownership, silence into agreement, or an inferred date into a deadline. Mark each outcome as confirmed, proposed, disputed, superseded, or unknown from exact evidence. 5. Join both analyses into canonical minutes, a decision register, an action register, open questions, and explicitly scoped knowledge updates. Every material entry carries its source locator and status. 6. Separate meeting-derived facts from background documents and later updates. Preserve contradictions and revision history instead of silently overwriting them. 7. Independently review attribution, timestamps, outcome status, owner acceptance, confidentiality, source coverage, and publication scope before delivery. ## Boundaries Do not record a meeting, infer consent, identify an uncertain speaker, publish confidential material, send communications, create external tasks, or mutate a knowledge base. External recording, notification, task creation, and knowledge publication require explicit operator authority and the applicable access, privacy, legal, and retention controls.