Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:00:10 UTC

A.15.8 - Work-Performance Configuration and Recovery Testing

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Plain name. Test whether the performer, support, and continuation-state configuration for Work can continue or recover when something important changes.

Reader. A practitioner preparing or performing human, automated, biological, organizational, computational, or mixed Work whose result may depend on several Systems, tools, records, resources, and environmental conditions.

A.15.8:1 - Problem frame

Use this when. Use this pattern when a result succeeds in one configuration but may fail after interruption, handoff, delay, support loss, replacement, or changed conditions, and the decision needs to know which relation to repair or test. Choose the branch for the focus being examined:

  • Actual-Work branch: start from one dated U.Work occurrence already admitted under A.15.1. Name actual performers, assignments, and attribution only where the rules governing those claims pass.
  • Present-WorkPlan branch: start from one present U.WorkPlan under A.15.2. Intended performers and intended performance remain declaration-local plan content; they are not an existing future U.Work, obtaining assignment, or actual attribution.

Start with a sentence appropriate to that branch:

Actual Work: For this admitted Work occurrence, these Systems performed it under the attribution rules; these other Systems or values supported it; this is where the state needed to continue lives; this is what the available evidence establishes about continuation or recovery; continue within the supported conditions, repair the affected relation, or stop as that result warrants.

Present WorkPlan: For this present WorkPlan, these Systems are named as intended performers in its declaration-local content; these other Systems or values support the proposed configuration; this is where the state needed for intended performance would be recovered; this is what the current plan and probe evidence support or leave unresolved; obtain a needed basis, revise the plan, continue within the supported conditions, or stop as that result warrants.

First useful result. Return a short branch-specific account of the Work or WorkPlan focus, required result and receiving decision, performers, supports, continuation state and probe observations needed by that decision, the supported, failed or unresolved relation claims, and the warranted next action or stop.

What changes in practice. Instead of saying that a person, tool, team, organism, service, or machine must “pay attention”, “remember”, or become one “extended performer”, the practitioner names the relation whose loss changes continuation or recovery and challenges that relation under one representative condition. The next move follows the result: continue within the supported conditions, obtain a needed basis, make a bounded configuration or plan repair, or stop.

Cheap non-use. Do not use this pattern merely because Work uses a tool, a person takes notes, software has state, a bacterium responds to its environment, or several Systems participate.

Stop when current results from domain Work already identify the configuration of the named Work or WorkPlan, continuation state, representative recovery evidence, and limits needed by the decision, with the applicable Method and evidence boundary explicit.

If A.15.5 has established an ordinary full kit and no interruption, handoff, support loss, or configuration ambiguity can change entry, stop there. If the configuration is adequate and only the next action during current Work is open, use A.15.7. For ordinary preparation and return after an interruption, use A.15.10 when the purpose, method or unfinished contribution must be recovered; that use does not require a configuration test.

Not this pattern when. Use A.1 to recognize a proposed System, and B.2 when changed facts require comparison with an established prior whole; A.2.2 for capability of one admitted holder; A.15.1 for Work occurrence identity or resumption segmentation; A.15.2 for the WorkPlan; A.15.5 for ordinary entry readiness; A.15.7 for next-action selection; A.22 for one selected Structure; C.30 for architecture; the pattern governing a representation; A.2.4 for the first evidence-use or status-use classification and A.10 when the bounded source-to-use account must remain replayable; or the applicable domain Method when only its test, threshold, algorithm, safety rule, or intervention is missing.

A.15.8:2 - Problem

Performance often depends on relations among actual or intended performers, supporting Systems, physical resources, representations, records, services, models, environmental conditions, and state needed for continuation. A perfect run can hide that one dependency is stale, inaccessible, inconsistent, unavailable to a successor, or supported only by the current session.

Umbrella words conceal different objects. “Attention” may mean sensing, selection, monitoring, search, checking, or a holder capability. “Memory” may mean internal state, a record, model state, retrieval, cultural continuation, or a relied-on claim. “Work state” may mix world state, epistemes, carriers, and cues. Treating these words as fields on one composite performer hides the relation that must change and can incorrectly assign System identity, Work, capability, authority, or evidence.

Recover the Work-dependent configuration and expose the minimum state needed to continue. Under a representative condition, test a dependency whose result can change the decision. If the available evidence identifies the weakest such dependency, test that one. Return the result to the pattern that defines or tests the affected claim.

A.15.8:3 - Forces

ForceTension
Useful whole versus justified wholeA coupled arrangement can be a useful unit of analysis without being one admitted U.System, performer, Agent, or capability holder.
Actual versus prospectiveActual Work permits obtaining performer and support claims; a present WorkPlan permits only current claims about plan content and a proposed configuration.
Compact result versus separate ownershipA reader needs one short result, while System identity, Work, capability, representation, evidence, architecture, and choice remain independently governed.
Perfect-run success versus recoverabilitySuccess in one live configuration does not establish recovery after interruption, handoff, staleness, or degraded support.
Transferable skeleton versus domain mechanismMany domains share the configuration-and-probe move, but their checkpoints, cues, thresholds, safety conditions, and recovery mechanisms differ.
Recognition versus assuranceOne credible failure can open the pattern; consequential use may require much stronger evidence, authority, and stop rules.
State availability versus state correctnessA carrier may be present while its value is stale, inconsistent, uninterpretable, inaccessible, or unsafe to use.

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 least burdensome representative probe capable of exposing a dependency that can change the decision. Return the branch-specific result to the patterns governing the affected claims. Do not first decide whether cognition, mind, or agency is “extended”.

A.15.8:4.1 - Keep the focus and participating objects explicit

In the actual branch, the governed world-side focus is one admitted U.Work occurrence. In the prospective branch, it is one 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 declared and supported when the result relies on them.

An arrangement remains ordinary prose unless another use needs a 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

  1. Choose the branch and name its focus, required result, and receiving decision. For an actual case identify one dated U.Work occurrence under A.15.1. For a prospective case identify one 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.

  2. 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 predicates pass. In the prospective branch name intended performers only inside the 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.

  3. Recover contributions and dependencies. Translate words such as attention, memory, computation, and checking into sensing, selection, monitoring, operation, record, state, evaluation, communication, access, update, control, or other 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 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 claims are current.

  4. Expose the minimum continuation state. For each value needed after interruption, handoff, support loss, or delay, state what it concerns. Recover where it resides, who or what may update and use it, how currentness or consistency is determined, and what makes it usable on return, insofar as those details affect the continuation. Keep world state, claims, carriers, and cues distinct.

  5. Select a representative 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 the receiving claim identifies a distinct test or later-performance Work occurrence, admit it through A.13 and A.15.1; an ordinary observation can remain within the current Work grain. A proposed condition stays in the plan or probe claim. Do not demand a ritual battery.

  6. Run the 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 account claims a distinct dated probe Work, recover each actual performer through A.13, admit that Work independently under A.15.1, and ground its enactment of the Method. Add A.2.1 and F.6 only when this probe account consumes assignment-bound attribution through the same obtaining A.13 assignment. A missing or failed attribution alone leaves independently admitted probe Work intact. If the finding also questions a premise of that admission, recheck that premise and its dependent claims.

    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.

  7. Return one branch-specific account for the affected claims. State which 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 warranted continuation, repair or stop.

    Return System recognition to A.1 and comparison with an established prior whole to 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 governing patterns; first evidence-use classification to A.2.4 and a needed replayable source-to-use account to A.10; a receiving choice to C.11; and next-action selection during current Work to A.15.7.

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

The following prompts can help state the account; omit those the receiving decision does not need:

Focus: actual U.Work occurrence … / 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: …

Relation result or blocker, and warranted next action or stop: …

For a small reversible use, this ordinary prose is enough. Its conclusion is limited to the named configuration, condition, window and available evidence.

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

When a current or later use needs an identified account, reuse a sufficient episteme or identify one under C.2.1. Arrange durable access when later reliance requires it.

  • An actual-branch account selects the U.Work occurrence as its one truthful EntityOfConcern.
  • A prospective-branch account selects the present U.WorkPlan as its one truthful EntityOfConcern. Its ClaimGraph may designate the declaration-local intended-performance content; that designation alone establishes no dated Work occurrence.
  • The ClaimGraph may also designate independently governed actual or intended performers, supports, state bearers, relation claims, and the 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 warranted next action or stop remain separate claim content.
  • The effective reference scheme always supplies the designation and interpretation rules needed by those claims and adds only the measurement, comparison, or evaluation rules used. Any actual measurement, comparison, or evaluation occurrence remains under the pattern governing it.
  • If one focus cannot truthfully carry the combined claims, keep claims local or use several epistemes. Do not invent a plural focus.

The account describes the configuration or WorkPlan; it is distinct from its focus and carrier. Its claims may support a named target claim under A.2.4. Use A.10 when the source-to-use account must remain replayable; establish each described relation or actual performance under its own rule and facts.

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.

A.15.8:5 - Precision restoration

Recover the object or relation before relying on the umbrella word.

Source phraseRecover before relying on itDo not infer
extended performerSelect the branch first. For actual Work, name admitted performer Systems and obtaining assignments or attribution only through the rules governing those claims. For a WorkPlan, keep intended performers in declaration-local plan content. In both branches name supports, relations, and the boundary selected for the use.Coupled things form one System, Agent, mind, performer, or capability holder.
attentionAfter branch selection, recover the observation, sensing, selection, prioritization, monitoring, search, checking, or capability claim whose obtaining, loss, or change affects the named Work or current WorkPlan.One scalar resource or mechanism is shared by a person, model, robot, organization, and collective.
memoryRecover the holder capability, internal state, model state, record or episteme, persistent runtime state, cultural-continuation claim, or retrieval, update, and forgetting relation that is current.Storage, retrieval, capability, knowledge, model state, and cultural continuation are one value.
computationRecover the operation, Method, performed Work, performing System, inputs, outputs, and resource relation when each is current.A model, calculator, or service performs the containing Work merely because it computes.
checkingRecover the observation, monitoring, evaluation, verification, validation, assurance, or decision and its separately governed result. Identify dated Work only when that occurrence is part of the claim.A checklist or score performs checking, supplies authority, or proves fitness.
work stateRecover the minimum world-side states, claims, intermediate results, commitments, configuration values, bearers, carriers, update/use relations, and currentness conditions needed for the named continuation.A record is identical to world state, or persistence proves resumability.
cue or return pointRecover the sign, representation, event, location, state condition, or source-finding aid; who or what interprets it; and the observation that it changes recovery. Use A.2.4 for a claim used as evidence, A.10 when its source-to-use account must remain replayable, and A.15.4 when appearance-based reliance hides its owner.A cue is evidence of correctness, a universal trigger, or an obtaining recovery relation by appearance alone.
configuration or arrangementRecover the Systems, values, and obtaining or proposed relations needed by the branch. Use A.22 or C.30 only when a selected Structure or architecture claim is required.A support list is already one Structure, architecture, whole, or performer.

Bias check. Human-centered cognitive vocabulary and anthropomorphic AI vocabulary are easy to recognize and therefore easy to overgeneralize. Begin with the Work or WorkPlan and recover the participants, values and relations needed for its result.

A.15.8:6 - Worked cases

A.15.8:6.1 - Literature qualification across a researcher, services, and files

Situation. In this constructed case, LiteratureQualificationWork-2026-08-27-AM runs from 09:00 to 11:00 UTC on 27 August 2026 within the admitted containing System ResearchService-3, enacting the admitted LiteratureQualificationMethod-2. The independently identified performer System Researcher-17 satisfies the local LiteratureQualifierRole criterion by controlling source selection and claim qualification. The declared ResearchAssignment species assigns LiteratureQualifierRole to a System when its question designation and authorized source access obtain. Those stipulated facts establish RA-Researcher17-Question6 throughout this interval and complete the A.13 core.

This constructed case stipulates the full A.15.1:4.1 admission basis, including that core, the independent performance history, A.1:4.2 construction, and a declared containing-System relation covering the complete occurrence. Because this account also compares accountability, F.6 then checks attribution through that same assignment.

A search service, language-model service, repository, pinned papers, claim sheet, and unresolved-question note support the Work; none becomes a performer or constituent of a new whole merely by appearing in the configuration. A reviewer may continue later.

Probe. The fresh-session and reviewer-handoff probe removes the original model session and asks the reviewer to recover the bounded question, source editions, accepted and rejected claim reasons, open uncertainty, and next probe.

Observation and result. The reviewer can recover the papers but cannot distinguish why one claim was rejected because the claim sheet lacks a decision reason and one citation lacks an edition pin. The result focuses on the Work occurrence, identifies the missing source and record relations, and returns two repairs to their representation and source owners. Do not rely on the unrecovered qualification; retain independently supported claims.

What changed. Recover the missing source edition and decision reason for that qualification, or retain the bounded stop.

A.15.8:6.2 - Non-human distributed computation after worker loss

Situation. In this constructed case, SettlementComputationWork-2026-08-27-Run42 runs from 08:00 to 12:00 UTC on 27 August 2026 within the admitted containing System SettlementService-2, enacting SettlementMethod-5. Its independently identified performer Systems Worker-1 and Worker-2 satisfy the local SettlementExecutorRole criterion through observed message processing and settlement-effect control. The declared SettlementExecutionAssignment species assigns that kind when registration for Run42 and connection to its queue obtain. Those stipulated facts establish RA-Worker1-Run42 and RA-Worker2-Run42 throughout the Work window.

The full A.15.1:4.1 admission basis is stipulated, including A.1:4.2 construction and a declared containing-System relation covering the complete occurrence. The performance history establishes the Method enactment. No assignment-bound attribution is required for these workers.

They exchange messages and use an object store, configuration values, intermediate results, completed-effect records, and provenance records. Another worker must continue without duplicating an irreversible settlement effect.

Probe. The independently identified RecoveryTestController-Run42 : U.System satisfies the local RecoveryProbeControllerRole criterion by controlling worker removal and observing recovery. WorkerLossRecoveryProbeWork-Run42-P1 : U.Work runs from 09:15 to 09:20 UTC on the same date within SettlementService-2. The full A.15.1:4.1 admission basis is stipulated, including A.1:4.2 construction and a declared containing-System relation covering the complete occurrence. Its history establishes that it enacts the admitted WorkerLossRecoveryTestMethod-1.

The declared RecoveryControllerAssignment species assigns RecoveryProbeControllerRole when probe designation and connection to the control interface obtain. Those stipulated facts establish RA-Controller42-P1 for that interval and complete the A.13 core. The comparison also uses which assignment covered the probe, so F.6 checks attribution through this same assignment.

The probe removes one worker after a message has been emitted but before its local completion record is available, then attempts recovery from the selected state mechanism.

Observation and result. Process state is recoverable, but channel state and the completed-effect provenance relation are not mutually consistent. The branch-specific account names those state bearers and update/use relations and returns the missing idempotency or provenance condition. A Chandy-Lamport snapshot, event sourcing, transaction protocol, or another computing Method may be selected as the reusable way for the repair. If the receiving account needs a distinct repair Work, admit its performer and occurrence through A.13 and A.15.1 and ground its Method enactment. An ordinary repair need not acquire a separate occurrence identity.

What changed. Add or repair the checkpoint, provenance, or idempotency condition.

A.15.8:6.3 - Equipped performer in a present WorkPlan

Situation. ConcertPerformancePlan-2026-09-12 is one present U.WorkPlan. Its declaration-local content names a musician and a robotic prosthesis controller as intended performers for a proposed performance after device replacement. It also names an instrument, cue source, power support, control link, and allowed latency. None of this content is a future Work occurrence or obtaining assignment.

Probe. The current plan proposes a rehearsal under changed latency and a degraded visual-cue condition. Its material, timing, control, threshold, and stop rules are taken from the applicable music-performance, robotics, human-factors, and safety Methods. If the account identifies a dated rehearsal Work, first recover each actual performer through A.13 and admit that Work independently under A.15.1.

Observation and result. Current evidence leaves recovery after cue loss within the required timing window unresolved. The WorkPlan-focused account names the intended performers, support and control relations, return condition, uncertainty, and the planned probe. Obtain the needed recovery evidence through the planned rehearsal or another sufficient source, or stop the dependent use. Change the cue/control relation or narrow the proposed use when the result requires it. Capability claims for the musician, device, or any independently admitted whole stay separate.

What changed. Resolve the recovery question before relying on a dependent entry-readiness claim. Make any needed configuration repair under the applicable domain conditions.

A.15.8:7 - Conformance and practical checks

A use conforms to this pattern only when it passes the checks that its claimed result needs:

  1. A cold reader can obtain the first result without deciding whether cognition or mind is extended.
  2. The selected focus is one admitted actual U.Work occurrence or one present U.WorkPlan; intended performance remains declaration-local plan content.
  3. Actual performers, intended performers, supports, values, and environmental conditions remain distinct. Every attempted relation claim names participants and the receiving use, applies a current governor when one exists, and preserves its factually unsupported, missing-information, inapplicable, negative, or other result; missing-governor is used only when no rule can state or test that claim.
  4. No arrangement becomes a System, performer, Agent, capability holder, Structure, architecture, or evidence merely by inclusion or wording.
  5. Continuation-critical state names its concern, bearer or carrier, update and use relations, currentness or consistency condition, and return condition when each matters.
  6. The probe uses the least burdensome representative condition that can change the receiving decision; its mechanism, thresholds, safety rules, and evidence rules come from an applicable domain Method. For any dated probe Work, recover the actual performer through A.13 and let A.15.1 independently admit the occurrence; add F.6 only for a consumed assignment-bound attribution, whose failure alone preserves independent Work admission unless the finding also questions an admission premise.
  7. A distinct test or later-performance Work asserted by the account has its own A.13 and A.15.1 basis; ordinary observations may stay within the current Work grain. A proposed condition remains a plan or probe claim.
  8. The result states what the available evidence establishes for the selected condition and window, any unsupported dependency and its reason, and the warranted next action or stop.
  9. A relied-on account has one truthful C.2.1 focus and effective ReferenceScheme; incompatible focuses split instead of forming a plural EntityOfConcern.
  10. Recognition and assurance remain separate; high-consequence use opens direct evidence, assurance, authority, and domain-stop rules.

Recognition check. Ask a reader to produce the compact result from one case in ordinary language. If the reader first needs a theory of attention, a new performer whole, a capability diagnosis, or a full architecture model, repair the entry and boundary.

Assurance check. For consequential use, identify the direct test, evidence, criterion, authority, protected condition, applicability window and stop that the proposed use requires. If a required basis is missing, retain the configuration observation and leave only the dependent readiness, safety, release or permission claim unsupported.

A.15.8:8 - Anti-patterns

  • Composite by coupling. Treating person, device, service, records, and environment as one performer because they jointly matter.
  • Future Work from a plan. Giving intended performance, intended performers, or proposed relations actual Work identity or obtaining attribution.
  • Umbrella slots. Adding universal attention, memory, cue, or Work-state fields instead of recovering objects and relations.
  • Carrier equals state. Treating a note, trace, checkpoint, model context, or file as identical to the world state or claim it carries.
  • Perfect-run readiness. Generalizing one successful live configuration to interruption, handoff, support loss, or changed conditions.
  • Probe as assurance. Treating success under one probe as universal capability, safety, permission, release, or certification.
  • FPF as domain algorithm. Inventing a universal timeout, checkpoint, cue, redundancy, practice, or recovery procedure in this pattern.
  • Configuration as architecture by default. Naming a support list a Structure or ArchitectureRelation without the admission and selection rules.

A.15.8:9 - Consequences and trade-offs

ConsequencePractical effect
Named failure relationRepairs target an assignment, interface, carrier, update rule, source pin, control link, support condition, or return condition rather than a vague lack of attention or memory.
Neutral transferThe same entry and result work for people, software, machines, organisms, teams, and mixed configurations.
Preserved ownershipWork, plan, capability, System identity, representation, evidence, architecture, and choice remain independently checkable.
Better handoff and degraded-mode evidenceA representative interruption or support-loss probe can expose dependencies hidden by a perfect run.
Additional modeling costIdentifying the needed relations and recovery conditions takes more effort than using one umbrella noun.
Bounded conclusionA conclusion is bounded by the named configuration, condition, window and evidence available; further assurance or transfer needs its direct grounds.

A.15.8:10 - SoTA-echoing source effects

Use these source contributions to identify relations and select probes while retaining their domain limits.

Source traditionUse of the cited contributionAction-changing contribution retainedLimit retained
Clark and Chalmers, “The Extended Mind” (1998)Retain as historical lineage and a live contrast; reject constitutive extension as an FPF System-admission or performer-attribution rule.Makes constitutive extension a live alternative and therefore forces an explicit boundary rather than an implicit “extended performer”.Coupling or parity is not an FPF System-admission test, Work-attribution rule, or design Method.
Hutchins, cockpit memory (1995), and Hollan, Hutchins, and Kirsh, distributed cognition (2000)Retain as historical cognitive-science lineage; adapt only the search for information propagation and material supports.Inspect information propagation and material supports around activity, not only an unaided person.An analytical unit is not automatically one System or capability holder, and the human-technology lineage is not universal ontology.
Hollnagel and Woods, cognitive systems engineering, and Fern, NASA HMI study (2016)Retain human-factors and cognitive-systems-engineering lineage plus the 2016 NASA application; adapt only coordination/recovery search and stress-scenario use.Add coordination, synchronization, interface, and recovery relations and use stress scenarios instead of component lists alone.“Joint cognitive system” remains a source-local stance and supplies no general whole identity, authority, safety, or evidence rule.
NASA, Objective Function Allocation Method, page updated 2024Adapt the cited official project record as a scoped systems-engineering and human-factors allocation example.Compare alternative human, automation, and robotic allocations as performance configurations rather than by static stereotypes.Allocation quantities and trade-offs remain systems-engineering and human-factors Methods.
ISO 6385:2016 and ISO/IEC CD 25589Use the cited ergonomic standard as a scoped inventory reference and the cited committee-draft edition as a specialist contrast.Make workers, equipment, space, environment, interaction, and current human-machine-teaming questions visible in the inventory.One is ergonomic and human-centred; the cited edition of the other is a specialist draft. Neither creates a transdisciplinary WorkSystem or team kind.
Hodgetts and Jones, interruption recovery (2006); Ratwani and Trafton, cue association (2010); Ülkü et al., resumption timing (2025)Retain the 2006/2010 human-task studies as empirical lineage and adapt the 2025 study as a bounded probe source.Make return cues and resumption conditions testable rather than inferred from perfect-run performance.Bounded human laboratory tasks establish no universal cue, delay, mechanism, threshold, or transfer to unlike Work.
Chandy and Lamport, distributed snapshots (1985), and Marinho et al., workflow provenance (2021)Retain mature distributed-systems lineage and adapt the 2021 provenance result as a non-human recovery stress test.Supply the non-human contrast: recovery may require consistent process, channel, control-flow, and provenance state.Snapshot and provenance techniques are computing Methods, not universal FPF algorithms or proof that every Work needs a checkpoint.
Hu, Wang, and McAuley, MemoryAgentBench (ICLR 2026), and Liu and Gabriel, PM-Bench (COLM 2026)Adapt these cited benchmarks only for their configuration-specific probe distinctions.Separate retrieval, updating, long-range use, forgetting, deferred-intention execution, and environment monitoring into configuration-specific probes.Benchmark labels are not FPF kinds or capability holders; the reported results do not transfer outside tested agent configurations without evidence.

A.15.8:11 - Relations

A.15.8.MS constructs how methodological material is obtained and applied across the named tasks, including a Method Base only when its maintained shared selection earns its cost. It returns the actual-Work or WorkPlan continuation question here when interruption or support loss is material.

  • Builds on: A.1 and A.13 for admitted Systems and actual-performer cores; A.15.1 for independent actual-Work admission; A.2.1 and F.6 only for a consumed assignment-bound attribution; A.15.2 for present WorkPlans and declaration-local intended-performance content; A.6.REL and the patterns defining obtaining relations; A.6.RCD for the missing-governor, factually unsupported, and missing-information split; and C.2.1 when a use needs an identified account episteme.
  • Coordinates with: A.15.5 for work-entry readiness; A.15.7 when the configuration is adequate and next-action selection during current Work remains open; A.2.2, E.23.CAE, and E.23.CDI for holder capability, the wider access/expression differential, and capability development; A.22 and C.30 for selected Structure and architecture; C.27.TA for temporal/currentness claims; C.2.P.DR and the patterns governing carriers and representations; A.2.4 for first evidence-use classification and A.10 for a needed replayable source-to-use account; A.15.4 for appearance-based reliance repair; C.11 for receiving decisions; domain patterns and Methods for probe mechanisms, thresholds, and safety rules; and subject patterns for authority and evidence. An A.15.8 observation may support an E.23.CAE configuration disposition, while the Work/WorkPlan relation test remains here.
  • Informs: domain patterns for equipped or joint performance, human capability development, organizational coordination, operations and service recovery, human factors, robotics, software and distributed systems, and biological Work when they retain their own quantities, mechanisms, evidence, and stops.

A.15.8:12 - Didactic quick card

  • Which branch? Actual dated Work, or a present WorkPlan with intended performance only as plan content.
  • Who performs? Independently identified actual performer Systems; add assignment-bound attribution only when needed. Keep intended performers within plan content.
  • What supports? Separately identified Systems and values through relations.
  • What must survive? The minimum state and the bearer, carrier, update/use, currentness and return conditions needed for continuation.
  • What do we test? Use an applicable domain Method to define one decision-changing loss, handoff, delay, or reconfiguration; identify a distinct dated probe Work only when the account needs that occurrence claim, with its A.13 and A.15.1 basis.
  • What comes back? What is supported, failed or unresolved for the named configuration and window, and the warranted next action or stop.

A.15.8:End

Referenced in the corpus

51 literal mentions in other sections. Read their context to establish the relation.