A.19.CHR:12 - Relations

A.6.7 MechSuiteDescription (the base suite description kind and obligations surface)
A.15.2 WorkPlan for edition/reference baselines; A.15.3 for conditional typed planned filling
A.6.1 U.Mechanism (operation-local argument/result declarations, their derived SlotIndex, and the exact comparison tests in §4.8)
A.19 CN-Spec and G.0 CG-Spec (governance card and admissibility gate)
E.18 / E.18 (P2W, crossings, UTS and Path pins)
E.10 (lexical and ontological discipline) and E.19 (conformance style)

G.5 (selector semantics, set-return defaults, archive semantics and report-only illumination discipline)
G.10 and PTM (publication and telemetry as external steps, not suite internals)
A.21 OperationalGate(profile) and USM.Guards (gate-level decisions and reserved guard pins)
C.23 SoS‑LOG (explicit degrade branches such as probe-only and sandbox)

Constrains Part G universalization: G patterns should reference this suite for the universal CHR node set and express method and generator specifics only as (a) explicit specializations (⊑/⊑⁺) or (b) separate provider mechanisms connected via Uses.
Informs other kits and suites: record the selected edition/reference baseline in A.15.2 WorkPlan content; use A.15.3 only where independently declared positions require typed planned filling.

Tell. This pattern is intended as a universal core anchor for the Part‑G:

G patterns not mixing universal CHR admissibility mechanics with CG-frame specifics, discipline-specific method content, and packaging concerns in one construct.
Instead, they cite CHRMechanismSuiteDescription (universal node set and obligations) and keep specifics in explicit specializations or separate Uses providers.
P2W integration cites the ordinary planned baseline and any applicable typed fillings, while actual bindings and launch witnesses remain enactment claims.