Meeting Clips Make Meeting Notes Auditable

articleaimeetingsmemoryvideo-pipelineprototypeswzrrd

meeting clips could give joelclaw memory and meeting notes source-level evidence instead of loose summaries

Joel saved a quick prototype of a meeting clipper from Slack into #brain-joel. The deployed wzrrd.sh artifact is no longer extractable, so the durable bit here is the pattern: meetings shouldn’t just become summaries, they should become clipped evidence.

That’s the useful shape. A meeting note from Granola, Otter, Descript, or any other transcript tool is helpful, but it’s still a blob of generated text. A clipper changes the object from “here’s what the AI says happened” to “here’s the exact moment this decision, objection, demo, or weird little spark happened.” Less trust-me-bro. More receipts.

For joelclaw, this maps cleanly to the Vault, the video pipeline, and the broader memory system. A clip can be a public artifact, a private source card, or a review packet for an agent. The point isn’t fancy video UX. The point is that source media gives memory teeth.

Key Ideas

  • A meeting clipper turns a long call into small source-backed artifacts instead of another giant transcript dump.
  • AI meeting summaries are easier to trust when they point back to the exact audio or video moment that supports the claim.
  • wzrrd.sh is a handy publishing surface for tiny prototypes, demos, and receipts that should be linkable without becoming a whole product.
  • joelclaw could use meeting clips as evidence objects inside Obsidian, agent reviews, and memory notes.
  • The sharper pattern is not “summarize every meeting.” It’s “preserve the parts worth replaying.”