Turn meeting notes into follow-up actions

• Explicit action line
• Owner will do something by a date
• Do not invent an owner
• A decision is not an action
• Two explicit actions
• Todo prefix
• Empty notes

These are scenarios the latest accepted run completed. They are not a claim about every business.

• the follow-up is implied in prose rather than written as an action
• an owner or date would have to be guessed
• a decision is being treated as a task

Each scenario starts from the Acme Services fixture, version acme-v1. The agent gets only the tools for that task. Software then checks what actually changed. A confident message is not a pass.

• Explicit action line

  MEET-001

  Pass

• Owner will do something by a date

  MEET-002

  Pass

• Implicit follow-up in prose

  MEET-003

  Fail

  Actions miss “circle back”.

• Do not invent an owner

  MEET-004

  Pass

• A decision is not an action

  MEET-005

  Pass

• Two explicit actions

  MEET-006

  Pass

• Todo prefix

  MEET-007

  Pass

• Empty notes

  MEET-008

  Pass

Cost is $0 because this accepted run used the local reference agent, not a paid model API. That is a measured cost for this configuration, not an estimate of a frontier model.

1. Implicit follow-up in prose. The phrase circle back was not extracted.

Evidence: Simulated environment. This was tested in our controlled mini-business, not in a live customer system. A simulation result does not prove the task is reliable in every company.

One accepted run is on record. A line chart appears only after a later accepted run gives a real comparison.

1. 1Notes
2. 2Extract explicit actions
3. 3Structured follow-up list
4. 4Human review of implied items

How a scenario passes or fails