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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 07:42:37 UTC · snapshot created 2026-10-03 07:43:27 UTC · last check 2026-10-03 08:00:10 UTC

A.3.4:0 - Use This When

Use this pattern when a project must decide whether an actual change occurred and identify that one change. Ask: what continuing subject changed, where the change begins and ends, which facts differ before, during, and after it, and what rule makes this one occurrence rather than unrelated observations.

Use it when the working question is:

  • what continuing subject changed: an entity, selected structure, presentation carrier, constituent organization, characteristic-bearing referent, or formal object;
  • when a specification’s claim content changes, which two C.2.1 epistemes exist, whether their EpistemeEditionRelation obtains, whether a continuing carrier or constituent organization changed, and whether revision U.Work first constituted the later episteme under A.15.PROD;
  • which actual characteristic-state and direct-relation facts differ across the boundary;
  • what temporal extent, formal ordering, or continuity rule identifies this occurrence;
  • which additional claim, if any, is actually being made about method, planned work, performed work, mechanism, flow structure, representation, evidence, publication, or a later use, and which pattern answers that claim.

Primary EntityOfConcern. One actual U.Transformation: the bounded occurrence identified through the five checks in 4.1. Identify the objects needed for separate planning, enactment, representation, evidence, or later-use claims under their own patterns.

Primary working reader. A practitioner or modeler who must identify one actual change for a current engineering, scientific, formal, documentary, or architectural use before relating it to method, work, flow, evidence, or production. The parked-composition branch additionally addresses an FPF author or reviewer only when that use asks whether several changes compose one change or whether that whole could satisfy A.1.

First useful move. Name the continuing subject and where the change begins and ends. Write the subject facts that hold before, during, and after that boundary, then state the boundary conditions and the continuity or reidentification rule that make this one occurrence. If the material supplies only a desired state, method, plan, model, trace, or assertion, stop: it has not yet grounded an actual U.Transformation.

Open-world guard. Not finding a method, work occurrence, evidence item, publication, delivery, acceptance, or later-use relation does not prove that it is absent. It prevents only the particular claim that needs it. Finding one of those objects likewise does not prove that an actual transformation occurred.

What goes wrong if missed. Method names become change proof, work traces become laws, process diagrams become execution, dynamics models become permission, temporal trends become intervention claims, mathematical constructions become project-world work, and publications or result records are treated as the change itself.

What this buys. The practitioner gets one usable actual-change result without first deciding whether finer changes are its parts. If no composition or holon claim is needed, continue with the ordinary neighboring-object guidance at 4.3. If such a claim is needed, keep the identified changes and return the parked composition blocker; this pattern does not guess the future architecture. Apply A.1 only after an accepted architecture supplies the proposed whole and its construction facts. Method, work, flow, representation, evidence, publication, production, and later-use claims stay separate.

Not this pattern when.

  • If the issue is only a semantic way of doing, use A.3.1.
  • If the issue is a description of that way, use A.3.2.
  • If the issue is a state-space and transition-law episteme, use A.3.3.
  • If the issue is a law-governed operation algebra with admissibility predicates, use A.6.1 and E.20.
  • If the issue is planned or dated work, use A.15.2 or A.15.1.
  • If the issue is the selected compound transformation-flow structure, its locus, path, path slice, crossing, or flow valuation, use E.18.
  • If the issue is a graph, algebra, category, tuple, morphism, quotient, fold, refinement, factorization, or wiring expression used to describe that structure mathematically, use E.18.2 and C.29.
  • If the issue is a positive temporal aspect of an object or claim, use C.27.TA.
  • If the issue is adequacy or admissible use of a temporal claim, use C.27.
  • If the issue is holon recognition without a current actual-change identity or constructive transformation-parthood claim, use A.1.