Experiment: turning vendor release notes into an operator queue
A small pipeline for separating actionable tenant changes from announcements that do not require an administrator's attention.
Release-note summaries are easy to generate and rarely enough. The useful output is a queue: what changed, who owns it, what needs verification, and when it could matter.
Test shape
The experiment used a small set of public vendor announcements. Each item was classified into one of four actions: review configuration, notify users, validate compatibility, or monitor only.
What helped
Requiring a concrete owner and deadline removed most low-value items. The model was also asked to preserve the source URL and quote no more than the minimum text needed to identify the change.
What still fails
Licensing and rollout scope remain easy to flatten into an overconfident sentence. Those fields need direct source checks, and regional or tenant-specific availability should be carried into the final queue rather than normalized away.