Capture commitments before they become project drift

Make the follow-up
defensible.

Paste the notes. Check what was decided, who owns what and what is still unclear. Every item keeps the line that supports it.

Review meeting notes
Notes stay here Sources remain visible You approve the record
1 Add notes 2 Check sources 3 Fix the draft 4 Approve and export

Workspace

What did the meeting actually leave behind?

The public version recognises clearly labelled decisions, actions and questions. It never tries to infer agreement from ordinary discussion.

Input

Meeting notes

0 / 20,000

Helpful labels: Decision: Action: Question:. Owners and dates stay blank when the notes do not provide them.

Nothing leaves this browser.

Your review will appear here.

Start with the safe example to see how each decision and action links back to the supplied notes.

Control and evidence

Language can propose. Evidence and people control the record.

This page uses transparent browser rules so anyone can try the workflow without an account or model key. For less structured notes, the repository contains a tested LangGraph path that must pause for named human review.

Inspect the graph and tests ↗
  1. CodeHashes the source and creates stable evidence blocks.
  2. Bounded modelCan propose structured items, but has no tools or approval authority.
  3. CodeRejects any item whose quote does not match the source.
  4. LangGraphStops and waits for a named human reviewer.
  5. LangSmithCan evaluate synthetic fixtures, misses, unsupported claims, cost and latency.

Learn the workflow

Build the useful version, not just the demo.