FPF.Reference:16.7 - Develop and use methods with distinct claims and results
Preface node
heading:fpf-reference-16-7-develop-and-use-methods-with-distinct-claims-and-results:1660
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
These connected questions help a reader improve a way of working without treating its description, support or observed performance as the same result. The full Methods retain their individual entries; the explanation below shows why their answers can differ and when they need to be used together.
When it is unclear which work deserves improvement, C.39.WI follows work that consumes substantial resources, causes avoidable loss or cannot yet supply a useful result. It compares complete consequences and burden, then selects an attainable Method, explanation, access, provision or execution change, a retained possibility or continuation of current practice. Use C.39.MF when the selected development question still has an ambiguous subject. An adequate professional improvement Method can be used directly.
When a selected failure survives correction, C.39.WI:4.4.1 connects the failed receiving use with the conditions that directed production, checking and the earlier repair. It uses a supported diagnosis to change the operative source or provision, makes that change available in the working form, and follows the changed basis through dependent results. C.28.CM supplies a needed causal distinction, B.5.RR preserves independent grounds during revision, and A.3.1.MI supports introduction and adaptation. Existing adequate results can supply these contributions. A corrected source, restored output, changed performance and worthwhile effect retain separate grounds.
Partial work earns its contribution through a particular relation to the originating question. A model calculation requires a justified return to its subject; a component result requires the whole's composition and operating conditions; a worked case requires an explicit operation and grounds for its wider use. C.39.QR recovers the original question, establishes that relation and its warrant, and separately judges which part of the requested result is now available. A valid subject inference can still leave an explanation or operating capability to be constructed. The next move follows that remaining need.
When the missing result is an account of an organized whole or broad field, C.39.WA develops the common grounds, constituent contributions and relations that make the account useful together. Those grounds explain choices about parts and which choices change with a premise. Findings in the parts can in turn change the common explanation. A discipline's knowledge–practice organization, a Method's obtaining relations and a system's functioning call for different subject constructions. The relevant subject patterns supply them; the common Method preserves the question through their use.
Grounding makes an explicitly explained construction concrete. In a Method explanation, distinguish the reusable operation, its displayed performance and the material worked on during that performance. Choose varied cases for consequential differences within the claimed range, and return from each to what it reveals about the operation and its conditions. Generalization also needs the elements and relations being generalized, the wider class and the grounds for that extension. E.8 and EXD.2 develop these explanatory moves; E.19 and E.21 connect their examination with the promised subject and use.
FPF.Reference:16.7.1 - Method, MethodDescription, WorkPlan, and Work remain distinct
A Method is a reusable way of doing. A MethodDescription is an episteme about one admitted Method. A candidate Method account can be improved, compared, and tested while its candidate status remains explicit. A WorkPlan is about intended Work. To assert a dated Work occurrence, use the full independent A.15.1 admission basis, including its A.13 performer, construction and actual performance, enacted Method, temporal extent and required containing-System relation. Ground its result and any additional relations separately when those claims are needed.
A team that writes a playbook, schedules a trial and publishes the text still needs separate grounds for Method qualification and for actual enactment.
FPF.Reference:16.7.2 - Several structures and several views can coexist
A Method decision may depend on a Method composition structure, a Method unfolding, simultaneous Work, an allocation structure, a subject-and-support arrangement, a description structure, or cultural relations. These structures need not be isomorphic. Name the structure and relation that changes the decision.
Project, process, and case views can expose different claims about the same Work. A project viewpoint may expose dates, allocations, authorities, and decision slots. A process viewpoint may expose recurring input/result and coordination correspondences. A case viewpoint may expose the changing evidence, exception, and next decision.
FPF.Reference:16.7.3 - Reader route and result dependencies do not prescribe Work order
One reading route through this family begins by selecting and recovering the Method-development subject: later decisions need a well-founded account of what is being developed. It then moves through qualification and architecture, description and support, and trial and change. This order helps a reader find prerequisites. Repertoire recovery, description, support repair, trial planning and source refresh can overlap; a known support or evidence defect can be repaired without traversing every earlier pattern.
Begin with the entry that can supply the result needed for the current decision. Follow a dependency only when that result relies on it. Stop when the answer already resolves the working difficulty.
Constituent actions in ongoing work. During a trial of a proposed review Method, asking a participant to explain a unit conversion can constitute part of testing that Method, while the trial constitutes part of developing the team's way of reviewing. If the trial asks about unaided recognition, supplying the conversion during the attempt changes what the trial can establish. The facilitator needs both the subject knowledge and the ability to elicit performance without supplying the answer. C.32.MWA.PP's worked case develops this connection; FPF B.1.5.EW recovers it and B.1.5.RS helps compare a substitute constituent. Preparing the trial remains earlier work, not an activity presumed to continue throughout it.
Learning to recover and change a way of working. If you know the work and want to learn how to explain and change its method, use the Reference's practice with records, first attempts and explained answers (Engineering.Reference:16). You can save an attempt, compare it with the discussion and correct it yourself. Individual feedback requires a qualified helper and agreed time; the text supplies material for self-checking.
FPF.Reference:16.7.4 - Status, evidence, and assurance decisions are preserved
Identification, qualification, selection, trial, and effectiveness are different claims. A candidate account does not become a Method because it is coherent, selected for trial, represented well, supported by a tool, or used in Work. A successful occurrence establishes only the observations and results supported by that occurrence.
A.3.1.CC checks coherence among the claims on which a use relies. A.3.1.FT checks bounded fit or transfer. C.11.MV judges
practical worth against current alternatives. The results can disagree. A Method can be coherent yet poorly fit,
fit one situation yet fail transfer, or produce a useful result whose burden makes another alternative preferable.
FPF.Reference:16.7.5 - What this Method-development family foregrounds and leaves outside
This family foregrounds choosing and recovering the Method-development subject; qualifying candidates and comparing architectures; authoring and comparing descriptions and configuring enactment support; obtaining actual trial evidence and making separate judgments; maintaining variants, introducing Methods into practice and changing cultural continuation; and producing and using connected pattern-language knowledge.
Obtain the specialist Methods, implementation work and authorized decisions needed for a domain task from the relevant discipline or practice. Open a neighbouring DPF when its specialist result is needed and its publication is available.
FPF.Reference:16.7.6 - Why these Method-development questions stay separate
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)