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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:01:07 UTC · snapshot created 2026-10-03 08:04:31 UTC · last check 2026-10-03 08:20:20 UTC

A.7:5.2 - System-role kind vs function-like wording, functional behaviour, capability, method, and work

  • System-role kind. One local U.Kind with U.System candidates and an operative condition for a stable, assignable, work-facing contribution. Its member/non-member boundary and continuity rule complete the C.3 recovery. A practice or source reference locates the definition; it does not identify the kind. An obtaining assignment occurrence may relate a system to that kind only through a directly admitted U.SystemRoleAssignment species. The kind is not behaviour. Example: the kind currently named CoolingCirculatorSystemRole, whose ThermalLoop-7 provenance locates one definition.
  • Function-like wording. A source phrase such as “function”, “behaviour”, “service”, or “does X” may name a required transformation or effect (A.3.4), functional behaviour (A.6.F), a capability envelope, a method, performed work, a quality, or a structure. Recover the governed claim before choosing the FPF term.
  • Under a system-role assignment. A System or acting holon that holds an assignment may have a Capability to enact a Method under conditions. A precise Work claim still uses A.13 to identify the actual performer and A.15.1 to admit the dated occurrence independently. Add F.6 only if the claim must also identify the assignment under which that Work was performed. The system-role kind, assignment, Method, Capability, transformation, and effect do not substitute for the Work or performer.

Safe rewrite for earlier “Holonic Duality (Substance vs Function)”: Holonic Duality (Substance vs system-role kind). A U.System keeps its identity while its classifications and obtaining assignments change. A contribution named by a system-role kind may call for a Method, a Capability envelope to enact that Method under conditions, and possible Work occurrences; none follows from the kind alone.

Normative guard: Use system-role kind for that exact local U.Kind, an admitted direct species under U.SystemRoleAssignment for assignment occurrences, functional behaviour for a behaviour claim stated with A.6.F, Method for the abstract way-of-doing, Capability for a holder System’s bounded ability or envelope for a Work family or result class under stated conditions, Work for the performed occurrence, and Transformation or effect wording for an actual change identified with A.3.4. Do not call the kind or assignment itself a function, and do not define Method as Capability or as the transformation or effect itself.