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

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 07:40:10 UTC

A.3.2:1 - Problem frame

When the reusable way is still only a candidate. A candidate account or mined behavioural model is not a U.MethodDescription merely because it is coherent, executable, process-shaped, or traceable to sources. First use A.3.1.MR while the reusable way is still being recovered. Apply this pattern only after the account’s EntityOfConcern has been admitted as one U.Method, and only when that same episteme makes a substantive claim about the Method as a way of doing.

Use this pattern when engineers need reusable claims about how one Method is carried out and must keep those claims distinct from the representation, publication, approval, plan, or actual Work through which the Method is discussed or enacted. In FPF terms, decide whether an already identified U.Episteme is a U.MethodDescription: whether its EntityOfConcern is one admitted U.Method and its claims say something substantive about that Method as a way of doing.

Plain reading. A method description is the knowledge object whose claims say how one identified method is done. Code, text, or a diagram may represent those claims; a publication occurrence may make an edition available.

Recognizable working moments include:

  • a maintenance team comparing a revised procedure with the method used to plan the next service window;
  • a clinical team selecting a triage guideline while keeping guideline claims, approval, and patient-specific work separate;
  • a production-planning team comparing scheduling-method claims while the MILP representation and solver runs change.

Use it when the working question is:

  • which admitted U.Method is the episteme’s EntityOfConcern;
  • which claim states the method’s transformation or enactment concern, applicability, precondition, effect, bound, or internal composition;
  • whether anyone is proposing a use beyond membership; if so, what that use is, where it belongs, and which method claims it needs;
  • which C.29 representation corresponds to the claims, which publication occurrence makes the selected edition available, which publication form expresses it, and which U.PresentationCarrier bears that form—but only when the proposed use needs those distinctions;
  • whether two epistemes concern the same A.3.1-identified Method and, separately, whether their claim content is equivalent for the proposed use; the later use sections carry any needed scheme correspondence, evidence-reliance, and assurance checks.

Object being classified. A.3.2 examines one already identified claim-bearing U.Episteme candidate and judges whether that same individual belongs to the dependent kind U.MethodDescription. For positive membership, the candidate episteme’s C.2.1 EntityOfConcern must resolve to one admitted U.Method, and at least one of its claims must concern that Method as a way of doing. The Method is the internal subject of the episteme’s claims, not a second candidate and not the object being classified. A.3.2 adds neither another episteme identity nor a binary description relation.

Primary working reader. An engineer, researcher, publisher, teacher, planner, or auditor who must identify or rely on reusable claims about a method before planning, enactment, comparison, audit, revision, publication, or teaching.

Primary working concern. Identify the claim-bearing episteme and its Method first. When someone proposes a further use, name that use and its subject pattern, then ask which claims the use needs and whether this edition contains them. With no proposed use, stop at membership.

First useful move. Name the candidate U.Episteme. Check two things: its C.2.1 EntityOfConcern is one admitted U.Method, and at least one claim says how that Method is done. If both hold, the same episteme is a U.MethodDescription; if either fails, it is not. Only then, if someone proposes a concrete further use, write that use’s criterion and result as a separate subject assertion under its exact predicate, with an optional subject-pattern locator. Otherwise stop at membership.

What goes wrong if missed. A visible file or diagram is classified by its form, a mere mention is mistaken for a description, or an episteme about a relation structure among several Methods is treated as if it described one composite Method. Planning, enactment, audit, and review then rely on the wrong object.

What this buys. The project can identify, compare, revise, and reuse claims about one Method while keeping representation, publication, planned use, enactment, and evidence use distinct.

Not this pattern when. Do not infer membership from words such as algorithm, program, proof, workflow, process, procedure, recipe, or model. Ask what the sentence actually asserts. If its EntityOfConcern is not an admitted U.Method, or it says nothing substantive about that Method as a way of doing, A.3.2 does not apply. Use the pattern for the actual Method, selected structure, formal declaration, work plan, dated Work, evidence use, or publication use instead.