A.15.8:4 - Solution · fpf.tools

A.15.8:4 - Solution

Choose one branch, keep every System and value separately identified, recover only relations that can change the named result or decision, and run the weakest representative probe that can expose an unsupported dependency. Return the branch-specific result to direct owners. Do not first decide whether cognition, mind, or agency is “extended”.

A.15.8:4.1 - Keep the governed object and non-kinds explicit

This pattern introduces no root U.ExtendedPerformer, U.WorkSystem, U.WorkState, U.Attention, U.Memory, or joint-cognition kind. It does not admit an arrangement as a System, performer, Agent, Structure, ArchitectureRelation, or capability holder merely because its constituents are coupled or jointly useful.

In the actual branch, the governed world-side focus is one exact admitted U.Work occurrence. In the prospective branch, it is one exact present U.WorkPlan; proposed performance stays declaration-local content of that episteme. Supporting Systems and values may be inside or outside a selected containing-System boundary. Their contribution, dependency, access, update, control, or other relations must be directly declared and supported when the result relies on them.

An arrangement remains ordinary prose unless another use needs an exact U.Structure admitted under A.22. An architecture claim enters only through C.30. A configuration account can designate several independently governed Systems and values without making them one whole or using a plural EntityOfConcern.

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.

A.15.8:4.3 - Return the first result in plain language

Use this compact form and omit rows the receiving decision does not need:

Focus: exact actual U.Work occurrence … / exact present U.WorkPlan … and its declaration-local intended-performance designator …

Required result and receiving decision: …

Actual performers for the Work / intended performers in the plan, plus supports: …

State needed to continue and where it is recovered: …

Probe and observation: …

Direct relation result or exact blocker, and next repair or stop: …

For a small reversible use, this ordinary prose is enough. The result describes support for one configuration and window; it does not certify every configuration, create a whole, or make the repair decision.

A.15.8:4.4 - Persist only the account another use needs

When another use must retain, compare, audit, or rely on the result, identify one or more C.2.1 account epistemes explicitly.

An actual-branch account selects the exact U.Work occurrence as its one truthful EntityOfConcern.
A prospective-branch account selects the exact present U.WorkPlan as its one truthful EntityOfConcern. Its ClaimGraph may designate the declaration-local intended-performance content but does not turn that designator into an entity.
The ClaimGraph may also designate independently governed actual or intended performers, supports, state bearers, exact relation claims, and the direct governor’s result. It may record the ordinary A.6.RCD blocker factually unsupported, missing-information, or missing-governor only under that pattern’s three-way split; these phrases are not new kinds or relation values. Probe observations, uncertainty, and the repair or stop remain separate claim content.
The effective U.ReferenceScheme always supplies the designation and interpretation rules needed by those claims and adds only the measurement, comparison, or evaluation rules actually used. Any actual measurement, comparison, or evaluation occurrence remains under its direct pattern.
If one focus cannot truthfully carry the combined claims, keep claims local or use several epistemes. Do not invent a plural focus.

The account is not the world-side configuration, performed Work, WorkPlan, carrier, evidence, or merely possible future performance.

A.15.8:4.5 - Separate recognition from assurance

Recognition: one actual or credible failure under interruption, transfer, support loss, or stale intermediate state is enough to open A.15.8. One ordinary sentence can name the first weak relation and probe.
Assurance: safety-, release-, compliance-, irreversible-, or high-impact use adds the applicable direct test, evidence, assurance, authority, and stop rules. A successful probe does not establish universal readiness or waive those rules.