E.18:5.5 - S5 - Comparability and aggregation (normalize‑then‑compare; counterfactual form)
The comparison explanation applies under the following admissibility conditions:
- If a path segment intends to compare or aggregate, it is admissible as a comparison only when UNM precedes it; UNM is method‑independent, publishes TransportRegistry^Phi and CG-Spec references, and faces cite those editions; otherwise this comparison explanation does not apply.
- If the comparator defines a declared partial order, then returns are sets or archives (Pareto or Archive); if a total order is declared, it is the one provided by the comparator; otherwise set semantics apply and covert scalarization is out of scope here.
- If a claim is ordinal‑only, then only comparison results are published; arithmetic transforms (e.g., means and z‑scores) are out of scope of this explanation and belong to declared comparators or downstream policy.
Edition-aware publication records for sets or archives (e.g., QD archives) pin DescriptorMapRef.edition, DistanceDefRef.edition, and CharacteristicSpaceRef.edition when applicable; refresh is slice-local. For current selector, archive, pool, selected-set result-declaration, comparator, or refresh claims, apply the definitions and tests in A.19.SelectorMechanism, C.18, C.19, G.5, G.9, and G.11. For actual publication, use E.17 for a source-backed face and return to source and E.24.PUB for the occurrence, form, carrier, audience, bounded use, and availability.