ME.20:4 - Solution
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 actually changed.
ME.20:4.1 - 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.
| Current difficulty | Direct contribution to use | First result retained here |
|---|---|---|
| The relevant alternatives or source editions are unknown. | ME.2; ME.4 for documentary recovery, A.3.1.MR and conditional ME.18 for occurrence-evidence recovery. | A bounded repertoire, dossier, candidate account, or honest gap, with its source and status. |
| One Method or individually scoped candidate needs qualification. | ME.5 and the applicable A.3.1 identity question. | The individual qualification or unresolved identity condition; not a verdict on a whole. |
| Several possible arrangements differ in relations, combined demand, or burden. | ME.6. | The compared arrangements and architecture decision, preserving proposed versus obtaining relations. |
| A proposed Method whole lacks supported identity or composition. | ME.7 with A.3.1 and B.1.5. | An obtaining composition result, prospective account, or lower return. |
| The way is understood but its description cannot support the named use. | ME.8; ME.9 only when several unlike Method uses need a cross-use representation profile. | The description/account or representation result with its omitted claims and use boundary. |
| A description, support arrangement, or earlier result is contradicted. | ME.12 for the correction question; ME.10 for a support configuration; ME.15 when reusable variation changes. | The corrected, narrowed, or still-unresolved result and its affected consumers. |
| The content question is settled and the question is publication or release. | The applicable E.11.PFP, E.4.PFIP, publication, and release Methods. | Their own result or blocker; content review does not supply publication authority. |
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.
ME.20:4.2 - 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 live 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 direct governor; a connecting arrow, contents order, or shared profile supplies no relation by itself.
- Return the live 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, intended performer, and stop or feedback; 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 actual 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 direct result and Work/evidence patterns 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 still match, and stop when the receiving use has its result or honest blocker.
The method does not require a log of every thought. “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.
ME.20:4.3 - 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.
| What changed | What to reopen | What is not changed merely by this observation |
|---|---|---|
| A fact, evidence item, test outcome, or qualification window. | The affected result’s reliance/currentness and the current continuation judgement; obtain the first missing basis or stop. | The Method, completed Work, and an independently unchanged potential structure. |
| A claim supporting a proposed whole or a participant relation. | The exact ME.7 identity/composition question; ME.6 if the architecture alternatives or chosen arrangement are affected. Preserve individual ME.5 results whose basis still holds. | All participant identities or all source recovery merely because one relation is unresolved. |
| Reusable action, applicability, required contribution, permitted variation, or reidentification rule of a Method. | A.3.1/B.1.5 and the affected Method Engineering result, including ME.15 when variant identity is current. | Earlier performed Work or an automatic new description/publication edition. |
| A formal CGUS constituent, selected obtaining relation occurrence, applied constraint, or named use frame. | A.22 structure identity. A changed locus binding or potential-continuation row separately reopens CGUS membership. | A case judgement cannot silently stand in for the changed structure or membership test. |
| The instructions or intended-work content, with the represented Method still unchanged. | ME.8/ME.12 for description correction; A.15.2 for a changed WorkPlan. | Method identity or evidence that the planned action was performed. |
| The audience, relied-on claim, or publication/use boundary. | The affected representation, source-use, or publication question and its direct consumers. | Unaffected content or independently qualified uses. |
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.
ME.20:4.4 - Retain Only What Another Use Needs
An ordinary continuation answer needs the current difficulty, selected knowledge, available/blocked/unknown action, first missing fact, and 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 exact architecture question or proposed set being considered, or an independently qualified selected structure when that is actually 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 its own 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.
ME.20:4.5 - Open Formal CGUS Only for Its Own Use
The plain alternatives-and-conditions answer often suffices. Use A.22.CGUS when an independently selected structure 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 PLUS-ME-Situated-Architecture-Continuation denotes this question: which continuation can obtain the next bounded Method-architecture result or honest 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.