Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:20:20 UTC

C.21:4.2 - Comparison and legality rules

  1. Direct same-semantics comparison. Compare readings under the same Characteristic and compatible Scale semantics and scope. Measured readings also retain C.16’s applicable measurement-definition, model, calibration, Unit and time or population conditions. State the basis used; different source labels or editions alone require no Bridge. For a claim about the whole field based on part of it, give the sampling or measurement assumptions that support the extension, or report what holds for every admissible status of the unobserved units. Restricting a report to the observed population changes the population it describes. A new observation may settle an answer under the existing model. For strict model refinement under B.5.MR, the new model must preserve the earlier assertions under the shared interpretation, admit at least one possible case and exclude an answer the earlier model allowed for the same inquiry.
  2. Cross-local comparison. When a comparison relies on a semantic relation between distinct F.17 local senses, cite the exact obtaining F.9 Bridge only after its predicate and dependencies hold. Keep its separate C.2.1 bounded-use claim, with the use, direction, correspondence rule, permitted-loss tolerance, and polarity, distinct from observed loss and current reliance. Follow F.9’s A.10 reliance branch or, for a named assurance claim, its B.3 branch for the same bounded use. If the assurance use requires an R adjustment, cite the applicable domain model and keep the adjustment in that use’s AssuranceResult. The relation supplies none of ClaimScope, measurement, comparison, or acceptance semantics.
  3. Reference-plane crossing. When a reading is used across distinct world, concept, or episteme planes, cite the exact crossing basis. Any R adjustment follows the named assurance-use and domain-model condition in rule 2. A dashboard row or source label does not establish the crossing.
  4. Cross-scale transformation. A conversion, normalization, distance, or aggregate names its exact Method, Scale, legal operation, and loss or uncertainty. No common scale is inferred from similar labels.
  5. Freshness. A persisted or reused coordinate carries its observation window and applicable currentness rule. Staleness leads to the receiving pattern’s degrade, abstain, or reopen result; it does not rewrite the historical measurement.
  6. Target bands. “Target-is-best” is not “higher-is-better.” A comparison to a band uses an explicit distance-to-band rule and keeps the receiving acceptance criterion separate from the raw reading.
Scale familyLawful ordinary operationsProhibited shortcut
nominal statusequality, membership, mode when justifiedlifecycle ranking or arithmetic without an ordered scheme
ordinal resolutionorder, median or mode where meaningfulmean, ratio, or affine arithmetic
ratio rate or densityoperations allowed by its exact Scale and Unitunit mixing or comparison across changed construction
interval balancedifferences and target distance under its exact ruleratios or silent target-band polarity
entropy and concentrationoperations under their own definitionstreating entropy and HHI as interchangeable or equally directed