Decisions only
A meeting recap compresses the meeting. This does the opposite: it throws the meeting away and keeps only the sentences that bind someone.
The product is the omission. Anyone can summarize a transcript. Returning six lines and nothing else is the hard part, and it is the only reason someone uses this instead of reading the recap. Protect it at every step.
Workflow
1. Take the input as given
A pasted transcript, a Teams or Copilot recap, .vtt captions, or someone's raw notes.
A file path works too (.txt, .md, .vtt, .docx). Expect bad quality: missing speaker
labels, mangled names, crosstalk, decisions phrased as questions.
Note the meeting date if the transcript carries one — relative dates resolve against it.
Ask nothing unless genuinely blocked. At most two questions, and only these:
- No speaker attribution anywhere → "There are no names in this transcript — list owners as unassigned, or do you want to tell me who was in the room?"
- Transcript clearly truncated mid-sentence → say so, ask whether to proceed on the partial.
Never ask about format, tone, length or audience. Draft first.
2. Sort every exchange
Read references/what-counts.md and apply it. Two questions per exchange: did an option
get closed (decision), and did a named person go on the hook (commitment)? Anything
answering no to both is discussion — discard it.
The reference carries the refusal table, the rulings for reversals, decisions made by silence, unowned actions and vague dates, and the closed four-item list of what earns a Needs chasing flag. Those cases are the skill; do not improvise them.
3. Write the tables and stop
Two tables, then the flag list, then the fixed trace line. Nothing before, nothing else after.
## Decisions (4)
| # | Decision | Made by | Confidence |
|---|----------|---------|------------|
| D1 | Going with Northbeam for the migration, over Calyx, at ~11% higher cost | Sarah | explicit |
| D2 | Launch moved to January — reverses the earlier call to hold December | Sarah | explicit |
| D3 | Second analyst req frozen until Q1 | the room | inferred — nobody objected |
## Commitments (3)
| # | Who | What | By when |
|---|-----|------|---------|
| C1 | Priya | Revised cost model to Sarah | Thu 17 Sep |
| C2 | — unassigned | Book the Northbeam kickoff | before end of month |
## Needs chasing (4)
- C2 has no owner and no fixed date — someone has to claim it before the slot lapses.
- C3's date is "end of the month" — never pinned.
- D3 rested on silence, not assent. Worth confirming in writing.
- D2 reversed an earlier call in the same meeting; anyone who left early still
believes December holds.
Ask "where did D2 come from?" or "why isn't X in here?" to see the transcript behind any line.
(Rows trimmed above for length — a real run lists every item the counts claim.)
Counts in the headings are deliberate: ## Decisions (0) is information, a blank section
looks like a bug.
Output lands in chat as copyable markdown. Write a file only if asked.
Rules
- No summary. No overview paragraph, no attendee list, no "key themes", no agenda recap, no closing line. If it doesn't bind someone, it isn't in the output.
- Nothing decided is a valid answer. If the meeting bound nobody, say so in one line and stop: "Nothing was decided and nobody committed to anything." Do not pad it into a summary to look productive. Many meetings genuinely are this.
- Precision beats recall. Four real decisions plus one thing that wasn't a decision is worse than three real ones alone — a false positive destroys trust in the omission, which is the whole product. When an item is genuinely borderline, leave it out and mention it in one line under Needs chasing.
- Never guess an owner.
— unassignedis the answer. A guessed name stops anyone chasing it. - Never invent a date. Resolve against the meeting date, or keep the phrase verbatim.
- Reversals collapse to their final state, with a clause noting the change.
- Flags are a closed list. Only the four triggers in the reference earn a Needs chasing line — unowned commitment, undated commitment, decision by silence, in-meeting reversal. Risks, concerns and things that merely seemed notable are commentary. Omit the section entirely when nothing qualifies.
- Trace on request, never inline. Don't carry a quote column — it doubles the width and
dilutes the brevity. Handles (
D1,C1) are always there; the working appears only when asked. See Tracing below.
Tracing
The tables carry no quotes and no reasoning, so the first doubt has to be answerable in one
turn. Read references/tracing.md before answering any follow-up about a row: it carries the
handles (D, C), the fixed closing line, the trace block (The lines · The test · The
ruling · What would change it), and the questions to expect — "we never agreed that",
"why am I the owner?", "why isn't X here?", "how did you get that date?" — with what each
answer must show.
A trace re-reads the transcript and can correct the tables: a row that doesn't survive is
retracted, a guessed owner reverts to — unassigned, a missed decision is added.
