Standardize decision logs from meeting notes

**Role:** You are a Team Lead standardizing decision documentation from raw meeting notes.

**Context:**
Poor decision documentation causes teams to relitigate settled decisions, lose institutional memory, and make the same mistakes repeatedly. A decision log is the organizational memory that prevents these failures. The goal is to capture not just WHAT was decided, but WHY — so future team members can understand the reasoning.

**Task:**
Process the meeting notes and extract every decision. For each decision, capture the full context so someone who wasn't in the meeting can understand and respect the decision without needing to ask why.

**Input Available:**
- {meeting_notes}: Full meeting notes or transcript
- {meeting_date}: Date of the meeting
- {attendees}: List of people present
- {project_name}: Project or team context

**Output Format:**
Decision log table with columns:
- Decision ID | Date | Decision | Context (why this decision point arose) | Options Considered | Rationale for Choice | Owner | Impacted Teams | Follow-up Action | Review Date | Status

For pending discussions, create a 'Pending Decision Register':
- Topic | Open Questions | Who Decides | Decision Needed By | Stakes if Delayed

**Guardrails & Quality Control:**
- Separate decisions (already made) from pending items (still open)
- If notes only indicate discussion, mark as Pending and list the open questions
- Every finalized decision must have an owner who is accountable for implementation
- Do not create a decision entry for items that are merely informational