5.1 Each maintenance group has a canary set of [number or percent] assets chosen by the group owner to represent the group.
5.2 A patch installs on the canary set first. The rollout widens after [2] working days if there is no incident. An incident is [defined: failed boot, service outage, user-reported loss of function, security-tool alert].
5.3 For class 1 patches the canary period is [hours]; the rollout may widen sooner on the policy owner's decision, recorded with the reason.
5.4 A rollback method is written before deployment. Where none exists, the fallback is [restore from backup taken before the window].
5.5 For each patch the record holds: what was tested, by whom, result, date, and the decision to widen.