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

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:55:09 UTC

E.18:11 - Rationale

E.18 states strict separation of concerns (selected-structure scope only); the patterns named below supply the definitions and tests for those current relations:

  • What the selected structure is: structure-positioned transformation and slot-filler loci plus the single relation kind U.Transfer; graph, morphism, tuple, category, or algebra language is used only when a current mathematical description or lens expresses the relation.
  • Where and when structural state changes: only at one OperationalGate(profile), with exact source and receiving positions, changed CtxState bindings, a per-binding account for each change, and CrossingRef. GateDecision and any permission claim remain separate; an F.9 Bridge, bounded-use claim, reliance, optional card, and optional CL appear only for a separately established cross-semantic use.
  • How comparability works: UNM is the single declaration locus for unit, plane, and transport declarations, and selectors operate only on normalized, edition-pinned comparators, returning sets or archives rather than totals. Edition-aware pins and archive semantics are checked through A.19.SelectorMechanism, C.18, C.19, G.5, G.9, and G.11 for current selector or archive cases.
  • How change propagates: sentinel-bounded PathSlice refresh; editions are monotone. When the selected structure contains an exact current LaunchGate relation for one prospective workEntryClaimRef, that gate is the pre-run decision locus for that claim. Actual launch values are established only through independently obtaining direct relations or A.6.1 bindings involving a later Work occurrence and may be cited by a separate finalization witness.

This arrangement gives checkable conditions for functorial publication on crossings and keeps inner constraint validity distinct from profile fit. A.21 can therefore aggregate mapped check results without evaluation order changing which independently established facts remain available.