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 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:35:10 UTC

A.6.REL:4.1.4 - Claim and description epistemes
Canonical FPF nameWhat this object isDirect relation to preserveNaming ruleSubject pattern
relation-participant designationa value or governed reference in a receiving episteme; it retains its own value kind or RefKinddenotes the actual relation participant through the content position corresponding to one declared SlotSpecname the value or reference under its own governor and effective reference scheme; if a concrete representation field carries it, keep that field’s source name and state the explicit declaration or representation correspondence to the SlotKind; equal spelling is only a representation choice, never object identityC.2.1, A.6.5, and F.18 when durable naming is current
relational assertiona claim-bearing U.Epistemeits content states affirmative or negative assertion polarity for the direct obtaining predicate with relation-participant designations; an affirmative assertion may designate an already individuated occurrence only after current case facts or constituting history satisfy that predicate and the direct identity rule has been applied; the assertion states that result; assertion form alone does not establish or constitute the occurrence; a forecast, scenario, counterfactual, permission, or other claim family keeps its own direct semantics, while supported, refuted, or unresolved reliance belongs to A.10 or the receiving evaluationname the asserted direct relation and its polarity; name the exact direct claim family whenever ordinary affirmation or denial is insufficientC.2.1, the direct claim pattern, and A.10 or the receiving evaluation for reliance
relation-occurrence description epistemea U.Episteme whose EntityOfConcern is one explicitly individuated relation occurrencedescribes that occurrence without replacing it; description form alone does not supply occurrence identityuse description of <relation-occurrence designator> in readable prose; give a reusable description-episteme kind its own governed name only when another use depends on that kindC.2.1

A receiving episteme contains a relation-participant designation in a content position corresponding to one declared SlotSpec. A concrete representation may carry that designation in a field, but the field keeps its source name and corresponds to the declaration-local SlotKind only through an explicit declaration or representation correspondence. Reusing the SlotKind spelling for convenience does not identify the field, SlotKind, designation, or participant. The designation denotes the actual participant; the participant remains a U.Entity, the obtaining occurrence remains a U.Relation, and the receiving episteme keeps its own C.2.1 identity.