E.2:5 - Conformance Checklist

ID	Requirement	Purpose
CC‑P‑1	Every architectural pattern must list which pillar(s) it instantiates or refines.	Guarantees constitutional grounding.
CC‑P‑2	Every DRR proposing a normative change must include a “Pillar Impact Analysis.”	Makes constitutional review explicit.
CC‑P‑3	Tooling and pedagogical artefacts should document which pillar(s) shape their design.	Upholds P‑2 (Didactic Primacy).
CC‑P‑4	Assess the substance of every applicable Pillar constraint and any material conflict. Name the Pillars whose realization changes the pattern’s design or use; no minimum link count substitutes for that argument.	Grounds conformance in the obligations that matter to the pattern.
CC‑P‑5	When a choice claims scale/generalization advantage in a computational domain, or invokes a separately declared local generality policy, authors MUST apply BLP to the usable response over its declared budget range and receiving conditions. Ordinary bounded specialization alone activates no scale audit, debt entry or waiver.	Keeps scale preference tied to usable performance and its actual claim.
CC‑P‑6	A pillar-impact analysis that relies on mathematical structure, scale behavior, optimization, uncertainty, invariance, obstruction, or other first-principles modeling support is complete only when that support is ordinary accepted local theory, a cited `C.29` output, or a named neighboring-pattern output for evidence, causal, bridge, assurance, measurement, work, decision, publication, or admission claims.	Keeps mathematical support for pillars inspectable without letting `C.29` revise pillar authority.