# KIMU specification change control

## Locked-change procedure

A future change to a locked item requires all of the following:

1. Explicit user instruction identifying the change.
2. New R-number or formally recorded amendment.
3. Updated Markdown and DOCX controlling specifications.
4. Updated `config/feature-locks.json`.
5. Updated placeholder/feature catalogue and relevant tests.
6. Compatibility and regression assessment.
7. Release notes stating exactly what changed and what remained locked.

Absence of provider support, implementation difficulty or a developer preference is not authorisation to silently substitute a locked requirement.