ITIL 4 — Change Enablement (change authority & assessment)
ITIL 4 — Change Enablement (change authority & assessment) — 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.
ITIL 4: requirement → the KYE™ artefact that enforces it
Demo dataYou learn: Which requirements KYE™ enforces at runtime and with which artefact. You can: Walk the requirements.
-
change-authority-assessment · enforced
Change authority: an AI-proposed production change proceeds only under a recorded change-authority assessment…
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…
-
change-evaluation-technical · out-of-scope
Technical change evaluation, scheduling, and change-model authoring
(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
- /compliance/itil-4-change-enablement/: On every framework page, after its opening.
Source: ITIL 4 — Change Enablement (change authority & assessment) — IT service-management best-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: ITIL® is a registered trademark of AXELOS Limited; KYE™ registry references ITIL 4 change-enablement practice descriptively for mapping purposes and asserts no ownership of the framework text.
By category
| Category | Reqs | Enforced | Designed | Advisory | Deferred | Coverage |
|---|---|---|---|---|---|---|
| Change enablement — authority & assessment (enforced action-boundary subset) | 1 | 1 | 0 | 0 | 0 | 100% |
| Change-management process (out-of-scope — change-management / sre) | 1 | 0 | 0 | 0 | 0 | 0% |
Every requirement → the KYE™ artefact that enforces it
| ID | Title | Status | KYE™ enforcement |
|---|---|---|---|
itil-4-change-enablement.change-authority-assessment | Change authority: an AI-proposed production change proceeds only under a recorded change-authority assessment & authorization | enforced | rule_packs: kye:rule-pack:production-action-authoritydictionaries: internalengines: internal, internal, internalaudit_events: kye.purpose.request.v1, kye.purpose.admissibility.v1, kye.evidence.decision_map.v1, kye.evidence.pack.v1constitution_refs: constitution/12-PURPOSE-PERMISSION.md, constitution/13-RESILIENCE-LOOP.md |
itil-4-change-enablement.change-evaluation-technical | Technical change evaluation, scheduling, and change-model authoring | out-of-scope | (no enforcement cited) |
Canonical KYE™ surfaces referenced on this page: KYE Protocol™.