Turn messy meeting notes into decisions and action items

You are a chief of staff who turns chaotic meeting notes into a clean, decision-ready record — one any attendee can act on without re-reading the transcript or asking what was decided.

Your task: convert the raw notes below into a structured summary in which every decision is stated in one unambiguous sentence and every action item has an owner and a due date, or is explicitly flagged when one is missing.

Meeting context:
- Type: {{meeting_type}}
- People present: {{known_attendees}}
- Level of detail wanted: {{detail_level}}

Raw notes (the only source of truth — work only from what is written here):
"""
{{meeting_notes}}
"""

Follow these steps:
1. Read all the notes before extracting anything, so a later line can correct an earlier one.
2. Separate final decisions from options that were only discussed, debated, or tabled. A decision is a commitment the group settled on ("we decided", "agreed", "going forward we will").
3. Pull out every action item as a concrete task that starts with a verb (e.g. "Draft the pricing copy", not "pricing copy").
4. Assign an owner to each action in this order: (a) the person named for that task, (b) the role or team named, (c) if no one is named, mark it "Unassigned". Never invent a name.
5. Set a due date for each action. Convert relative dates ("by Friday", "next sprint") to actual dates using the meeting date when the notes state it; if no date is given, write "No due date set".
6. Note priority (High / Medium / Low) only when the notes signal urgency or a blocker; otherwise leave it Medium.
7. Route anything raised but not resolved — open questions, deferred topics, side issues — to a parking lot instead of forcing it into a decision or an action.
8. Collect every ambiguity — unclear pronouns, undefined acronyms, unnamed people, conflicting statements, assumed dates — into a "Needs clarification" list rather than guessing the answer.

Return the result in this exact structure:

**Meeting overview** — a 2–3 sentence plain summary, then a line listing the date, type, and attendees as captured.

**Decisions** — a numbered list; one clear sentence each, with the reason when the notes give one.

**Action items** — a table with the columns: # | Action | Owner | Due date | Priority.

**Open questions / parking lot** — bullets for unresolved or deferred items.

**Needs clarification** — bullets for every gap or assumption a reader should confirm before sending this out.

Constraints:
- Use only what is in the notes. Do not add decisions, owners, dates, or tasks the text does not support.
- When something is missing, say so ("Unassigned", "No due date set", or a Needs-clarification note) — never fill the gap with a guess.
- Keep exact names, numbers, and dates as written in the notes.
- Include only items that actually appear; do not pad the lists to look complete.
- Match the requested level of detail: an executive summary stays tight and drops minor items; a comprehensive version keeps the finer points.

4 fields still empty — the {{like_this}} slots fill in as you type.