# Change Register

Per `../methodology/build-methodology-core.md` §9. Locked artifacts are never edited piecemeal —
approved changes batch into versioned revisions. **Classes:** 1 cosmetic · 2 functional-within-design
· 3 structural/technical · 4 foundational (stop the belt).

| ID | Date | Source | Change | Class | Gate | Artifacts touched | Status |
|---|---|---|---|---|---|---|---|
| CR-001 | | | <!-- what changed + why --> | 1–4 | Owner ✓ / pending | <!-- spec §, architecture, etc. --> | Proposed / Approved / Applied |

## Incident retrospectives
<!-- When something slips through, write the root cause + the rule/control you added so it can't
recur. These become new MUSTs/SHOULDs in CLAUDE.md. Two worth carrying from the prior project:
- INC-001: built UI diverged wholesale from the approved design and was self-certified "done" →
  fix = MUST-9 (conformance = definition of done) + this register.
- INC-002: a "clean UAT / no bugs" was claimed from a shallow render-check; real security/scenario/
  responsive testing then found critical bugs → fix = the build-completion testing battery +
  production-readiness checklist in CLAUDE.md §9, and never claim "production-ready" without it. -->