Describe a Method for Its Intended Use
About this pattern
This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.
How to use this pattern
Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.
Type: Method pattern Status: Stable
Use this pattern when people need usable claims about an identified Method or a candidate account of a proposed way of working. The receiving use may concern planning, enactment, comparison, review, revision, publication or teaching; retain the claims' status. Start from one named use: who needs to do or decide what, which Method claims that use consumes, and what can remain outside the edition.
Relations
Content
Use This When
Use this pattern when people need usable claims about an identified Method or a candidate account of a proposed way of working. The receiving use may concern planning, enactment, comparison, review, revision, publication or teaching; retain the claims' status. Start from one named use: who needs to do or decide what, which Method claims that use consumes, and what can remain outside the edition.
The first useful result is a short use-coverage account. It names the Method or candidate account, the receiving use, the claims needed now, the claims deliberately omitted, and the stop. That account prevents a documentation project from expanding before its practical question is clear.
Do not use this pattern merely to publish, diagram, approve, schedule, or record Work. A U.MethodDescription is the claim-bearing episteme whose EntityOfConcern is one Method already admitted under A.3.1; its representations, carriers, and dated enactments remain separate objects. Planning and approval have their own claim conditions; the same episteme may also meet A.15.2 as a U.WorkPlan. If the proposed whole is still a candidate account, improve that account without classifying it as a U.MethodDescription for the whole.
Working Distinctions
Problem Frame
A working group often has too much material rather than too little: procedures, diagrams, code, examples, approval notes, logs, training slides, and tacit explanations. Different users need different portions. A planner needs applicability, preconditions, parameters, bounds, and stops; a performer needs the actionable claims for the current situation; a reviewer may need provenance, changed claims, and declared evidence limits.
Without a use boundary, authors either copy everything into one manual or reduce the Method to one convenient representation. Both moves hide whether the episteme describes an admitted Method and whether its claims are sufficient for the receiving use.
Problem
A document can look complete while saying little about the way of doing. Conversely, a small claim set can be a valid MethodDescription yet be unsafe for a consequential enactment use. Teams also copy calendars, assignees, tool states, observed results, and approval decisions into the description as if adjacency turned them into Method semantics.
The result is difficult to reuse and difficult to challenge. Readers cannot tell which claims belong to the Method, which belong to one Work occurrence, which are evidence or policy, and which omissions require a return.
Forces
Solution
A.3.2 distinguishes description membership from adequacy for use. C.39:4.3–4.5 supplies construction of a missing action or join. Here the author develops the explanation for the declared reader: recover the operations, reasons, conditions and changed case that the reader must be able to follow, retaining an unresolved candidate as such.
Author claims for named uses while preserving the described Method's identity or the account's candidate status. Return gaps instead of filling them with neighboring objects.
Pattern-Use Unfolding
- Name the receiving use. State the reader or consuming system, the action or decision, the situation and qualification window, and the stop. Define completeness by the claims the receiving use needs, including their connections.
- Establish the subject branch. Name the admitted
U.Methodand the effective reference scheme for the description, including the rules that resolve its Method designation. If admission is absent, keep the subject as a candidate account and author only improved candidate content. - Select the needed Method claims. For the named use, consider the transformation or enactment concern, generic participant meanings, applicability, preconditions, intended effects or preserved conditions, bounds, parameters, variation, internal composition, evaluation conditions, and stops. Include only positions that change the use. For enactment or learning, recover the operations the performer must carry out and where their inputs come from.
- Separate neighboring claims. Keep planned assignments and dates in a
U.WorkPlan; actual performers, temporal extent, participation, and results with datedU.Work; operation declarations withA.6.1; evidence reliance withA.10; capability withA.2.2; approval, permission, and authority with the patterns that define those claims. Cite them when the use depends on them without absorbing them into Method semantics. - Write the explanation or instruction. For enactment or learning, connect each needed action to its inputs, the operation performed, the result and the condition for continuing or stopping. Explain why a connection or ordering matters when the reader needs that reason to apply or adapt it. For a Method that depends on professional judgment, explain which observations bear on the decision, how they change the proposed action, and which unresolved conflict needs another contribution or a stop. Naming a mindset without showing that effect leaves the explanation incomplete. Unfold a constituent operation until the intended performer can carry it out, or identify the missing know-how or contribution; do not invent an operation to fill a heading. Retain alternatives and dependencies without imposing one order on independent actions. In the admitted-Method branch, identify the episteme by its claim content, Method as
EntityOfConcern, and effective scheme. In the candidate branch, retain the account's proposed content and unresolved Method-identification conditions. State which claims were added, retained, narrowed, or removed when another edition is being revised. - Record use coverage and omissions. For each named use, list the claims exposed, claims deliberately omitted, unresolved claims, and the return condition. An omission is acceptable when the receiver does not rely on it; otherwise it is a gap.
- Choose expression and publication separately. Select text, code, diagrams, a mathematical lens, publication form, and carrier only after the claims are stable enough for the use. For one representation-use action, use C.37 or its direct governing pattern. When different named Method-related actions require complementary governed representations of the current MethodDescription or candidate account, C.37.MP returns a complete Method representation profile: one complete C.37 claim group per action, together with cross-use correspondences, conflicting omissions, edition relations, decisions to keep representations separate, and conditions that require reconsidering several selections. Use the FPF pattern governing any other represented entity.
- Try the receiving use from the description. Recover the claims, conditions and omissions needed by the receiving use. For enactment or learning, work through a small case: recover the first action and its inputs, follow its result to the next needed action or stop, and expose any instruction supplied only from the author's memory. Return a description or candidate-account correction, or identify the missing input, know-how or other result needed by the use. This checks the description at that use; it does not establish the Method's effectiveness or a learner's acquired capability.
Record the Result
These positions can be stated in prose or in an existing description account; they do not require a separate row or form.
What Changes in Practice
Authors stop treating “the method document” as one undifferentiated object. They can issue a small edition for one use, explain why it is enough, and name the gap when it is not. Readers can distinguish a claim about a reusable way of doing from a plan, an observed occurrence, a tool presentation, or an approval fact.
Archetypal Grounding
Stop at the Candidate Whole
C-EC-Release-v2 is a prospective account of a possible release-coordination whole. It proposes waiting for signed supplier evidence before software integration, or integrating from a versioned provisional edition and reconciling it with signed evidence before safety closure. It also specifies recovery after failed closure, authority boundaries, confidentiality, reversibility and stops. The Method identity of this proposed whole remains unresolved; B.1.5.CM:5 gives the full case.
Improve the claims required for selection or trial planning and retain the unresolved Method-identification condition. The result remains a candidate account.
A Bounded Description of an Admitted Constituent Method
For the admitted constituent M-HW-Verify, suppose the named use is preparing safety-verification Work for one EC-417 release. A description edition can state the applicable safety-relevant change family, the distinction between provisional and signed evidence, the comparison and affected-verification actions, the signed-before-closure bound, confidentiality conditions, and the mismatch or stale-edition stop. The use-coverage account says that it exposes those Method claims but omits dates, assignees, actual evidence versions, actual verification results, and release authority decisions.
The planner may cite that edition when constructing a WorkPlan. Supply separate claims about the Work schedule, the assignment of SafetyReviewer-17, the required capability, closure authorization, and whether verification occurred whenever the plan or later Work relies on them.
Turn a reconciliation reminder into an instruction
In this constructed case, a stock-reconciliation Method has already been identified. Its working rule is available, but the draft for a new storekeeper says only: "Reconcile stock and investigate discrepancies." The reader can add and subtract counts; they still need to know which counts to compare and what the difference means.
The author recovers the rule's inputs and dependencies. For one item, unit and interval, an opening stock count plus receipts minus issues gives the expected closing count, provided the movement account includes every change once. A physical count at the closing boundary supplies a different input. The author writes this instruction:
- Select the item, counting unit and interval. Obtain the opening count, receipts and issues for that same scope, and the physical count at its closing boundary. Resolve a missing movement class, unit conversion or mismatched boundary before treating the balance as complete.
- Calculate expected closing stock as opening stock plus receipts minus issues. The additions and subtractions represent movements into and out of the selected stock.
- Subtract expected stock from the physical count. Return the difference with the counts and scope used. A negative difference means fewer units were counted than the movement account predicts; it does not identify the cause.
- If the counts disagree, return the discrepancy for checking the movements and counts. Do not change a source count merely to force agreement.
With opening stock 48, receipts 12, issues 17 and a closing physical count of 41, the expected count is 43 and the discrepancy is -2. The description now supplies an operation, its operands, their origins, the reason for their combination and a useful return. Its authoring result is the instruction, not evidence that a storekeeper performed it.
The receiving-use check asks the reader to recover that calculation and return from the description. If the opening figure is in boxes while movements are in individual units and the conversion is unknown, a numerical balance remains unavailable. A comparison-only description could legitimately omit this enactment detail; this edition promises the storekeeper a way to perform the reconciliation.
Explain the Basis of a Professional Judgment
A stakeholder map can keep the same boxes and labels while the way of constructing and using it changes. In this constructed case, an admitted contact-planning Method includes people who hold the approval or supply roles needed to arrange a rollout. A proposed child account instead asks whether a new shift-handover routine covers the work of the people who produce and use the handover information. Its author cannot explain that change merely by adding "be inclusive" to the old instruction.
The receiving use is a facilitator's preparation of a handover review. Available inputs are the proposed routine, the two-shift role roster, the information each role's holders supply or need, and the known limits of those accounts. The author writes the proposed instruction:
- Start from the handover information that must reach the next shift and identify the roles whose holders produce or use it in their work. Include a role because of that working dependency, even when its holder has little influence over rollout approval. Use supplied facts; mark an uncertain dependency for clarification.
- For each included role, obtain an account of the information its holders need, the action that information enables and a relevant missing-information case. Distinguish what a participant or work record supplies from the facilitator's assumption. A manager's approval does not supply another role's working account by itself.
- Relate those needs to the proposed routine. Show which handover action supplies each needed result and which dependency remains uncovered or unknown. Influence can help arrange contact; it does not remove a required receiving role from this check.
- Return the map with the supported coverage and the missing account or handover contribution. Stop a claim of complete coverage when a material dependency remains unresolved. The result can guide a correction or a bounded trial; it does not itself authorize rollout or show that the routine works.
For a small worked case, suppose a day lead approves the trial, an IT maintainer supplies the display, and a night operator uses unresolved-item flags to resume work. The approval-contact map may correctly contain the first two roles. The proposed method also includes the night operator because the operator consumes a result needed for the handover. If the routine supplies a flag but no next action, the map exposes that missing contribution. If a relief operator's information need is unknown, add that unresolved dependency rather than treating a full roster of names as complete coverage.
The explanation now makes the changed judgment recoverable: inclusion follows a working dependency, and completion requires an account of its contribution. The canvas may remain unchanged, but the operation, required evidence and stop differ. This is proposed reusable content, so retain candidate status and use A.3.1.MV:5.2 for its derivation and evidence boundaries. The worked case checks whether the explanation supplies the intended distinctions; it is not a field validation of the proposed method.
Bias-Annotation
Conformance Checklist
- Each
U.MethodDescriptionresult names oneA.3.1-admitted Method as itsEntityOfConcern. - A candidate whole remains a candidate account when Method admission is absent.
- Every named use has a receiver, action or decision, situation, qualification window, and stop.
- Included claims say something substantive about the Method as a way of doing. An enactment or learning description lets the prepared reader recover the needed operations and their input/result connections, or exposes the missing contribution.
- Use coverage distinguishes exposed claims, deliberate omissions, unresolved gaps, and return conditions.
- WorkPlan, dated Work, actual participants and results, operation declarations, evidence, capability, permission, authority, representation, publication, and carrier claims remain separate.
- Representation choice does not decide MethodDescription membership.
- The result says only whether this edition covers the named claim need; it does not infer Method fit, effectiveness, assurance, or actual use.
Common Anti-Patterns and How to Avoid Them
Consequences
Method descriptions become more reusable and easier to compare because their subject and receiving uses are explicit. Candidate accounts remain useful without losing their truth status, and missing claims return to the right owner.
The cost is plurality: one Method may have several editions, use-coverage accounts, and representations. Projects must also maintain links to neighboring plans, evidence, policy, and publication results instead of copying them into one manual.
Rationale
Description adequacy is use-relative, while MethodDescription membership is not. Separating those questions lets a small episteme describe an admitted Method, with adequacy assessed for each receiving use. It also lets a rich candidate account remain prospectively useful without turning description quality into Method identity.
The claim-first order prevents representation and publication choices from selecting ontology.
SoTA-Echoing
Relations
A.3.1supplies Method admission;A.3.2definesU.MethodDescriptionmembership and its boundary from plans, Work, representations, and publication.- B.1.5.CM can supply an admitted whole or a prospective candidate account. A.3.2.DE preserves the branch it receives.
- RMP.10 can supply claim content and evidence limits for a candidate account; it does not admit the Method or create the description.
- C.37.MP consumes A.3.2.DE's current MethodDescription or candidate-account claims only when several unlike named Method-related actions require a Method-specific profile. It returns one complete C.37 claim group per action and a separate result showing how the selections relate: source correspondences, conflicting omissions, edition relations, decisions to keep representations separate, and conditions that require reconsidering several selections. For one action, use C.37 or the pattern that governs it; for another represented entity, use that entity’s governing FPF pattern.
A.15.2,A.15.1,A.10,A.2.2, andE.24.PUBdefine or constrain neighboring plan, Work, evidence, capability and publication claims.A.6.3.RTandA.6.3.RT.OEgovern representation correspondence;C.29governs a mathematical lens.
A.3.2.DE:End
Last Updated: 2026-10-12 — this section last modified in upstream FPF commit 6c31cd80 (github.com/ailev/FPF)