E.5:6 - Conformance Checklist
| ID | Requirement | Purpose |
|---|---|---|
| CC‑GR.1 | A Core pattern SHALL name the guard-rails whose interpretation, realization or interaction changes its design or use, and explain that relation. | Makes material rule interactions recoverable. |
| CC‑GR.2 | Core, Tooling and Pedagogy respect GR-1 through GR-4 at their own layer. Implementation and runnable teaching remain in their sources. Necessary subject-defining syntax follows E.5.1 and interpretation/mapping follows E.5.2. | Preserves both portability and applicable concrete-subject rules. |
| CC‑GR.3 | A change to a guard-rail’s governing meaning REQUIRES an E.9 Design-Rationale Record stating the reason and Pillar impact under the E.3 precedence model. | Grounds a changed constitutional obligation while preserving E.9’s ordinary editorial branch. |
| CC‑GR.4 | The aggregate of guard‑rail rules MUST remain internally consistent and acyclic. No guard‑rail may override another without explicit precedence edges. | Preserves deterministic governance. |
| CC‑GR.5 | Every Core pattern MUST make its primary EntityOfConcern or primary relation recoverable at first mention. Declare CHR:ReferencePlane (`world | concept |
All CC‑GR duties are conceptual. Any automated checks are informative only and live in Tooling/Pedagogy.