Google SRE — Change Management (progressive rollout & rollback)

Google SRE — Change Management (progressive rollout & rollback) — 100% of in-scope requirements covered.

2 requirements · 1 in scope (1 enforced) · 1 out-of-scope (outside KYE™’s authority layer). The 100% is weighted over the in-scope base.

Google SRE: requirement → the KYE™ artefact that enforces it

Demo data

You learn: Which requirements KYE™ enforces at runtime and with which artefact. You can: Walk the requirements.

  1. progressive-rollout-authority · enforced

    Progressive rollout & rollback readiness: an AI-proposed production change proceeds only under a recorded…

    Rule packs: kye:rule-pack:production-action-authority · Audit events: kye.purpose.request.v1, kye.purpose.admissibility.v1, kye.evidence.decision_map.v1, kye.evidence.pack.v1 · Constitution: 12…

  2. monitoring-rollout-tooling · out-of-scope

    Monitoring, canary analysis, and rollout-automation tooling

    (no enforcement cited)

How this widget is built
Demonstrates
KYE™ Compliance Mapping Rail™
Components
  • Framework requirement (clause)
  • Coverage status
  • KYE™ enforcement artefact (event, decision-record field, Evidence Pack™ entry)
Flow
Clause → status → the KYE™ artefact that enforces it, enforced requirements first. Architecture diagram
Used on

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

CategoryReqsEnforcedDesignedAdvisoryDeferredCoverage
Change management — rollout authority & rollback readiness (enforced action-boundary subset)11000100%
Monitoring & rollout tooling (out-of-scope — sre / platform)100000%

Every requirement → the KYE™ artefact that enforces it

IDTitleStatusKYE™ enforcement
google-sre-change-management.progressive-rollout-authorityProgressive rollout & rollback readiness: an AI-proposed production change proceeds only under a recorded rollout-authority decision with a rollback planenforcedrule_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-toolingMonitoring, canary analysis, and rollout-automation toolingout-of-scope(no enforcement cited)

Canonical KYE™ surfaces referenced on this page: KYE Protocol™.