Coffee break: the summariser you can prove is wrong syllabus
Twenty minutes to a summariser
No framework, no vector store, no agent. One file, one call. Everything you might add would only make the second half harder to interpret.
Get a transcript
One real one. A recorded meeting, a support call, or five minutes of you talking through a project out loud into your phone.
Real matters. A tidy sample transcript from a blog post has no crosstalk, no half-finished sentences, nobody changing their mind, and nobody being interrupted — which is to say it has none of the properties that make this hard. Remove names or details if you need to before it becomes a fixture.
One call, one prompt
Ask for three things: a summary, the decisions made, and the action items with owners. Print the result. That is the build.
Resist improving the prompt yet. You have no way to tell whether a change made it better, and adjusting it now means the next twenty minutes measure your intuition rather than the system.
It reads well. Now what?
The output is clean, well organised, and plausible. What have you established?
How long did that take?
Minutes from starting to a printed summary. Worth recording because it makes the point: the build is not where the work is.