Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:20:20 UTC

F.9:8 - Bridge occurrence, description, Card, and publication

Recover and, when needed, individuate the direct relation before describing it. A Bridge may obtain without any assertion, description, Card, registry row, or publication.

A Bridge occurrence description is constituted independently under C.2.1 from its complete interpreted claim content, the already individuated occurrence as EntityOfConcern, and its effective interpretation rules (ReferenceScheme). Its content and rules satisfy the C.2.1:4.1.2 ranges; each endpoint cell retains its own scheme and exact local sense.

A proposal may instead be a modal C.2.1 episteme whose EntityOfConcern is the admitted direct Bridge relation kind and whose ClaimGraph designates proposed endpoints and profile; it supplies no positive occurrence reference and makes no relation obtain.

Use a Bridge Card only when durable reuse, delayed handoff, evidence review, audit, publication, or costly reversal makes reusable packaging worthwhile. A particular filled Card’s claim-bearing account can be the description episteme when its C.2.1 identity supports that exact use. Identify its particular expression separately from the reusable layout rules. PublicationExpressionRelation states which claim content can be recovered from the expression for the bounded use, and PublicationFormConformanceRelation states whether it follows the selected Card form. That expression witnesses the form-mediated PublicationFormExpressionRelation; use the same expression for any carrier-bearing claim relied on for availability.

When availability matters, publish one selected description/Card edition through E.24.PUB: its EpistemePublicationRelation occurrence, particular expression, reusable form, and independently identified physical or digital carrier remain distinct from the selected episteme and from the Bridge.

BridgeCard:
  ClaimMode: actual | candidate | negative
  BridgeOccurrenceRef?: exact ref, actual mode only
  EntityOfConcern: exact obtaining Bridge, or admitted F.9 Bridge relation kind for candidate or negative mode
  ProposedSourceSenseCellRef?: SenseCellAddressRef
  ProposedReceivingSenseCellRef?: SenseCellAddressRef
  ProposedBridgePredicateProfile?: by-value profile
  BoundedUseClaims?: each with u, d, r, t, polarity, and effective ReferenceScheme
  A10EvidenceUse?: descriptive evidence-provenance path citing independently established direct relations, plus local RelianceDisposition
  B3Use?: exact AssuranceResult for the same bounded assurance use
  ObservedLossAndCounterexamples?:
  EvidenceWarrantAndCurrentness?:
  NearestNonUse?:
  CardReferenceScheme: EpistemeInterpretationScheme, byValue // rules interpreting this description/Card's complete claims

For ClaimMode: actual, the description/Card episteme’s exact EntityOfConcern is the already individuated Bridge occurrence.

In actual mode, the description/Card may package the Bridge assertion, one or more bounded-use propositions, their evidence and polarity, the descriptive A.10 evidence-provenance path, the independently established direct relations it cites, and local disposition, or the exact B.3 AssuranceResult when an actual named assurance claim is current, plus currentness and nearest non-use. Its C.2.1 identity is not the occurrence identity.

For ClaimMode: candidate or negative, no positive occurrence reference exists. The modal description/Card episteme’s EntityOfConcern is the admitted F.9 direct Bridge relation kind; its ClaimGraph designates the proposed endpoints and profile. candidate says the proposed Bridge may obtain; negative says its predicate does not obtain. Any bounded-use proposition in the same graph keeps its own polarity. Completing, approving, registering, or publishing the description/Card creates no Bridge.

The exact <ClaimGraph, EntityOfConcern, effective ReferenceScheme> triple identifies each description/Card episteme. A changed description or Card edition, evidence path, reliance disposition, B.3 AssuranceResult, registry record, E.24.PUB publication occurrence, publication form, carrier, or layout does not reidentify a fixed Bridge. Publish only the selected description/Card edition needed by the named audience and bounded use; publication changes availability, not relation truth.