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

C.22:8 - Common Anti-Patterns and How to Avoid Them

CountercaseRepair
A preferred method or strategy name is inserted into S2 before eligibility is tested.Remove the method value, restore the exact problem traits, and let A.19, C.23, G.4, and G.5 govern later comparison and selection.
A live unknown is encoded as false, 0, or an empty value.Restore unknown, name the direct basis relation and receiving-use policy, and let the downstream pattern produce the result governed by that policy.
Ordinal values or values with unlike units are averaged into one score.Recover scale, unit, polarity, reference plane, and admitted order for every head; use only a directly governed admissible comparison or leave the candidate set partially ordered.
One TaskSignature mixes design-time traits, later run observations, and incompatible DesignRunTag positions.Split the claims by their actual Work and relation positions; retain only the traits current in this signature edition. Use E.18 only when a selected transformation-flow relation is current, F.9 only when exact local meanings differ and its Bridge predicate is true, and the Work pattern for the actual run.
A new file, card, or database row is treated as a new TaskSignature.Compare the declaration content, exact task or work target, and effective reference scheme. Reuse the same identity when only publication, carrier, serialization, or designator changed; identify another episteme when an identity component changed, then apply C.22:5.2’s signature-membership and edition-continuity checks.
A broad domain, organization, or location label is used as if it supplied scope, measurement, evidence, or selection rules.Recover the exact EntityOfConcern, effective ReferenceScheme, A.2.6 ClaimScope relation, U.Discipline when current, characteristic rules, and direct selector or policy relations that the use actually needs.
Data shift is assumed away because the old profile used iid.State the current ShiftClass or unknown, cite its evidence and currentness relation, and state the changed-use result under the exact acceptance or selector predicate.
A vendor, tool, or fashionable method label is treated as a normative selector input.Keep it only as a Plain example or recover the exact method-description, capability, evidence, and selector relations on which comparison relies.