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 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:05:10 UTC

A.6.RSIR:4.2.1 - Relation-defined wording dispatch

When wording derives a qualification, status, or category from participation in a relation, recover the object needed by the next use before naming it:

  1. If the claim concerns an actual entity participating under one named relation-participant meaning, state the direct relation, that meaning, and the actual participant. The participant retains its direct kind.
  2. If reusable typed declaration is current, use A.6.5 for the corresponding SlotSpec inside one exact RelationSignature. Its SlotKind is declaration-local and neither is the participant nor makes the relation obtain.
  3. If an episteme asserts, evaluates, or describes the participation, C.2.1 governs the episteme’s identity and content, while the direct assertion, evaluation, evidence-use, or description family governs the exact predicate, polarity, or use relation. When a compatible SlotSpec is current, A.6.5 governs the participant designation’s ValueKind and refMode discipline; without reusable declaration, the assertion may designate the actual participants directly.
  4. If repeated local quantification over such actual participants is current, use C.3 and C.3.1 for the local U.Kind, membership rule, and extent rule. Neither the participant-meaning label nor the declaration-local SlotKind admits that kind.
  5. If the source exposes a tuple component, argument, edge endpoint, schema field, or other representation position, keep it under C.29 or the exact representation pattern and state an explicit correspondence before an FPF claim consumes it. A value shown at that position establishes neither actual participation nor relation obtaining.

For parameter, argument, or result wording, separately recover the A.6.1 declaration content, one independently identified exact operation application and any obtaining declaration-local binding, and the selected representation position. Open the binding only when the actual bound value matters to a receiving claim. Neither the declaration nor representation syntax establishes the binding; a result binding is distinct from production, a produced entity, a result episteme, evidence, and work.

When a receiving use compares or constrains a whole organization of relation occurrences, A.22 may govern a selected U.Structure. One actual participant, corresponding SlotSpec or designation, operation binding, or representation position does not by itself establish such a structure.