Treat the release note as a claim, then check it

Most release notes are written in the future tense disguised as the past: “Users can now…” The sentence is hopeful. The ledger either confirms it or does not.

In a release mapping we print the note, number each claim, and ask which local event would have to exist if the claim were true. “Users can now bulk-archive conversations” needs an archive action, a count greater than one, and at least one person who was not on the shipping team. If the only archives belong to the engineer who built the button, the note is still a draft.

This is not a hunt for blame. Notes are written under time pressure. The mapping gives the next note a shorter list of verbs. Teams that repeat the exercise for three releases in a row usually stop announcing empty states as if they were destinations.

Bring the note, the date it went out, and the ledger. Leave credentials at home. If a claim cannot be checked without opening a production console, we mark the claim unverified and move on.