A.10.1:4 - Solution

Use the outline in 4.1 to locate the current move; sections 4.2–4.7 give its comparison criteria, fields, and stop conditions.

A.10.1:4.1 - Perform the Nine-Step Move

1. Start from the changed source, not a presumed receiver. Name the predecessor and later or replacement source epistemes, the claim set whose change may matter, and the present question that bounds the search. Leave source identity, edition continuity, access, or applicability unresolved when the required fact is missing.
2. Compare claims rather than files. Separate changes in proposition, subject, scope, applicability, assumptions, limits, evidence status, and effective conditions from wording, layout, publication, carrier, and revision-label changes. If comparison establishes compatible meaning, applicability and access, finish with any needed reference repair. If comparison cannot establish them, return the material gap; neither branch requires a multi-use search merely to record its stop.
3. Select a receiving-use search frame. Use the search-frame fields in 4.3 to state where a receiving use would count for the present question.
4. State reproducible discovery coverage. Name the exact source identifiers, claim addresses and aliases used; the included search surfaces; the source-outward and receiver-oriented routes; and every unsearched, inaccessible, stale, unindexed, or identity-ambiguous surface.
5. Discover and then name candidate receiving uses. Use search, citations, lineage, traces, indexes, owner knowledge, or tools to find candidates. Inspect the receiving content and recover the exact premise, evidence-use, operation-argument, specification, decision-basis, or other direct relation. Discovery alone establishes no reliance.
6. Classify and bound reach. Distinguish actual dependence, irrelevant mentions and unresolved uses within the searched frame. Group equivalent irrelevant mentions when one inspected reason covers them. Retain the direct-use basis and gaps that can change the receiving conclusion, without a separate exclusion record for each mention. Follow a depends branch only through another exact use relation while a receiving action can change. Supply the discovery-and-reach content needed by each subject judgment.
7. Apply the direct subject pattern’s guidance. Use the discovery-and-reach statement to apply that guidance to the changed claim, exact direct use, current conditions, affected reach, coverage limits, and material subject facts. The practitioner or admitted System carrying out that application may find that the proposed dependence must be narrowed or rejected or that stronger evidence is required. Use adequate existing evidence and return the supported subject result or its scoped blocker directly to its existing consumers. Further inquiry is selected for the receiving question; a discovery gap alone does not commission Work.
8. Supply a common account when a receiver needs it. A sufficient direct subject result can finish the use. If another receiving question needs an overview, cite the independently governed results and summarize only the consequences it needs. That summary neither replaces those results nor changes A.10 RelianceDisposition.
9. Stop at the completed receiving answer. Apply the branch conditions in 4.7. Preserve the coverage and direct-use basis needed for the conclusion actually returned, including material gaps. Name a next actor or reopen observation when the receiving use needs that continuation. An unresolved independent branch need not delay a completed one.

This numbered presentation is an A.22.CGUS learning unfolding, not a lifecycle and not a mandatory sequence of U.Work. Discovery, source recovery, subject inquiry, and communication may overlap. Only the information dependencies in the move impose order.

A.10.1:4.2 - Compare the Source at Claim Size

Recover each source as a C.2.1 episteme: a claim-bearing informational object, not its file or display. Name the predecessor and later or replacement episteme, their relevant claim addresses, subjects, interpretation bases, effective conditions, and edition relation when that relation is established.

Treat a difference as material here only when it can alter a receiving action or result. Useful comparison dimensions are:

Wording can change without meaning changing; one word can also reverse an obligation. A text diff is a locator, not the semantic verdict.

If the same source episteme is merely republished on a new carrier, update the governed identity, publication, representation, availability, or one-use reliance facts through C.2.1, E.17, E.24.PUB, and A.10 as applicable. Do not open the several-use search unless availability itself changes the bounded reliance question.

A.10.1:4.3 - Bound the Search Frame and Make Coverage Reproducible

These fields apply when affected-use discovery is selected. Set the frame before treating found candidates as the universe. Keep it in the existing result or working source at the detail needed to interpret the search. A harmless reference repair opens none of these fields. A claim of no impact across a frame does require adequate coverage and support for that frame.

Coverage is adequate only relative to that frame. Use complementary routes:

• Source-outward discovery starts from exact source identifiers, claim addresses, aliases, citations, backlinks, provenance, data or model lineage, declared traces, and transformations.
• Receiver-oriented discovery inspects the included receiving families for the same or an equivalent premise, limit, parameter, assumption, evidence use, or decision basis, even when the source identifier is absent.

One justified complete index may cover both directions. Otherwise state both routes and their limits. For every surface, record the query or inspection basis, the source identifiers and aliases used, the date or source value inspected when it matters, and the result or gap. An unsearched, inaccessible, stale, unindexed, or identity-ambiguous surface is a discovery-coverage gap. Outside the covered surface, a use is not found, not established unaffected.

A.10.1:4.4 - Confirm Direct Reliance Before Following Reach

Search output supplies candidates. The receiving content supplies the reliance test.

These discovery dispositions answer whether a found candidate belongs in the affected branch. They are not A.10 RelianceDisposition values. Use A.10 to judge whether one bounded evidence use passes, degrades, abstains, reopens, needs evidence or assurance, or is blocked for current use.

A citation, a present or missing trace, storage, indexing, carrier co-location, succession, ownership, declared dependency, graph reachability, or a shared keyword does not establish depends. A missing trace may be a discovery or coverage gap; it is not impact and it does not prove no impact. Conversely, an undeclared use can depend when the receiving content actually uses an equivalent premise.

Follow a depends branch only through another exact direct use relation. Stop before a downstream item whose action, condition, result, or required check cannot change. The affected reach is the smallest dependency-closed structure that contains every in-frame use that can change an action; it is not every transitively reachable node.

For a branch that needs subject judgment, supply the following discovery-and-reach content at the detail required by its receiver. It may already be present in the direct result; no second statement is needed:

The statement is usable claim content for that subject judgment, not a new mandatory carrier or universal record. A table, list, matrix, or optional G.6 path slice may present it; the representation establishes none of its relations.

A.10.1:4.5 - Apply Direct Subject Guidance and Keep the Result Independent

Discovery and reach classification prepare the branch for subject judgment. A practitioner or admitted System applies the direct subject pattern’s concrete rule or test to each depends branch. Recover or recheck facts about current conditions, evidence, authority, cost, and Work only where those facts can change the independently governed result.

A practitioner or admitted System may, by applying the direct subject rule or test, narrow or reject the proposed affected reach. Keep the independently obtained result on its existing direct route: the engineering source-change result governed by SYSE.19 goes to SYSE.14; revision feedback governed by FIN.17 goes to FIN.4; and the assumption-impact result governed by STR.2 goes to STR.3 and STR.4.

When a common account is needed, it cites independently governed subject results and is never their own input. The information dependency is:

material source change → needed discovery and reach → application of direct subject guidance → independently governed subject result → common account, if a further receiving use needs it

A.10.1:4.6 - Complete the Affected-Use Revalidation Account

Prepare a common account only when a receiving question needs an overview beyond the sufficient direct results. Cite each independently governed result used by that overview. A repaired reference or a direct subject result can close its own question without this account. When durability or reliance requires an episteme, ordinary C.2.1 content is sufficient.

Preserved, narrowed, reopened, superseded, reliance withdrawn, and blocked are local prose summaries, not a universal status vocabulary. When they summarize subject judgments, they require those judgments’ basis. They replace neither RelianceDisposition nor assurance, permission, authority, release or decision.

Keep earlier source editions and prior results recoverable for their original uses and conditions. A later source does not rewrite what an earlier source meant. Reuse a prior result only when its conclusion and conditions remain current and the changed claim lies outside its actual dependency.

A.10.1:4.7 - Stop, Return Gaps, and Reopen Locally

Close the branch that answers the present question:

Retain the history and reasoning needed to reuse the result. State who must receive an unresolved action question or what would reopen a continuing use when that information changes practice; a completed small repair need not create a monitoring arrangement.

An inaccessible or unsearched surface is not established unaffected. Reopen locally when a source, claim, direct relation, included surface, subject result or applicability condition changes enough to affect the current conclusion. Use A.15.9 and C.11.DUA when further acquisition is considered; attainable contribution and whole burden govern its selection without weakening support or authority conditions.