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

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:30:10 UTC

F.18:11 - Relations

Builds on F.0.1, F.1, F.2, F.3, F.5, F.8, F.9, F.13, F.14, F.15, C.2.1, and E.24.PUB.

Coordinates with:

  • A.2, A.2.1, A.2.5, A.2.7, A.15, A.15.1, and F.6 for system-role kinds, system-role assignments, assignment-state predicates and direct state relations, relations among system-role kinds and selected SystemRoleKindRelationStructure, system-role–Method–Work alignment, performed-Work occurrence grounding, and the separate Work-to-assignment attribution;
  • A.3.1 for method and method-family names; A.3.2 for a separately identified U.MethodDescription episteme whose exact EntityOfConcern is that Method, and for the description episteme’s separate name;
  • A.6.P, A.6.P.WMR, A.6.RCD, A.6.REL, A.6.5, A.6.RSIR, A.6.0, A.6.M, A.6.F, and A.6.C for relation-claim settlement, work/method-boundary relation recovery, relation-kind and occurrence boundaries, slot, signature, interface, port, and protocol names;
  • A.2.4 or another direct subject pattern for evidence-use relations; A.10 for their descriptive provenance and bounded reliance; B.3 for an actual named assurance claim; F.10, E.10.D2, and C.2.1 for status-use, source-use, and description-episteme names;
  • E.17 for multi-view publication-face and publication-form use;
  • F.17 only after its current entry accepts the exact F.18 value, kind, card, and sense result and, for reuse between different semantic-context projections, the separate obtaining Bridge, affirmative C.2.1 use claim, and current A.10 or B.3 reliance; otherwise the local NameCard remains sufficient and the public row stays pending;
  • E.24.PUB for the separate occurrence, form, carrier, audience, bounded-use, and currentness objects needed when an exact row-episteme edition is actually made available;
  • C.16, C.18, and Part G search patterns when candidate comparison uses Pareto or quality-diversity vocabulary.

Constrained non-use:

  • F.18 admits no new U-kind and creates none of the governed system-role kinds, assignments, statuses, methods, Work, relations, signatures, slots, interfaces, or other subject values it names. A NameCard is a separately constituted U.Episteme under C.2.1, not a kind minted by F.18.
  • Do not use F.18 to decide whether two locally interpreted values are identical. A Bridge between exact F.17 cells can obtain only under the F.9 predicate; a separate C.2.1 claim states one proposed naming use between those cells, A.10 or B.3 supplies its reliance rule, and any governed-value identity claim must independently satisfy the direct value rules.
  • F.18 does not turn a publication row, card, table, or glossary entry into the thing being named.