A.15.8:4.2 - Follow the seven-step configuration-and-recovery sequence

Choose the lawful branch and name its focus, required result, and receiving decision. For an actual case identify one exact dated U.Work occurrence under A.15.1. For a prospective case identify one exact present U.WorkPlan under A.15.2 and the declaration-local intended-performance content used by the configuration claim. Use A.15.5 only when entry readiness is current. Do not call intended performance a future Work entity.
Keep performers, intended performers, supports, and values separate. In the actual branch identify the admitted Systems that performed the Work, with assignments and attribution only where their direct predicates pass. In the prospective branch name intended performers only inside the exact WorkPlan’s claim content. In either branch identify supporting and external interacting Systems, physical resources, representations, records, models, tools, services, and environmental conditions without forcing them into one whole.
Recover concrete contributions and dependencies. Translate words such as attention, memory, computation, and checking into exact sensing, selection, monitoring, operation, record, state, evaluation, communication, access, update, control, or other direct relations. For actual Work, retain only relations whose obtaining, loss, or change can alter continuation, result, or recovery of that occurrence. For a WorkPlan, retain only relations whose obtaining, loss, or change can alter the current plan, proposed configuration, or intended-performance content. For every attempted relation claim, name the exact participants and receiving use. When a current predicate definition, applicability condition, occurrence rule, or other governor can state or test it, apply that governor and preserve its result: use factually unsupported only when the available case basis is sufficient and the positive test fails, missing-information when a needed fact is unavailable, and an inapplicable or negative result only under the governor’s own rule. Return missing-governor only when no current rule can state or test the attempted claim for those participants and that use. Name capability and authority only when their direct claims are current.
Expose the minimum continuation state. For each value needed after interruption, handoff, support loss, or delay, state what it concerns, where it resides, who or what may update and use it, how currentness or consistency is determined, and which return condition makes it usable. Keep world state, claims, carriers, and cues distinct.
Select the weakest decision-changing condition. Choose one representative interruption, handoff, degraded support, changed performer, changed tool or environment, or delayed-continuation condition. Apply it to the named Work occurrence in the actual branch. In the prospective branch, formulate it as a condition of the current WorkPlan, proposed configuration, or intended-performance content. If executing the probe creates actual test Work or a later performance, admit that occurrence separately under A.15.1; otherwise keep the condition in the plan or probe claim. Do not demand a ritual battery.
Run the direct domain probe and observe recovery. Select an applicable human-factors, biological, software, robotics, operations, rehearsal, safety, or other domain U.Method only to define or constrain the probe, mechanism, thresholds, safety rules, and evidence rules. When the probe is executed, recover each actual performer through A.13 and admit its dated probe Work separately under A.15.1; state that the Work enacts the Method. Add A.2.1 and F.6 only when this probe account expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment. A missing or failed attribution leaves the probe Work intact. When the probe remains prospective, keep it as a condition in the WorkPlan or probe claim. Observe result recovery, time or burden where material, wrong continuation, missing or stale state, unsupported dependency, protected-condition loss, and fallback or stop. This pattern supplies no universal cue, timeout, checkpoint algorithm, intervention, or safety threshold.
Return one branch-specific account to direct owners. State which exact Work occurrence or present WorkPlan is the focus, what configuration is supported for which occurrence or intended-performance content and window, what failed or remains unknown, and the next relation or configuration repair or stop. Return System identity to A.1 or B.2, Structure to A.22, architecture to C.30, capability to A.2.2, actual Work and resumption identity to A.15.1, plan content and plan change to A.15.2, representations to their direct owners, evidence to A.10, and a receiving choice to C.11 or A.15.7.