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:00:20 UTC

E.10.MOVE:12 - Relations

  • Builds on: F.19, E.10, E.10.ARCH, A.3.4.P, A.22.CGUS, E.11.PUA, E.11.PUR, E.23, A.15.5, and E.24.
  • Coordinates with: E.11.PUA for the PatternUsePracticeContinuationDescription@Context shown by a qualified practice continuation; E.11.PUR for PatternUseCoordination@Context, one PatternUseOrderingRelation@Context, or the bounded total-order PatternUseSequence@Context; E.10.DEV when development or evolution wording and trajectory wording carry independent ambiguities; A.1.STM for a non-CGUS system-thinking long-mantra map location; A.3.3, A.3.4, A.3.4.P, B.4, C.27.TA, C.29, C.17–C.19, C.22.2, C.11, A.15.2, C.36, and A.16.0 for trajectory exits; and E.18, E.18.1, A.15, A.21, C.24, C.30, E.17, F.17, F.18, G.11, A.10, and each recovered value’s direct subject pattern. F.18 governs a durable-name decision; G.11 governs refresh orchestration only when currentness, edition, telemetry, freshness, or decay is the actual claim.
  • Selected by: E.10 compact routing when move, readiness, route, path, or trajectory wording still has an unresolved FPF-governed use after the F.19 reading and no direct subject pattern has already resolved it.