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 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 08:26:30 UTC

B.3:8 - Common anti-patterns and repairs

Anti-patternWhy it failsRepair
Universal weakest-link formulamin can be an upper bound for a conjunction and can ignore alternatives or dependence.Use the exact dependency model and domain rule; otherwise report inputs separately.
Ordinal penalty subtractionAn ordinal label is subtracted from a probability or ratio quantity.Use a calibrated mapping to the same quantity when one exists, or keep the values separate.
Formality raises assuranceA more formal wrong model receives a better result.State the inspectability gain and the uncertainty it closes; keep truth and empirical adequacy separate.
Same letter, different propertyR names system reliability in one row and evidence quality in another.Give each characteristic its own bearer and definition.
Safety-case inflationA warning, access value, or consequential display triggers a generic B.3 package.Use the direct domain pattern; apply B.3 only to an actual assurance claim.
Evidence creates truthNew evidence is said to make the target fact obtain.Revise the warrant or disposition unless the world-side facts changed.
Assessment-record collapseA checklist, trace, witness, or note is treated as the assessment Work or result.Identify each object separately and add only what the use consumes.
Design/run chimeraBlueprint evidence and runtime observations are merged into one score.Produce separate results and compare them.