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:45:20 UTC

B.2:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Emergence by adjectiveA capability or property is called emergent without reidentifying the whole.Use B.2.P to recover claim kind, then B.2 only if whole reidentification is current.
Record as ontologyTrigger profile, result field, or record name is treated as a world-side kind.Keep the trigger profile, optional explanation result, and reidentification record as U.Episteme values; keep the ordinary comparison as an action. Let E.24.UK handle the candidate new whole’s public kind and A.1 recognize that candidate.
Content field as relation slotA reference field inside a profile or record is treated as a participant SlotKind or as evidence that the referenced relation obtains.Keep the field in episteme content, resolve its reference to the direct occurrence, and use that occurrence’s subject pattern for obtaining and identity.
KPI jump as MHTA metric improves and MHT is declared.Perform the ordinary existing-whole comparison; use the direct measurement, characteristic, Method, Work, or architecture pattern when it explains the change.
Agency shortcutAgency threshold crossing creates a new root kind.Use the direct characteristic-space and threshold patterns; apply B.2 only when closure, supervision, objective, or identity changes.
Math result as MHTGraph, RG-like, MSPD, or benchmark expression declares new whole.Use C.29; recover holon identity before B.2.
Transformation as containmentA system changes another holon and is treated as its part or containing whole without a separately obtaining part-whole relation.Use A.12, A.3.4, A.15.1, and the direct crossing relation pattern; use parthood only when an exact grounded part relation independently obtains.