Google SRE — Change Management (progressive rollout & rollback) — 50% covered.

2 requirements · 1 enforced · 0 designed · 0 advisory · 0 deferred.

Source: Google SRE — Change Management (progressive rollout & rollback) — Site-reliability-engineering practice framework. KYE Protocol™ governs the SUBSET that resolves at the action boundary — the moment an AI-driven production action (a rollback / hotfix / infra-change) moves toward a consequential effect — under a recorded change-authority decision, with the change-class due-diligence recorded, replay-provable provenance, and named sign-off. KYE does not detect the incident, perform RCA, monitor the system, or operate the change-management tooling. · License: Google SRE change-management practice is described in the publicly available Google SRE Book; KYE registry references the practice descriptively for mapping purposes and asserts no ownership.

By category

Category	Reqs	Enforced	Designed	Advisory	Deferred	Coverage
Change management — rollout authority & rollback readiness (enforced action-boundary subset)	1	1	0	0	0	100%
Monitoring & rollout tooling (out-of-scope — sre / platform)	1	0	0	0	0	0%

Every requirement → the KYE™ artefact that enforces it

ID	Title	Status	KYE™ enforcement
`google-sre-change-management.progressive-rollout-authority`	Progressive rollout & rollback readiness: an AI-proposed production change proceeds only under a recorded rollout-authority decision with a rollback plan	enforced	rule_packs: `kye:rule-pack:production-action-authority` dictionaries: `internal` engines: `internal`, `internal`, `internal` audit_events: `kye.purpose.request.v1`, `kye.purpose.admissibility.v1`, `kye.evidence.decision_map.v1`, `kye.evidence.pack.v1` constitution_refs: `constitution/12-PURPOSE-PERMISSION.md`, `constitution/13-RESILIENCE-LOOP.md`
`google-sre-change-management.monitoring-rollout-tooling`	Monitoring, canary analysis, and rollout-automation tooling	out-of-scope	(no enforcement cited)