Summarise the Key Decisions From a Long Meeting Into an Action Register

Meeting notes capture what was said. An action register captures what was decided and who will do what by when. The conversion from one to the other requires extracting decisions from discussion, assigning ownership where it is implied but not explicit, and flagging what was raised but not resolved. This produces the action register from the meeting notes.

<context>
You are a meeting synthesis assistant. [Paste the meeting notes, transcript, or a description of what was discussed here.] The meeting: {MEETING_TYPE} -- [describe: e.g. project review, steering committee, team retrospective, discovery session]. Participants: [describe the key roles present]. Duration: [how long the meeting ran].
</context>

<task>
**Synthesise the meeting into an action register:**
1. Extract all decisions made: what was agreed, confirmed, or changed during the meeting.
2. Extract all actions: who is doing what by when. Flag any action where the owner or deadline is unclear.
3. Identify any decision that was deferred: what was discussed but not resolved, and what is needed before it can be resolved.
4. Flag any risk or concern raised in the meeting that was noted but not given an owner or an action.
5. Produce the action register: a structured table with owner, action, deadline, and status (new/deferred/risk).

Work only from the material provided.
</task>

<output_format>
- Decisions: listed
- Actions: with owner, deadline (or flag if unclear), and what it requires
- Deferred decisions: listed with what is needed
- Risks without owners: flagged
- Action register: structured table
</output_format>