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

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 08:26:30 UTC

F.9:15 - Relations

Builds on: F.17, F.18, C.2.1, F.0.1, F.7, and F.8.

Coordinates with:

  • A.10. Use it for the descriptive evidence-provenance path, the independently established direct relations it cites, and local RelianceDisposition for ordinary bounded evidence use.
  • B.3. Use B.3 only after an actual named assurance claim is current; it states the bounded AssuranceResult or non-positive disposition and does not create the claim, authorization, or use.
  • E.10.ROLE, A.2, C.3, F.4, F.5, A.13, A.15.1, A.2.1, and F.6. Use E.10.ROLE first when source wording leaves role ambiguous. Use A.2 and C.3 for the local system-role kind and any separate System-classification judgment. Use F.4 only when a description of that kind is current, and F.5 only when its durable naming is current. Recover each exact actual performer through A.13 and admit dated Work independently through A.15.1. A.2.1 governs the assignment species and obtaining occurrence already required by the A.13 core. Add F.6 only when the receiving Bridge use expressly consumes precise assignment-bound attribution through that same assignment. A Bridge establishes none of these facts.
  • F.8. A mint-or-reuse decision may consume an obtaining Bridge plus a separately warranted bounded-use claim; it does not strengthen either.
  • A.2.6. Scope translation may use an obtaining Bridge only together with an affirmative claim naming the exact direction, scope-correspondence rule, and loss tolerance. Use A.2.6 for the translated scope and membership.
  • A.6.1. Use it to identify any actual operation application. The u designation in a Bridge claim names a proposed use and is not an application binding.
  • A.6.5. Relation-position labels and SlotSpec claims remain governed by slot discipline.
  • C.29. Mathematical-lens use may cite a Bridge and bounded-use claim; C.29 still governs its mathematical object, preserved and lost structure, and actual lens use.
  • C.34. Structural correspondence or morphism adequacy may cite an obtaining Bridge and a bounded-use claim but states its own preserved and lost architecture structure.
  • A.6.REL. Applies the F.9 recurrence and occurrence-identity rule only when a receiver must distinguish or reference the occurrence.
  • C.2.1. Independently constitutes assertions, modal proposals, occurrence-description epistemes, and filled Cards; none supplies the Bridge predicate or occurrence identity.
  • E.24.PUB. Use it for any EpistemePublicationRelation occurrence, publication form, and presentation carrier for a selected description/Card edition. Publishing creates neither Bridge nor receiving use.
  • A.6.3.CSC, C.26.1, and C.26.2. Govern coarsening, probe effects, and no-faithful-enough-report cases when those questions are live.