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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:10:03 UTC

B.3.5:12 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhat goes wrongRepair
Trace as relation or truth-makerA Gamma_m trace is treated as the public relation, as proof that the relation obtains, or as the source of whole identity.Keep the Working-Model relation canonical; recover the direct relation facts and reidentification rule independently; attach the trace only as their inspectable C.2.1 account.
Unchecked relation label or modeA familiar relation label or axiomatic flag is published as though either settled relation obtaining or identity.State and test the direct relation first. When B.3.5 is elected, add the branch-specific mode and support account. Stop when a fact required by the direct pattern is missing.
Order/time leakageSequence, phase labels or parallel timing are treated as sufficient evidence of parthood.Recover each direct relation separately: A.15.1 for Work parts, A.14 for a proper phase of an unchanged non-Work carrier, and B.1.4 for aggregation of recovered order or temporal relations.
Assurance by notationA diagram, graph display, or data format is treated as if it made the relation true.Use the diagram, graph display, or data format to present the relation claim; keep the grounding relation and validation mode explicit.