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 08:50:20 UTC

A.15.3:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternFailureRepair
Generic slot-bearing descriptionAny description with fields is treated as a reusable declaration.Point to a declared RelationSignature SlotSpec, A.6.1 argument or result, or another member whose pattern defines its meaning and actual use.
Dependent PlanItem U-kindA ClaimGraph component receives a rival identity and ontic settlement.Keep SlotFillingsPlanItem as declaration-local WorkPlan content.
Planned SlotRelationThe plan claim is reified as an obtaining world-side relation.Keep planned filling as positive claim content; open an actual relation only under its direct predicate.
Declaration/plan responsibility blurThe declaration pattern is said to make the planning intention, or A.15.3 is said to define actual use.Let the declaration pattern define member meaning and actual-use predicate; let A.15.2 and A.15.3 state the intention.
Method-description slotGeneric method wording is mistaken for a declaration member.Keep it as ordinary plan content or return missing-governor when typed reuse is required.
Relation/operation collapseA.6.1 arguments and results are written as A.6.5 SlotSpecs.Dispatch by target family and keep each declaration vocabulary local.
Row-count cardinalityRow count or order silently defines multiplicity, alternatives, or sequence.Use the declaration’s cardinality; for alternatives, state conditions and a resolution rule.
Empty filler as prohibitionOmission, null, or a negated reference is read as must not use.State prohibition, exclusion, required absence, or completeness as a separate plan claim.
Plan-as-actualA planned value is treated as actual participation or a returned result.Identify work and actual relation or application bindings independently.
Generic reference or policyRef, SpecRef, PolicyRef, or a shared label is treated as sufficient.Use the concrete RefKind and identify the policy’s kind, defining pattern, edition, applicability, and reference scheme.
Latest-as-baselineA mutable label stands for a declaration or value edition.Pin the edition when choosing another one could change the planned or comparison result.
Backfilled planActual values replace planned rows after work.Preserve the cited plan edition and state a neighboring substitution or variance claim.