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:40:10 UTC

C.2.P.DR:7 - Common anti-patterns

Anti-patternSymptomRepair
Path word deletionEvery path is replaced or avoided.Preserve legitimate A.10, E.18, carrier, mathematical, URL, and quoted-source path uses; repair only hidden stronger claims.
Imperative metaphor as ontologyRepresentations “route”, “call”, “dispatch”, “receive”, “invoke”, or “flow” by prose habit.Separate the visible expression, direct object or relation, exact representation use or none, and blocked stronger action claim; then write the direct relation declaratively.
Algorithm as method or description by formCode, solver model, proof script, workflow, SOP, recipe, protocol, or diagram form is treated as proof of U.Method or U.MethodDescription.Use A.3.1 only for the recovered reusable way of doing. Use A.3.2 only for an already identified claim-bearing episteme with one admitted U.Method as exact EntityOfConcern and a substantive way-of-doing claim; otherwise keep the representation or other claim with its subject pattern.
Mechanism by prestigemechanism is used because the word sounds more rigorous than method or algorithm.Require operation algebra, laws, admissibility predicates, transport, audit, realization, or governing-definition assignment.
Dashboard as gateGreen status, dashboard tile, score, or status label becomes permission or release.Recover source relation or publication relation, state-family value, evidence relation, and gate or release pattern when current.
Pattern dispatcherPattern relations are given action or control effects through route, exit, receiver, call, owner, or home wording.Write declarative neighboring-pattern boundary or application relation; use E.8 and F.19 together when both publication-form and phrase-apparatus claims are live, or use the one subject pattern when only one claim is live.
Generic representation theoryThe repair tries to classify every representation in FPF or becomes an API pattern, schema pattern, legal framework, workflow framework, or generic admissibility pattern.Stop at the representation-use field set and use the subject pattern for the current claim.