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 09:35:10 UTC

F.8:9 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Suffix mintingA word ending in Role, Status, Graph, Map, or Record becomes ontology.Recover the governed value or relation, subject pattern, and proposed use first.
Evidence-role revivalEvidenceRole becomes a system-role-kind name family.Recover the evidence-use relation; name it only through its subject pattern.
Status-system-role fusionReadyReviewerRole or ApprovedRole names a local system-role kind plus state.Separate the system-role kind from the assignment-state or status-use relation.
Row overuseA public naming row justifies equivalence, system-role assignment, or structural inference.Lower use to the F.17 AdmissibleUse or repair the row and any needed Bridge.
Alias with payloadAn alias changes kind, scope, occurrence identity, use, or authority.Treat it as a different decision; use F.5, F.13, and F.18.
Source prestige mintingA standard or framework term becomes the selected FPF name by prestige.Keep it as source wording, evidence for a local sense, or an alias until the subject and naming use are recovered and a designation is selected.
Review label as contextPatternReview_2026 is used as context, Work, system-role assignment, evidence, or authority.Recover the dated Work, plan or edition, decision-use claim, or naming ReferenceScheme needed by the assertion.
Decision identifier or record as decisionAn identifier or filled record is treated as the decision occurrence or as creating its result.Recover the occurrence through the decision or choice pattern, predicate, actual participants, applicability, and identity rule that establish it. If none is available, return missing-governor; constitute a separate C.2.1 result episteme only when needed.
Naming-object cascadeOne expression automatically gets a cell, NameCard, row, identifier, and publication.Apply F.14 at every gate and create only the next object whose receiving use pays for it.
U-kind comfort mintingA new U-kind is proposed because existing names feel awkward, and F.8 is asked to name or admit it.Return blockOrLowerUse; recover the object through E.24.CD when needed, let E.24.UK settle admission, and reopen naming only for the object named by that stable result.
Policy identifier as magic wordAn identifier is used without a separately resolvable specification, or its mint history is called accountable, cited, replayable, normative, or reusable across the local boundary without an occurrence basis.Supply the specification for every identifier. For the stronger history claim, supply its direct occurrence basis or return missing-governor; a merely local non-accountable identifier does not manufacture one.