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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:15:20 UTC

A.3.4.P:4.4 - Functional change-situation settlement

When change-situation wording includes function, functional, functioning, transforms, or implements, use this pattern only to recover the exact current claims:

  • Is one actual bounded U.Transformation established by changed referent, temporal or formal boundary, boundary conditions, actual subject facts, and continuity or reidentification?
  • Is a selected TransformationFlowStructure current without being treated as the acting system or the change occurrence?
  • Is performed Work being attributed to a System? Recover each precise performer’s A.13 core and independently admit the Work under A.15.1. Add F.6 only when precise assignment-bound attribution is current, then state separately the realization, causal, production, or other Work-to-change relation required by the claim. An assignment occurrence, Work record, common timestamp, or generic transformation-participant fact does not prove performance.
  • Is a non-work functional or physical actor-side claim current? Recover the exact system and the participant, operation-application, functioning, causal, or other direct actor-side relation supplied by its governor. If no actor-side governor is recoverable, leave the actor claim unresolved.
  • Is a distinct influence source current? First recover its exact kind. A manufacturing, certification, or design organization may be a System under its direct admission pattern; a toolchain or communication System needs its own admitted kind; a selected structure remains a structure; and a Method or Method family is not a holon by label. State only the exact architecture, Work, communication, constraint, or candidate-synthesis relation current for that value. Influence alone establishes no local system-role kind, separate System-classification judgment, assignment occurrence, Work, acting fact, or transformation participation.
  • Are exact participant, port, operation-application, relation-signature, or functioning relations current at the boundary? Keep them under their direct governors; a transformation input or output requires its own direct relation.

Do not introduce a TransformerHolon kind, a generic transformer role, or a universal architecture-influence relation to bridge these claims. After recovery, apply A.6.F when the question is which function-like kind or relation is being claimed. A.3.4.P selects the direct governor for each recovered claim.