Turn meeting notes into action items—without inventing owners or deadlines.
Walk through one preserved synthetic run, see what stayed unresolved, and copy the exact sample kit without uploading or processing notes here.
Copies the exact published prompt and synthetic notes—not the preserved output. No notes are uploaded or processed, and no model runs on this page. Results may differ.
Inspect the complete evidence →After a successful copy, the page attempts property-free measurement events. Analytics may be blocked or delayed. The events do not prove a person, paste, model run, adoption, or outcome. QA visits using ?qa=1suppress this attempt.
- Synthetic example
- No note upload
- 1 preserved run
- Post-hoc rubric
Start with the notes. Keep the unknowns visible.
This is the exact Test 001 source and raw output. It is evidence from one Codex-generated, Codex-self-evaluated run—not independent validation.
Maya: client likes the revised scope but wants the estimate broken into launch and ongoing hosting. I can send the revised estimate Friday, but we need to settle which hosting tier first. Jon will make a first pass at the onboarding checklist by next Tuesday. We said analytics can wait until phase two. Maya should book the client review after the estimate goes out. Nobody picked an owner or date for the hosting decision. Client asked whether weekend support is included; that still needs an answer.
## Decisions | Decision | Source quote | |---|---| | Analytics is deferred to phase two. | "We said analytics can wait until phase two." | ## Actions | Action | Owner | Due date | Dependency | Source quote | |---|---|---|---|---| | Send the revised estimate, split into launch and ongoing hosting. | Maya | Friday | Hosting tier must be settled first. | "I can send the revised estimate Friday, but we need to settle which hosting tier first." | | Confirm the hosting tier. | Not stated | Not stated | None stated | "Nobody picked an owner or date for the hosting decision." | | Draft the onboarding checklist. | Jon | Next Tuesday | Final scope | "Jon will make a first pass at the onboarding checklist by next Tuesday." | | Book the client review. | Maya | After the estimate is sent | Revised estimate sent | "Maya should book the client review after the estimate goes out." | ## Needs clarification - Who owns the hosting-tier decision, and when is it due? - Is weekend support included? - What calendar dates do "Friday" and "next Tuesday" represent? Confidence: High that the explicit decisions and actions were captured from the supplied notes; human clarification is required before this becomes an operational record.
In this preserved run, missing facts stayed missing.
The goal is not to extract the most tasks. It is to keep absent owners, dates, decisions, and answers from becoming confident-looking facts.
An unassigned decision stays unassigned.
The notes say nobody owns the hosting-tier decision and give it no date. The preserved output keeps both fields missing instead of silently completing them.
“Nobody picked an owner or date for the hosting decision.”
Human check: Choose the owner and deadline before this becomes an operational record.
Relative dates stay relative.
The run retains “Friday” and “next Tuesday,” then asks for the actual calendar dates. It does not pretend the meeting date or timezone was supplied.
“I can send the revised estimate Friday” and “by next Tuesday.”
Human check: Resolve both dates against the real meeting date and timezone.
An unanswered service question stays open.
The client asked whether weekend support is included. The notes provide no answer, so the run places the question under Needs clarification.
“Client asked whether weekend support is included; that still needs an answer.”
Human check: Verify the current support policy before replying or promising coverage.
Make every extracted field traceable.
Keep decisions, actions, and clarification questions separate. Use Not stated when the source does not supply a value.
Do not paste private or confidential notes into this site or replace the synthetic sample with them in another tool. This public experiment uses only synthetic or public material; the guide does not authorize processing private material elsewhere.
## Decisions | Decision | Source quote | |---|---| | | | ## Actions | Action | Owner | Due date | Dependency | Source quote | |---|---|---|---|---| | | Not stated | Not stated | None stated | | ## Needs clarification - Who owns each unassigned action? - What calendar date does each relative date mean? - Which questions remain unanswered? Human review: resolve every missing field before using this as an operational record.
Useful with human review. Not ready without review.
Test 001 is one preserved synthetic run. Its rubric was formalized after generation and Codex evaluated its own output. It does not establish reliability, runtime, cost, or performance on real notes. A human must resolve the relative dates, assign an owner and due date for the hosting-tier decision, and answer the support question before operational use.