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

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

A.6.9:4.1 - Stable lens: relation, use claim, reliance, and receiving object

Keep these objects distinct:

  1. Bridge occurrence. The direct relation has exactly two F.17 cell participants and obtains under one exact F.9 profile.
  2. BridgePredicateProfile. It contains only Bridge kind, kind-defined symmetry or orientation, endpoint-sense readings, relation-specific correspondence or difference condition, applicability and as-of basis, Boolean truth condition, and stop dependencies.
  3. Bounded-use claim. An ordinary C.2.1 claim says whether the exact obtaining Bridge is suitable for <u,d,r,t>. Its EntityOfConcern is the Bridge; its ClaimGraph designates the use, direction, rule, tolerance, and polarity; its effective scheme interprets them.
  4. Optional Bridge Card. It packages claims and evidence when durable reuse pays. It neither creates the relation nor grants the use.
  5. Separately governed receiving object. If the use happened, its Work, assertion, publication, direct relation, operation application, or other object keeps its own participants, obtaining or performance condition, and identity.
Bridge(SourceSenseCell, ReceivingSenseCell; BridgePredicateProfile)

Use that notation only after the F.9 predicate passes. For a proposal, write candidate Bridge(...) or use a candidate card with no positive occurrence reference.

Changing u, d, r, or t changes the bounded-use claim, not the Bridge. Changing evidence, an A.10 relation or local RelianceDisposition, or a B.3 claim, record, or disposition reopens reliance without reidentifying the Bridge or the bounded-use claim. A changed endpoint or relation-semantic profile identifies another Bridge candidate.