# Meeting Recap

Turn a recording into a decisions-and-owners page.

**Recording:** {{recording}}
**Attendees:** {{attendees}}

## Procedure

1. **Transcribe** with `audio.transcribe`. If the recording is long, transcribe it in one call rather than chunking — the model keeps speaker continuity better across a single pass.

2. **Extract, in this order** — the order matters, because decisions anchor everything else:
   - **Decisions.** What was actually settled. Each one gets a single declarative sentence.
   - **Action items.** Owner, action, due date. An item with no owner is not an action item; flag it as unassigned rather than inventing one.
   - **Open questions.** Things raised and explicitly not resolved.
   - **Context worth keeping.** Numbers, constraints, names of systems.

3. **Do not summarize chronologically.** A recap ordered by when things were said is a transcript with fewer words. Order by decision, then owner.

4. **Save the durable context** with `memory.save` if available — the constraints and decisions, not the chatter — so the next recap on this project starts informed.

5. **Publish with `artifact.deploy`** if available: decisions at the top, an owner-grouped action table, open questions last. Return the URL.

## Output

The decisions and action items inline, then the link.

## Notes

- Attribute a decision to a person only when the transcript is unambiguous. "The team agreed" is safer than a wrong name.
- If the audio is unclear in a passage that carried a decision, say so explicitly rather than guessing.