fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 18787–18799

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

A.6.P.WMR:8 - Common Anti-Patterns and How to Avoid Them

Informative misuse examples. The Repair column describes the outcome of applying the checklist; it creates no additional imperative or world-side fact.

Anti-patternSymptomRepair
Boundary word as kindInput, Output, Result, or Handoff is used as the entity kind.The repaired claim restores the entity’s admitted kind, related object, direct relation, orthogonal claim dimensions, and governor.
Plan as actualityA planned filling, work-package row, or intended deliverable is treated as an actual participant or result.Intended relation content stays under the plan; actuality opens only from direct obtaining facts.
Binding as productionAn operation result binding is treated as proof that work produced or constituted the bound entity.The repaired claim states only the binding; A.15.PROD opens separately when exact production facts make that question current.
Result record as result relationA report, log, or evaluation-result episteme is treated as the changed entity, work, or direct subject relation.The repaired claim identifies the episteme and its claim content, then keeps any work, change, measurement, or evaluation relation separate.
Local id used as ontologyA project id or assertion id is cited where the RelationKind, obtaining predicate, relation-declaration episteme, or SubjectPatternLocator is needed.Name the token and its exact reference scheme or resolver; keep any occurrence, assertion episteme, and local id separate. When no current exact predicate source exists, return the established missing-governor result.
Missing governor hidden by hypernymA broad word makes an unresolved relation look complete.The repaired result records exact participants, proposed predicate, obtaining question, affected use, and absent definition, applicability, or occurrence rule; a future definition need is optional.
Composition by proximityShared work, time, flow, or referent is treated as transformation composition.The repaired result keeps independently identified transformations and returns the exact composition blocker.