Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

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 07:40:10 UTC

F.9:25 - Bridge Card publication discipline

F.9:25.1 - Minimal truthful card

A reusable description/Card states its mode and exact C.2.1 identity. An actual one names its already individuated Bridge; a candidate or negative one names the admitted direct Bridge relation kind and modally designates proposed endpoints, profile, and polarity in its ClaimGraph. When it packages a proposed use, it states u, d, r, t, polarity, observed loss, evidence, currentness, nearest non-use, and the exact A.10 disposition or, when an actual named assurance claim is current, its B.3 AssuranceResult. Missing relation facts are never repaired by filling more fields. If availability matters, E.24.PUB publishes the selected episteme edition for one declared audience and bounded use through its independently governed publication occurrence, form, and carrier.

F.9:25.2 - One occurrence, several claims and descriptions

Several bounded-use claims, cards, reviews, or publications may concern the same actual Bridge. Their C.2.1 identities differ when their ClaimGraph, EntityOfConcern, or effective scheme differs; the Bridge identity does not. Prefer one primary current card only when it reduces navigation cost.

F.9:25.3 - Revision without silent ontology change

If evidence, observed loss, reliance, assurance, wording, or publication changes while endpoints and profile remain fixed, revise the corresponding claim, evidence relation, disposition, card, or publication. Test another Bridge only when an endpoint or relation-semantic profile component changes.