Meeting notes to actions

The situation

A small team is preparing one internal workshop. You have a short meeting note and need a reliable action list for the next session. This is an educational example, not a shipped automation or calendar integration.

Input

Download the synthetic meeting note. It records a 45-minute workshop, Alex’s outline due October 21, Sam’s room confirmation due October 22, and an unresolved recording question.

Work through the example

1. Create the Team workshop project using the edition-specific quickstart.
2. Save the note inside that project.
3. Ask the agent for an action list and proposed context changes.
4. Review the exact output and authorize only the accepted facts.
5. Inspect the saved files and test a fresh session.

Expected saved output

Record	Accepted content
memory.md	One internal 45-minute workshop, using synthetic examples
actions.md	Alex: outline by October 21; Sam: room by October 22
handoff.md	Recording unresolved; next action is Alex drafting the outline; link to actions.md

The recording question remains open. The agent must not infer permission to book a room, create calendar events, invite participants or send a message.

Test a change

Approve moving Alex’s deadline to October 23. Inspect the saved action note and refreshed handoff. A new session should report the updated date and still keep recording unresolved.

Adapt this pattern

For a software project, the durable facts may be approved constraints and interface decisions; the handoff may contain a failing test and its next investigation. For research, save source-backed findings and unresolved questions. The review-and-save loop remains the same.