A release produces not only code artifacts but a change log that outsiders can check: which rule class changed, the effective date, which pages were affected, and who signed off. Put the log at a stable, citable entry rather than leaving it in internal chat — chat cannot be cited and does not survive hindsight.
Separate 'effective' from 'planned' in log entries: unreleased changes belong in the planning section so outsiders do not read a proposal as current policy. When a rollback happens, append an entry instead of deleting the original, keeping a traceable timeline.
This article covers log visibility and format only; it makes no compliance judgement about the changes themselves. Logs follow the retention period, and the public version follows existing redaction rules with no private parameters.