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

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

E.18.NET:4.5 - Preserve the direct cross-flow relations

For every relation used by the network, recover:

  • the exact obtaining occurrence;
  • the exact relation kind;
  • the pattern that defines or tests its predicate, applicability, and occurrence-identity rule;
  • the complete participant signature and participant order;
  • the endpoint member and position binding for every participant; and
  • direction only when the direct relation has direction.

An n-ary relation remains n-ary. Do not decompose it into invented binary arrows. A row, edge label, shared entity, temporal adjacency, operation result, plan row, or graph connection never makes the relation obtain.

U.Transfer remains E.18’s internal relation kind for one TFS. It is not a universal relation between network members. For any production, use, participation, evaluation, correspondence, feedback, dependency, supply, or other cross-flow relation, the relation kind must already be admitted. Use its applicable relation pattern to recover the participant meanings, predicate, applicability, and occurrence-identity rule; current case facts or constituting history must satisfy the predicate affirmatively. Only then does one world-side occurrence obtain. Use A.6.REL only when a named use must distinguish that occurrence from another. For ordinary network selection, the PatternID and exact relation occurrence are enough; add relationFunctionClaimRef to the defining or constraining ClaimGraph only when comparison, migration, or reliance depends on that exact rule identity. The network selects only the exact already-obtaining occurrence ref.

If no admitted relation kind and applicable predicate cover the intended participants and use, carry missing-governor from the pattern governing the relation claim. If required case facts are unavailable, carry its missing-information result; if the available basis is sufficient to apply the positive test but that test fails, carry factually unsupported. Neither result by itself establishes a negative. Carry an inapplicable or negative result only when the governing pattern defines that outcome and its current basis establishes it. Only a positive obtaining occurrence may fill selectedCrossFlowRelationOccurrenceRefs[].

After a positive occurrence is established, test the E.18.NET endpoint and position bindings separately. A missing binding blocks network selection but does not change the relation result. Missing members, applied constraints, and use-frame values are likewise separate network-selection blockers. A row, graph edge, or episteme neither admits a relation kind nor creates an occurrence. In none of these branches substitute creates, produces, uses, input, output, result, handoff, or transfer as a generic edge.