SYSE.19:4 - Solution

Compare source claims, recover their actual engineering uses, and revalidate only what is needed to decide whether the affected engineering decisions remain usable.

SYSE.19:4.1 - Perform the Move

Name the receiving decision. State the engineering decision at risk, any relied-on Work result, the current configuration and use, the relevant interval, and the action that could change.
Identify the source epistemes. Recover the predecessor and later claim-bearing epistemes, their applicability, provenance, and publication or carrier facts when those facts matter. Establish an edition relation only when its predicate obtains; otherwise treat the later source as a replacement candidate or record an identity gap.
Compare claims rather than files. State every material change in claim content or applicability—for example, proposition, scope, assumptions, limits, evidence status, or MethodDescription content. Classify the remaining differences as publication or carrier changes. When relevant meaning, applicability and access remain compatible, finish with any needed reference repair. Missing comparison facts remain a scoped gap.
Recover direct reliance. For each material claim, inspect candidate receiving content found by means such as search, citations, traces, or AI assistance. State the decision or Work result and the direct premise or evidence-use relation that connects it to the claim.
Bound the affected reach. Distinguish depends, mentions only and unresolved within the searched frame. Group equivalent irrelevant mentions; retain a short exclusion reason in the existing result when its receiver needs it. Follow a depends branch only while a downstream engineering action can still change. Use A.10.1 when several receiving uses still need discovery; retain the search coverage needed for the stated conclusion.
Choose any needed revalidation Work. Use adequate existing evidence first. A scoped limitation or blocked use can be the completed answer. Select further Work under C.11.DUA when its obtainable contribution warrants the complete programme burden within the receiving window. For selected Work, name the Agent, Method, configuration, conditions, evidence need, authority, cost and stop. Cost does not make an unsupported use safe or supply missing permission.
Perform and qualify selected Work. Identify actual performed Work and returned evidence separately. State what the result supports for the current configuration and what remains unknown.
Decide separately for each affected engineering decision. Assign one decision disposition from the closed set in section 0.1 and state its reason, evidence and applicable interval. Name next Work only when selected for this receiving use. A passing check becomes a decision premise only when authorized decision Work uses it.
Supply the result and preserve history. Give the Agent making the relevant engineering change or release decision the supported use, relevant revalidation evidence and material blockers. This direct return can finish the question. A further common account is needed only for a receiver who needs that overview. Keep earlier source editions and decisions recoverable for their original uses and intervals.
Stop at the completed receiving answer. Finish a compatible reference repair directly. For material change, return the qualified in-scope decisions or exact blockers and preserve independently resolved branches. A no-impact claim requires adequate discovery coverage and actual-use support; uninspected or inaccessible surfaces remain gaps.

The numbered presentation is an A.22.CGUS learning unfolding, not a lifecycle or a required Work sequence. Source comparison, design, testing, operation, and release Work may overlap. Only dependencies established for the current claims impose an order.

SYSE.19:4.2 - Record the Result

Record only the content needed by the receiving decisions in their existing result. The rows below apply to the branch actually taken; a harmless reference repair needs no revalidation dossier.

Result position	Content when needed by this receiving decision
receiving decision	Engineering decision, any relied-on Work result, current configuration and use, relevant interval, deciding Agent, and action that may change.
source comparison	Predecessor and later or replacement epistemes; material claim changes; publication or carrier changes; source-access and identity gaps.
direct reliance	Every affected decision or Work result, the source claim on which it depends, and the premise or evidence-use relation that establishes the dependence.
affected reach	Actual-use bases and unresolved candidates that affect the conclusion; equivalent irrelevant mentions may share one exclusion reason. Retain discovery coverage and the last action-changing decision.
revalidation	For selected revalidation: planned and actual performed Work, Agent, Method, configuration, conditions, evidence needs, authority, results, cost and stop.
decision dispositions	One disposition from section 0.1 for each affected decision, with reason, evidence and interval; next Work only when selected.
continuation	Material gaps and historical source/decision references; a receiving Agent or reopen condition when the actual continuation needs one.

For example, a compact table, linked decision note, model query result, or generated report may present this episteme. Treat the form as a representation; keep the source claims and direct-reliance relations recoverable.

SYSE.19:4.3 - What Changes in Practice

Engineers stop using a source version as a proxy for impact. A source update can matter while the engineered System stays unchanged because the warranted decision basis changed. A carrier update can leave engineering decisions usable when claim content and applicability remain compatible.

Revalidation produces a bounded decision result: it identifies decisions that remain usable and decisions that need new Work. Search and AI-assisted comparison reduce discovery effort, while an Agent with suitable capability and authority judges materiality and applicability.