# Synthetic sample: meeting-to-action register

Illustrative output only. The meeting, roles, note identifiers and dates are fictional. No task, invitation or reminder was created.

## Sample decision

Note M-012, decision 2: Prepare a migration checklist first. This is not approval to migrate.

## Ready sample — awaiting owner confirmation

Action 1: Draft the migration checklist.
- Proposed owner: project lead; map the role to a real person before use.
- Due: 18 March 2030, 17:00 Europe/London.
- Source: sample note M-012, action 1.
- State: awaiting owner acceptance.

Action 2: Review the checklist.
- Proposed owner: technical reviewer; confirm who accepts the work.
- Due: not agreed. Confirm after the draft is available.
- Source: sample note M-012, action 2.
- State: awaiting owner and date confirmation.

Human review: the meeting owner checks the meaning. Each action owner accepts the work and date. Do not turn this draft into a calendar commitment automatically.

## Missing-input path — decisions needed

Input: “Someone should handle this next week.”

No owner, task boundary or explicit date is established. Keep the item in a decisions-needed list.

Request: “Who accepts this action, what must be delivered, and what date and time zone should apply?”

Discuss this workflow: https://leon-ai-workflows.pages.dev/?workflow=meetings#contact

Leon S Kennedy — Independent FDE Engineer (Forward Deployed Engineer)