A.19:7 - Common Anti-Patterns and How to Avoid Them

The following are common modeling mistakes (“anti-patterns”) related to measurement spaces, and how to correct them:

• “Same label ⇒ comparable.” ✗ Assuming two Ready labels or two same-named coordinates are comparable across different reference schemes or planes. ✓ Normalize into one declared target space. Cite an F.9 Bridge only when its predicate obtains between two exact F.17 local senses, state the bounded-use claim and reliance separately, and cite the applicable plane relation for a ReferencePlane crossing. Let CPM state the comparison scope, comparator, plane, and window.

• “Compare before common-space mapping.” ✗ Comparing values directly across different scales, e.g. Drift_A = 5°C vs Drift_B = 5°F as if they were the same. ✓ Normalize to common units first: for drift expressed as a temperature difference, use ΔT_C = ΔT_F × 5/9. For absolute temperature values, apply the Fahrenheit-to-Celsius NormalizationMethod m(T_F) = (T_F - 32) × 5/9. Then compare the converted values of the same declared Characteristic. Always normalize into one space before comparing magnitudes.

• “Checklist = method sequence.”

  • Wrong: Ready means “do Step 1, then Step 2.”
  • Repair: let the checklist state the conditions that must hold. Put the way of reaching them in a separate Method or MethodDescription, planned occurrences in a WorkPlan, and what actually happened in Work. Evidence separately supports an assertion or evaluation result; it is not the condition itself.

• “Retro-fix past assertions.” ✗ Going back to edit or reinterpret old StateAssertions after changing a threshold or NormalizationMethod (e.g. “We updated the criteria, let’s ‘fix’ last quarter’s records to match”). ✓ Never alter historical assertions: Leave history as-is. If criteria change, issue new assertions under the new criteria going forward, and if needed, explicitly version the NormalizationMethod or UNM declaration or checklist. Past assertions retain the criteria and time under which they were made; any renewed use requires checking their applicability and currentness. This ensures auditability and avoids erasing or rewriting what was asserted under earlier standards.

C.27 temporal-claim relation.

• C.27 may flag: a rate or rate-change claim that needs base characteristic, scale and unit, time base or sampling window, transformation or finite-difference method, evidence, and admissible use.
• A.19 governs CharacteristicSpace and Coordinate discipline; C.16 governs measurement construction and backing.
• Non-admissible use: words such as velocity, acceleration, throughput, cadence, or recovery speed do not by themselves establish a Characteristic, Scale, or measurement method.
• Use boundary: when the interpretation governs the current claim, cite baseCharacteristicRef, the relevant measure reference, sampling window, construction method such as DHCMethodRef, and the C.16 measurement or construction relation reference; C.27 does not define a parallel measurement system.

A.19.ECS object-under-improvement evaluation construction relation.

• A.19 defines CharacteristicSpace as an ontological structure: slots, characteristics, scales, value sets, overlays, and comparability boundaries.
• A.19.ECS governs the construction of one object-under-improvement evaluation CharacteristicSpace for an object being improved. It is used before E.22 and E.23 when no adequate object-under-improvement evaluation exists.
• Existing object-under-improvement evaluation patterns such as E.21, E.9.DA, E.2.DA, and the naming vector inside F.18 are examples of this construction shape for object kinds under improvement. They keep their own coordinate, value-meaning, and stop-condition definitions.