A.19.CPM:5 - Archetypal Grounding — informative
A.19.CPM:5.1 - Tell
Think of CPM as a declaration for a replayable, relation-producing comparison operation:
- Input: “two admitted profiles + an explicit comparator spec + declared admissibility and evidence declarations”
- Output: “a set‑valued relation outcome that preserves incomparability and uncertainty”
CPM returns the comparison relation; candidate selection and work authorization require their own rules.
A.19.CPM:5.2 - Show (U.System) — comparing two supplier options without faking a total order
A program manager compares Supplier‑A vs Supplier‑B for a safety‑critical component. The team tracks a profile of measures (cost, lead time, defect rate, assurance, sustainability), but not all measures are comparable across regions (different reporting regimes, different units).
-
The project has a declared
CN‑Spec(admission and comparability declarations) and a declaredCG‑Specthat lists admissible comparators inComparatorSetand evidence rules inMinimalEvidence. -
The comparator is
ParetoDominanceComparatorSpecRef@edition, declared inCG-Spec.ComparatorSet. -
The application binds the two supplier profiles; the claim scope
supplier options for the named component and procurement decision; its selected regulatory and reportingU.ContextSlicemembers under A.2.6;ComparisonPredicate = nonebecause Pareto dominance is supplied by the comparator; the stated procurement reference plane; and the explicit comparison interval. -
CPM runs
Compare(...); a changed component, scope member, comparator, plane, or interval is another comparison rather than an update to the same output.- Supplier-A is better in cost but worse in defect rate, while assurance evidence is missing. The known cost/defect trade-off can justify Pareto incomparability if the declared comparator and partial-evidence policy admit that inference. Missing assurance evidence alone establishes no incomparability relation.
CompareEligibilityreturnsdegradeorabstainunder the evidence policy. Onabstain, no comparison tokens are fabricated. When an explicitdegradepolicy permits a bounded partial comparison,ComparisonResultSlotcontains only the justified relation tokens and preserves incomparability.
-
The downstream
SelectorMechanismcan then return a selected set (e.g., keep both suppliers in the candidate set) rather than forcing a single winner by hidden tie‑break rules.
A.19.CPM:5.3 - Show (U.Episteme) — uncertainty‑aware comparison with set‑valued outcomes
A research lead compares two proposed methods for a system component. Both methods have performance estimates with uncertainty bounds (e.g., distributions or prediction intervals). The team uses a SoTA uncertainty quantification package (for example, a conformal prediction method) to avoid overstating confidence.
USCMproduces score profiles that are interval‑valued (or otherwise uncertainty‑annotated) rather than point estimates.- The chosen comparator is uncertainty‑aware and declared as a
ComparatorSpec(edition‑pinned) inCG‑Spec.ComparatorSet. CompareEligibilityreturns its guard value separately. If comparison proceeds, CPM returns justified relation tokens such asnot worseorincomparable; if it abstains, noabstaintoken is smuggled intoComparisonResultSlot.- The comparison or eligibility application, its effective comparator and evidence policy, and its returned value or explicit absence make the outcome recoverable. Use A.10 when the bounded source-to-use account must remain replayable. A dated Work account is additional only when asserted and independently grounded under §4.1.