Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:30:20 UTC

C.16:11 - Common Anti-Patterns and How to Avoid Them

  • Template as occurrence. A reusable U.DHCMethod, model, signature, or calibration procedure is treated as proof that work occurred. Ground dated work and actual bindings.
  • Generic result field. A record has result=... without saying whether it is output, indication, measurement result, diagnosis, verdict, or decision. Name the direct result kind and governor.
  • Evidence algebra. Evidence locators are unioned as though idempotence or count determined uncertainty or warrant. Use measurement-model uncertainty propagation and exact A.10/B.3 reliance separately.
  • Scale drift. A template id survives changed Scale, model, unit, or calibration semantics. Publish a successor and state the relation; do not mutate historical readings.
  • Arithmetic on ordinal. Encoded levels are averaged or ratio-compared. Stay with order-preserving operations or introduce a separately governed scoring method and Scale.
  • Multi-Characteristic stuffing. One reading carries a vector while pretending to be one measurement. Create separate results and declare any later aggregation.
  • Result-to-verdict shortcut. A value inside a tolerance is called accepted without performed criterion evaluation. Ground the separate evaluation work, exact clause application, verdict episteme, and later decision.