The Problem
I’d just come out of an exec review of a campaign plan. The meeting went well, but now every planning doc had to be synced to what was actually decided, and the raw material was three AI notetakers that each heard a slightly different meeting. The quieter risk: things said in the room were about to harden into “facts” in the docs.The Approach
Claude Code pulled the meeting from all three sources: Zoom’s AI summary plus the full transcript, the workspace notetaker, and a calendar-based one. Where they disagreed, it arbitrated using a diarization hierarchy we’d measured months ago (Zoom attributes speakers best, the others guess more). Then it propagated the outcomes into the campaign docs, both the shared pages execs read and the local mirrors my system treats as the reasoning archive. The arbitration earned its keep immediately. One notetaker had assigned an action item to the wrong person, and the transcript settled it.What Happened
Reading the updated claim ladder afterwards, I stopped on one cell: a product feature marked “shipped.” I asked why. The answer was honest and wrong. The VP of Product had said “that one’s already launched” in the meeting, and one sentence spoken in a room had become a sourced claim in a strategy doc. So I made Claude prove it. Check the public help center. Check the engineering team’s ship-announcements channel. If both strike out, fall back to AI search over the workspace. Two lookups later, the announcements channel had the full rollout trail (internal, then 5% of users, then 100%, with dates and an owner) and the help center had a live public article. The claim was true. But the verification pass also turned up something no meeting summary had mentioned: an adjacent dependency feature sitting in internal alpha and due to promote to GA within weeks, a leading indicator that directly changes how I read our launch risk. The receipts came with free intelligence attached.What I Learned
A claim surviving verification doesn’t retroactively justify skipping the verification. It cost two lookups, upgraded hearsay into a citable fact, and surfaced adjacent intel I’d have otherwise waited weeks to hear. The rule is now written into the system so the next session inherits it: an exec’s in-meeting product claim is a lead, not a citation. The fast checks are the ship-announcements channel for rollout state and the help center for what’s publicly true.Drafted by my Claude from our working session. I approved it before it went up.