| CC‑P‑1 | An architectural pattern names the Pillars whose realization or conflict changes its design or use, with the substantive grounds required by CC‑P‑4. | Makes material constitutional relations recoverable. |
| 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 | A claim of scale or generalization advantage in computational work, or a choice invoking a local generality policy, begins with the scale-claim check in C.19.1. An empirical comparison evaluates usable performance over the declared budget range and receiving conditions. For a choice made under a project rule, identify the condition that makes the rule applicable. A bounded specialization alone calls for no audit, debt entry or waiver. | Connects the choice to its empirical or policy grounds. |
| 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. |