E.5:6 - Conformance Checklist
| ID | Requirement | Purpose |
|---|---|---|
| CC‑GR.1 | Every new Core pattern SHALL cite, in its Relations section, the guard‑rail(s) it relies on or may affect. | Ensures traceability and deliberate rule interaction. |
| 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 revision to any guard‑rail pattern REQUIRES a Design‑Rationale Record that (a) states the reason, and (b) includes a Pillar‑impact analysis per E.3 precedence model. | Aligns evolution with higher‑level principles. |
| 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 anchor its primary EntityOfConcern or primary relation with a declared ReferencePlane (`world | concept |
All CC‑GR duties are conceptual. Any automated checks are informative only and live in Tooling/Pedagogy.