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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 10:17:34 UTC · last check 2026-10-03 10:35:10 UTC

A.6.7:12 - Relations

  • Relates to A.6.1: suite members are U.Mechanism; the suite does not replace the mechanism definition.
  • Relates to A.6.5: member operation declarations retain A.6.1 argument/result meanings, ValueKinds and binding rules. A.6.5 applies only where a cited RelationSignature independently declares participant SlotSpecs; there SlotKind stability, correct refMode and non-semantic SlotIndex remain required.
  • Relates to E.18 / P2W: suite protocols describe intended composition; use E.18 for the selected transformation-flow structure and its crossings, and E.18.1 for P2W carry-through.
  • Suite conformance: Suite-level conformance uses the conceptual checklist in §7; suites require pins/anchors rather than procedural validation.
  • Relates to G.10: suites are not packs; G.10 handles shipping of Part-G outputs as a SoTA pack, while E.17 publishes reader-facing forms of an already accepted engineering account.