A.19.ULSAM:5.2 - Show
Scenario A (manager-facing): “roll up” a multi-metric readiness into one reliability-like coordinate.
- A CHR pipeline produces a set of admitted measures (post-
USCMor directly from characteristic measures):MeasureSetSlot = {m₁, m₂, …, m_k}. - The team wants a single “readiness” measure
m_readyto be used as an input to later comparison/selection. The temptation is to “just average” or “just do weighted sum”. - ULSAM forces three explicit questions before folding:
- Admissibility: Is the fold admissible under
CGSpecSlot.SCP(units/scale) andCGSpecSlot.Γ_fold(declared fold kinds)? - Evidence: Is the evidence posture sufficient under
MinimalEvidence? If not, do wedegradeorabstain? - Policy identity: What is the identity of the fold (which ΓFoldRef, which edition)?
- Admissibility: Is the fold admissible under
- Only then, the pipeline performs:
Fold_Γ(MeasureSetSlot, CNSpecSlot, CGSpecSlot, GammaFoldSlot, MinimalEvidenceSlot?) → (AggregatedMeasureSlot, ContributorSetSlot?). The audit recordsΓFoldRefand (optionally) the contributor surface.
Scenario B (engineer-facing): proposed aggregation across different bases.
- A project tries to fold measures with different bearers, membership rules, scales, comparison bases, or reference planes. ULSAM first checks whether one admitted set and lawful fold can be stated. If the conclusion relies on an F.9 Bridge, kind relation, aggregation or membership relation, or plane relation, the project cites that exact obtaining relation and its loss; otherwise it constitutes separate folds or fails closed.