The four things real preview notes always have
- Supported floor in build numbers — “Windows 10 or later” is a shrug; “Windows 10 1809 (build 17763) x64 or Windows 11” is a commitment with a test matrix.
- Scope boundaries in system terms — “safe” enters as HKCU-only, no service, no SCHEDULED tasks, import-safe CSAs reviews; claims that can be verified, in the exact vocabulary the tool itself uses.
- Gate evidence matched to the artifact — hashes and manifest files beside the MSI; if the checksum ships “after ship,” the discipline shipped after ship.
- Downgrade/undo story — a preview brave enough to mention how to leave it is the preview that plans to still exist after the honeymoon.
Self-application
Hold us to the list: the preview page should pass every element or the release notes meet the gates they came from. Good announcements are easier to write for teams that can't ship violations; good users learn to expect the equivalent of a build log from their candidates — expectations rise in proportion to verifiability.
ProofTune ProjectEngineering notes — every claim here names the bytes a real tool touches. Verify first, install second.