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 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 20:05:10 UTC

E.10.MOVE:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsBetter use
Synonym replacement“Move” becomes “action” or “use” without recovered kind.Recover governed text span, claim being made, object under wording repair, relation, and subject pattern first.
Imported MOVE kindTameFlow source wording becomes FPF ontology.Recover intended work, readiness, gate, preparation work, or performed work.
Readiness as gate passageA ready label is taken to establish a GateDecisionResult with decision pass.Recover the applicable A.21 profile, complete required check set and mapped decision. Readiness supplies only the input that the profile actually consumes.
Path as work-authorization routeEvidence path or source-reference path becomes a way to authorize work by resemblance.Recover evidence relation, source relation, graph path, gate relation, work authorization, or deontic permission separately.
Local expression generalizedA bounded local phrase is generalized to unrelated project work.Preserve the chosen branch: a post-qualification E.11.PUA continuation description, a Plain local mantra tied to its bounded result, or a Plain long-mantra map tied to its current answer or stop. Recover each claim through its own direct pattern.
Trajectory shell generalizedOrdered points, paths, plans, histories, lineages, and archive or front succession are treated as one world-side kind or Method.Recover the direct claim and owner, then the subject, identity or continuity, reference order, posture, and receiving-use distinctions it needs; keep only a declared C.29 representation relation when that is the actual claim.