Continue Method Development from Changed Conditions
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
Working result: a bounded Method-architecture continuation: the result needed now, the relevant pattern knowledge, the available, blocked, or unknown continuation, and the smallest return after a decision-relevant change.
Use this when. You are developing a Method or its relations, several questions remain connected, and current facts can change which question should be answered next. A pattern language can help, but its contents page does not tell you whether to qualify a candidate, resolve a whole, compare arrangements, repair a description, or stop.
Relations
Content
Problem Frame
Use this when. You are developing a Method or its relations, several questions remain connected, and current facts can change which question should be answered next. A pattern language can help, but its contents page does not tell you whether to qualify a candidate, resolve a whole, compare arrangements, repair a description, or stop.
Start by asking: Which Method-architecture result do we need now, and what fact could change that need? For example: “We can review the candidate description, but cannot yet claim that its proposed Methods form one whole. Which result should we obtain, and what stays valid when the missing evidence arrives?”
The first useful answer can be spoken: “Review these unchanged claims through A.3.1.QM; keep the whole claim unresolved under B.1.5.CM; publication remains blocked by its separate condition. Reopen the whole claim when its missing relation basis arrives.” During ongoing Work, the deciding System uses A.15.7 to choose the next action and names the intended performer and any feedback condition needed for that continuation.
The practical gain is continuity across Method-development questions. Each new fact returns to the result it can change; the practitioner need not restart qualification, comparison, description, and support work together or reconstruct their boundaries from a reading sequence.
Ordinary non-use. If one current MethodDescription already states the applicable action, conditions, result, and stop, use it. If one existing pattern or result answers the whole current question, use that answer and stop.
A single action does not need a continuation account, alternative set, CGUS, or durable result.
Before Work begins, use the architecture, planning, or work-entry question; A.15.7 governs only an ongoing-Work choice.
This is the situated-use branch of Method development using pattern-language knowledge. It does not recover and reconcile an entire source corpus or construct the complete language.
Problem
A Method engineer receives knowledge in different forms: candidate accounts, source dossiers, qualified contributions, architecture proposals, descriptions, and review results. A convenient pattern sequence can hide the distinction between a result that exists, a claim awaiting support, and a next action that somebody must choose.
When one condition changes, two errors follow. The practitioner may carry a stale composition or authority claim into the next action, or reopen every result because “the situation changed.” Both lose useful work: the first by relying beyond its basis, the second by repeating unaffected judgements.
Forces
Solution
C.39 connects a missing way to its receiving result. The construction here uses that connection across distinct Method-development questions when a changed fact can alter the useful continuation. It retains already supported results and returns only the affected question to its supplier; an adequate description remains a sufficient exit.
Keep the current Method question connected to the result that answers it. Obtain the narrow pattern contribution, expose only the continuations whose conditions matter now, and after a substantive result check which earlier claims or uses changed.
Find the Missing Method-Architecture Result
Name the receiving problem and the result it needs. Distinguish an unavailable result from an available result that is not currently applicable. Use the following returns only when their question is present; they are alternatives, not a prescribed sequence.
Retrieve the selected pattern through E.11.PUA/PUR and read its Solution and boundary. If a current result already answers this question, reuse it under the defining pattern and stop. A title match or search result is not a substitute for that check.
Make the Present Continuation Usable
-
Carry the result boundary forward. In ordinary language name the Method, candidate account, proposed relation, description, or other subject under decision. Retain which claims are established, proposed, contradicted, or unresolved and which source or result supports them.
-
Expose only relevant continuations. For each alternative state the result it could obtain, the condition it needs, the facts known now, and whether it is available, blocked, or unknown. Name the first missing fact or rule. Do not add alternatives merely to make the account branch.
-
Keep material relations readable. State a prerequisite result, local order, alternative, conflict, support condition, check, or return when it changes this use. Two nearby patterns can remain an unordered neighborhood. Use each relation's governor; a connecting arrow, contents order, or shared profile supplies no relation by itself.
-
Return the choice to A.15.7. During ongoing Work, the deciding System uses the available facts and the domain Method's limits to choose the next action. That result names the chooser and, for a selected action, its intended performer, with any stop or feedback condition needed for the continuation; establish capability, access, permission, or authority only when the action needs it.
If Work is blocked by a missing performer, support, or continuation-state relation, use A.15.8's actual-Work configuration branch before returning to choice. An assistant's recommendation is input to that choice.
Before Work, use the architecture, planning, readiness, or fixed-option decision instead.
-
Observe a result before updating its consequences. An expectation remains an expectation until the result is obtained or independently supported. Use the patterns governing result and Work/evidence claims when those claims matter. Choosing an action, changing a plan, performing Work, and learning a fact remain separate.
-
Check the decision-relevant delta. After a substantive result, or before relying on possibly stale information, use §4.3. Reopen the smallest affected question, retain results whose defining conditions match, and stop when the receiving use has its result or blocker.
“No decision-relevant change; continue using this result within its stated window” is sufficient when a continuity statement is needed. If no later use needs that statement, no additional record is required.
Localize a Situation Change
Compare the new fact with the claims and uses currently being relied on. Check applicability or preconditions; alternatives; constraints or interfaces; resources or capability; assignment, access, permission, or authority; evidence/currentness; expected result, stop, or risk; and the decision-relevant situation boundary. Inspect only positions whose possible change could alter the next result or action.
These are different change questions, not a universal event classification. For example, learning that evidence is missing does not prove that the claimed relation is false. If the reach of the change cannot be bounded, name that uncertainty and widen the relevant question; do not claim unaffectedness from the absence of a visible text edit.
Retain Only What Another Use Needs
An ordinary continuation answer states the current difficulty, selected knowledge, available/blocked/unknown action, any missing fact that matters, and the applicable stop or return. Retain an existing result by reference when it already carries the needed claims.
Only when another turn must cite, compare, audit, or rely on the connected answer, keep a Situated Method-Architecture Result as an ordinary C.2.1 episteme. Its content includes the architecture claims and statuses in use, their source/result returns, the current continuations and conditions, the affected-delta answer, and the next return. This is a descriptive result name, not a new root kind or mandatory register.
Its EntityOfConcern is the architecture question or proposed set being considered, or an independently qualified selected structure when that is the subject. Do not use a fictitious CGUS as the concern of an ordinary proposal.
A changed ClaimGraph, EntityOfConcern, or effective ReferenceScheme changes episteme identity under C.2.1; any continuity between results needs a meaningful basis.
The profile/language episteme, a description of one Method, a selected structure, a continuation judgement, a next-action decision, a WorkPlan, performed Work, and evidence retain their separate identities. One result may cite another; that does not merge their subjects or claims.
Open Formal CGUS Only for Its Own Use
The plain alternatives-and-conditions answer often suffices. Use A.22.CGUS when the needed claim concerns a selected structure with potential continuation branching, and that claim must be qualified, persisted, compared, published or more strongly relied on.
A structure requires its constituents, selected obtaining relations, applied constraints, and named use frame; its CGUS membership requires at least two potential continuations across allowed cases. Zero or one currently enabled continuation is compatible with that potential branching.
For a Method-architecture continuation use, the local frame name Situated-Method-Architecture-Continuation denotes this question: which continuation can obtain the next bounded Method-architecture result or stop? Its admissible actions are to select a continuation, retain alternatives, request the first missing fact, or stop. The stop is the first decision-usable result or a missing condition that prevents it. Naming this frame does not establish the structure or choose the action.
Use A.22.CGUS's complete basis for each formal judgement, retaining condition evaluation separately from an obtaining relation.
The formal continuation outcomes are enabled, disabled, unknown, or error. A completed negative condition evaluation has the outcome notSatisfied; derive its continuation effect from the declared required polarity.
An execution or evaluation failure remains error; return the affected test before relying on its result. Missing evidence can leave the condition evaluation unknown. Keep structure identity, membership, case judgement, description adequacy, and later reliance separately checkable.
Archetypal Grounding
Continue a Release-Method Proposal Across Two Turns
This constructed case concerns ongoing Method-architecture work on proposal P. Whole Method W and participant Methods M1 and M2 have independent identity results, and the participant qualifications remain current. P proposes a construction of W using both participants, but the claimed methodPartOf(M2,W) is unresolved: its cited procedure has not been checked for a required contribution or an admitted alternative in W's construction. A description review can inspect the independent participant claims now. Publication is blocked because no publication decision has been obtained.
The Method engineer needs the description-review result now while keeping the whole claim visible for the next meeting. The continuation answer is:
Using A.15.7, the engineer selects description review as the next action and commissions it. The review lead compares their participant-identity claims with the existing identity results and finds support for W, M1 and M2 as identified Methods. The material examined still supplies no basis for the proposed inclusion of M2 in W. The lead gives the engineer those findings now. The first is usable in the meeting, and the second states which construction rule still needs examination. Because the next meeting will rely on these distinctions, the engineer retains one situated result about P's architecture question, citing the existing A.3.1.QM results rather than copying them. No formal CGUS is needed for this use.
Before the next choice, the relevant procedure is inspected. Its construction rule places M2 outside W: M2 supplies optional advice but is neither required nor an admitted construction alternative. That changes the proposed composition claim, not the independently established identity of W, M1, or M2.
The engineer returns the affected composition question to B.1.5.CM. The proposed relation set is not supported as W's obtaining composition; retain the useful support relation and return P for correction or another proposed arrangement. The engineer can use the completed comparison with the existing A.3.1.QM identity results at the meeting. Publication still requires its own decision.
The new situated result changes the composition-claim and return content. It does not backdate a new Method, change independently established completed review Work, or announce a new structure from one new fact. If another proposed arrangement changes W's reusable semantics, that later proposal needs its identity question.
The newly inspected rule decides the composition question and changes the uses that depended on it. The completed identity comparison remains available for its original use.
A Sufficient Description
The current approved description already says: inspect the named evidence field; if the signed supplier result is absent, retain the release hold and return to the supplier. The field is absent and no competing action is admissible. Use that description and its stop. There is no extra continuation result, choice dossier, formal structure, or invented second alternative.
An Assistant Recommends from Stale Facts
An assistant retrieves a relevant review pattern and recommends sending the candidate to the reviewer. Its recommendation uses yesterday's access statement. The current question is whether that reviewer can inspect the restricted evidence today; the assistant has neither that access nor publication authority.
Keep the recommendation as a recommendation. Ask the access holder to refresh the decision-bearing fact. If access is unknown, the evidence-dependent review continuation is unknown; if access is denied, it is blocked. A permitted review of unrelated public claims may remain available if the same review Method allows that narrower result.
The deciding engineer uses A.15.7 for the next action, the access holder supplies the access answer, and the permitted reviewer performs any selected review. Confidence in retrieval supplies none of those relations. If no safe narrower review is available, stop at the missing access result. No performed review or publication follows merely from the recommendation.
Bias-Annotation
Method engineers may favor explicit architectures and overlook a sufficient description. Start with the non-use test. Pattern-language enthusiasts may attribute capability to the language itself; retain the acting and deciding Systems only where those claims matter. Automation can amplify old source assumptions, so inspect currentness before a confident recommendation enters action.
The cases emphasize documentary Method Engineering and review. They establish no empirical advantage across domains, human readers, or AI systems. A high-consequence decision may need stronger evidence than these constructed continuations supply.
Conformance Checklist
- The current question is about a Method, its relations, or its description; a sufficient result is used without a profile wrapper.
- The next needed result and its supplying pattern are explicit; established, proposed, contradicted, and unresolved claims retain their statuses.
- Every exposed continuation has a relevant condition and current basis, or a missing fact.
- During ongoing Work, A.15.7 supplies the action choice; the chooser, intended performer, and any material authority/access/capability relation remain distinguishable.
- A substantive change reopens its affected Method-development result and dependent uses; unaffectedness is checked against the retained basis.
- Formal CGUS, persistent results, and Work claims are opened only for a use that needs them and satisfy their rules.
- The answer states the first useful result or blocker and the next stop or return, without treating reader order as Work order.
Common Anti-Patterns and How to Avoid Them
Consequences
The practitioner can continue Method development without rereading the whole repertoire or treating every local change as a new Method. Missing basis remains visible at the result that needs it, so independent useful work can continue without claiming that blocked work has become possible.
The cost is maintaining a few explicit result-to-use connections when they matter across turns. A poor or stale pattern language cannot be repaired by this continuation method; the missing content must return to source recovery, qualification, architecture, or authoring.
Architectural Rationale
General pattern use and live Work steering already exist. The Method-development contribution is the connection between a current professional question, the distinct result that can answer it, and the smallest affected return when that result's basis changes. The table in §4.1 and the two-turn case make that connection usable without copying the full qualification, composition, representation, or steering Methods.
A MethodDescription is preferable when it already supplies the action and stop. A fixed route is useful when its dependencies remain sufficient. For a changing plurality of questions, reconstructing the returns from separate patterns can hide an unresolved whole or repeat unaffected qualification. This method keeps those returns visible at a cost proportionate to the present decision.
A pattern language supplies problem-oriented knowledge for the deciding practitioner. Local action order follows the applicable prerequisites and causal assumptions; a contents order does not establish them.
SoTA-Echoing
Use these source contributions for the stated questions and limits. Reopen the affected source or action when a current alternative supplies the same result with less reconstruction, a source change alters a load-bearing distinction, or use evidence reveals a missed dependency or unnecessary burden. Claims of human or AI superiority require comparative evidence supporting those claims.
Relations
- C.39.RP and A.3.1.DR supply documentary knowledge; A.3.1.MR and, when needed, an applicable research Method supply occurrence-evidence recovery results.
- A.3.1.QM, C.32.MWA.PP, and B.1.5.CM keep individual qualification, alternative architecture, and whole resolution distinct. A.3.2.DE, C.37.MP, A.15.8.MS supply description, cross-use representation, and support results; A.3.1.CC and A.3.1.MV carry the applicable correction or variant return.
- E.11.PUA/PUR govern the pattern-use and recommendation questions, including reuse of a matching earlier result. A.15.7 governs live next-action choice; A.15.2/A.15.5 and C.11 retain their other entry conditions.
- A.22.CGUS governs structure and continuation judgements. C.2.1 governs a retained result episteme. A.3.1/A.3.2/B.1.5 and A.15 keep Method, description, composition, plan, Work, and result claims distinct.
- E.11.PFP and E.4.PFIP supply publication-form and publication-preservation work when that question becomes current; a situated continuation grants neither publication nor release.
C.39.MC:End
Last Updated: 2026-11-12 — this section last modified in upstream FPF commit 1e57ccda (github.com/ailev/FPF)