FPF.Reference:16.7.6 - Why these Method-development questions stay separate
Preface node
heading:fpf-reference-16-7-6-why-these-method-development-questions-stay-separate:1722
What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
Content
A practitioner often receives a proposed Method as a package: a procedure, a diagram, a tool, a training course and a success story. The costly failure is to change the whole package without knowing which contribution is missing. This family separates the questions because their useful results and grounds differ. A truthful description may still describe an unsuitable Method; a suitable Method may have poor support; a well-supported trial may still leave practical worth unresolved.
The gain is an appropriately bounded answer that the owning practice can use to continue its work. The EC-417 application in FPF.Reference:16.9 illustrates how these questions connect. Direct domain work remains outside until a Method-related question blocks it.
Check the subject, receiving use, relied-on conditions and first useful result before accepting a more ambitious account. If a known direct answer already settles the difficulty, stop there.
The cost is maintaining several answers and their dependencies instead of one undifferentiated success claim. Keep them separate only where a difference changes selection, action or reconsideration. C.39.MF selects the Method-development subject needed for the receiving use; A.3.1.QM, C.32.MWA.PP and B.1.5.CM supply qualification and architecture; A.3.2.DE, C.37.MP and A.15.8.MS supply description and support; A.3.1.WT, A.3.1.CC, A.3.1.FT, C.11.MV, A.3.1.MV, A.3.1.MI and C.36.MC separate evidence, judgments and maintenance. RMP.11 can explain why a professional architecture differentiated without treating that history as a justification of its present worth.
Mathematical modeling can contribute both to comparison and to construction. MMP.21 asks which consequences follow from proposed arrangements: does regrouping preserve the answer, can shared resources meet a deadline, or can an intervening operation invalidate a result? MMP.22 uses a mathematical transformation to construct a changed way of working, then returns its preserved properties and changed demands to the practical comparison. A different notation for the same way of working remains a description change.
The mathematical operations are developed in Mathematical Thinking (MATH), especially MATH.17 and MATH.18. Computational Thinking (CMP), including CMP.14, supplies constructions for interactions among computations. FPF C.29 connects a derived consequence to the work it describes. These contributions let practitioners reuse mathematical behavior while preserving the question about the actual method, its performers and conditions.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)