A.19.USCM:12 - Relations
-
Builds on
A.6.1(operation declarations and actual application/binding rules).A.19.CHR:4.2.1(CHR SlotKind lexicon).G.0(CG‑Spec, specificallySCPandMinimalEvidence).A.18(CSLC lawfulness discipline).C.16(measurement constitution and scale-lawful operations when measurement is claimed).A.15.2for the planned edition/policy baseline;A.15.3plusA.19.CHR:4.7.2for typed filling of independently declared positions.A.19.CN(CN‑Spec, specificallycomparabilityrouting and normalization‑based comparability expectations).
-
Used by
A.19.CHR(suite membership and suite protocols; USCM is thescorestage).- Downstream CHR stages that require score measures as inputs (e.g.,
CPM,SelectorMechanism). E.18when USCM instances are used as nodes in a selectedTransformationFlowStructure; the selectedScoringMethodDescriptionRef@edition(…)and other pins live in planned baselines (P2W), while executions surface effective refs/pins viaAudit.
-
Coordinates with
UNMwhenCN‑Spec.comparabilityrequires normalization‑based comparability (explicit choreography, no hidden UNM).ULSAMwhen folding/aggregation is needed as a distinct, explicit step.G.2andGPatternExtensionwiring modules for post‑2015 method families, without mutating the USCM kernel.E.20(governing-pattern discipline) andF.18(alias docking) for governing-source references and designation continuity.