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:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:10:20 UTC

E.24:7 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Shadow-kind by repetitionThe same claim-bearing episteme or reusable publication form appears in several patterns and starts being cited as an ontology object.Apply E.24; either write a durable ontic pattern or keep the coordination in a bounded local episteme under C.2.1.
Draft ToC row as authorityA ToC row is cited as if it supplied current governing text.Treat it as an investigation cue only; use current subject patterns until the pattern exists.
Slot list without identityA pattern lists record fields as if they were SlotSpecs but never states what identifies the proposed ontic.Add the exact identity or constitution rule and the smallest direct-relation set required by named dependent use, or keep the claims and references in a bounded local episteme under C.2.1 without proposing a durable ontic.
Pattern nest as ontologyA numbering or placement group is treated as the governed subject.Name the primary governed subject kind, exact identity or constitution rule, minimal governed relation set, and their subject patterns; keep the pattern nest as publication and specialization placement under E.8.
New name as solutionThe repair invents a smoother term while the typed values remain mixed.Recover the primary governed subject kind, exact identity or constitution rule, minimal governed relation set, and direct governors first; name only after the ontology is settled.
SlotKind label becomes participant kindA declaration-local SlotKind is reused as the world-side participant’s kind.Keep the participant under its subject pattern and keep the SlotSpec inside the separate RelationSignature declaration.
Interface metaphor for slotsA relation-participant meaning, SlotSpec, assertion-side participant designation, or participant-kind constraint is called an interface without a governing interface pattern.Use the named direct-relation or declaration term unless a boundary, module, signature, mechanism, or architecture pattern makes interface meaning current.
Typed paraphrase overloadA readable subject sentence is rewritten as a full chain of kinds, slots, and source-ontology labels without changing the claim.Keep the subject sentence and annotate only the decision-changing slot or value under decision.