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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:35:10 UTC

A.6.P:4.2 - State the direct relation, participant meanings, and obtaining condition

Write the smallest readable direct-relation sentence that answers the current question:

<actual participant 1> <direct relation predicate> <actual participant 2> ...

Then name the pattern that defines or constrains the direct relation and recover from it:

  • the admitted direct relation kind and its explicit governed RelationKind token;
  • the relation-participant meanings and actual participants, each retaining its independently governed kind;
  • the condition under which the relation obtains and its semantic predicate is satisfied by those participants considered under the participant meanings;
  • applicability, direction, symmetry, inverse law, polarity, and temporal qualification when they change the predicate;
  • the occurrence-identity rule, whether or not the current use needs explicit individuation;
  • when the direct ontology says that a new occurrence is constructed or constituted, the constructor, inputs, construction work or process, and their contribution to occurrence identity.

Every in-scope positive or governed-negative direct subject-relation result names an explicit admitted RelationKind token. When no suitable token exists, first settle the relation value and any required relation-kind admission using the pattern that defines them, A.6.RCD, and E.24; then apply F.8 and, for durable naming, F.18 and F.17. Naming does not admit a kind or occurrence. An exact A.6.1 operation-application binding, local A.15.PROD or A.6.RCD claim, or non-assertability result keeps the semantics defined for that operation, production, or missing-relation claim and is not coerced into this relation-kind family.

An ordinary assertion may name the actual participants directly. When reusable typed use is current, a compatible RelationSignature declaration can restate the participant meanings, obtaining predicate, applicability, and identity rule and contain only the declaration-local SlotSpecs needed by the receiving typed uses. The declaration remains an episteme; it neither makes the relation obtain nor supplies occurrence identity.

Assertion polarity remains claim-side. An affirmative assertion claims that the direct predicate is satisfied; a negative assertion denies it. Refutation or unresolved reliance belongs to A.10 or the receiving evaluation. Denial, refutation, or unresolved reliance creates no negative world-side occurrence.

Do not select ontology from grammar. A verb-shaped phrase supplies neither constructive identity nor agency. Use the pattern that defines, constrains, or tests the relation, object, Work, Method, change, local system-role kind, system-role assignment, or admitted System named by the current claim.