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:16:27 UTC · snapshot created 2026-10-03 05:17:06 UTC · last check 2026-10-03 05:16:56 UTC

F.17:13 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsRepair
Global glossary rowRemoves the exact governed value, scheme, and local-sense claim.Recover the exact value and one scheme-based cell; keep local wording local when that suffices.
One row for system-role kind and statusFuses a work-facing system-role kind with a state-family value.Split the rows and use the pattern that defines or constrains each value.
Evidence-role bucketTurns evidence use, source use, assurance, and Work into one pseudo-kind.Recover each claim under A.10, B.3, E.10.D2, or the pattern that defines or tests the source or Work claim.
Automatic card-cell-row chainTreats the presence of one naming object as need for the next.Apply F.14 separately at each gate and stop at the lightest sufficient object.
Merged viewpoint/view/conformance rowA dependent kind, another dependent kind, and their direct relation are treated as one naming result.Keep separate U.Viewpoint, U.View, and EpistemeViewpointConformanceRelation rows and use E.17.0 for every membership or obtaining claim.
Spelling or suffix identityLets a familiar label, stable id, or ...@Context form create or merge values.Resolve the value under the pattern that defines or constrains it and treat only tokens fixed there as lineage.
Borrowed locality label as Tech nameImports one tradition’s commitments into the row and hides the effective interpretation basis.Recover the governed value and scheme-based cell; select the designation under F.18 and cite an actual F.9 Bridge only when its separate predicate and use conditions hold.
Basis by source titleReplaces the exact cell and actual basis relation with a file or citation.Recover the cell and two-participant basis relation; keep source-unit and publication facts separate.
Row as publicationTreats table presence, rendering, upload, form, or carrier as availability.Use E.24.PUB for the selected row edition, audience, bounded use, form, and carrier.
Block as ontology or completeness proofTreats navigation as subtype structure or row count as value evidence.Keep blocks optional and judge the exact row use through reader recovery and blocked-use avoidance.
Row without its defining or constraining patternLets F.17 govern the named object.Point to the pattern that defines or constrains the value or stop the public-row path.