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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 10:50:05 UTC

A.6.5:4.8 - Recover interface and port relations before declaring slots

Keep recognizable source words such as interface, port, endpoint, API, and signature in the recognition sentence; do not erase them and do not promote them into a generic U.Interface. Then use this sequence:

  1. Repeat the source sentence so the practitioner can still recognize the situation.
  2. Say in ordinary language what connects, crosses, or is transferred between which exact entities.
  3. Recover the exact direct relation and its definition. If no current definition supplies the needed participant meanings, predicate, applicability, and identity rule, require A.6.RSIR or record one missing-relation result naming the proposed participants, required predicate, and receiving use.
  4. Only after the direct relation’s definition is recovered, let its RelationSignature declare the SlotSpecs for participant meanings actually reused by the receiving typed claim.

Compact contrast. In “the evaporator outlet interfaces with the compressor inlet,” keep interfaces for recognition. If the intended claim is that refrigerant crosses from one named outlet to one named inlet, name that medium and those two endpoints and recover the exact transfer-relation definition before declaring any slots. If interface instead names a diagram boundary, API description, protocol, or publication form, use the definition for that object and use. A catalogue of possible participants closes neither branch; without a definition of the direct relation, stop before a RelationSignature.