SYSE.13:4.1 - Perform the Move

1. Name the decision and differences that matter. State the deciding Agent, question, use, project System-of-interest or other subject, interval, and configuration differences that can change the result. Do not begin by inventorying everything.
2. Identify actual and intended subjects. Name every subject needed by the decision—for example, an actual unit, part, site, or possible-future referent. State needed part–whole and structure relations; a product code or bill-of-material row is not the bearer.
3. Choose item boundaries for this use. Designate only the entities that must be distinguished independently, such as Systems, parts, software-package epistemes, or descriptions. Different kinds of receiving Work may choose different boundaries; relate them instead of forcing one granularity.
4. State identifier schemes and mappings. For each item, name the identifier, scheme, issuing or maintaining Agent, interval, and supported mapping to another scheme. Shared spelling is not identity; a mapping need not be symmetric or lossless.
5. Separate variants, units, packages, installations, and editions. Name the variant description, actual units claimed to realize it, software package, observed installed realization, and description edition. Mark unsupported realization claims as gaps.
6. State actual configuration and effectivity. Name the actual constituents, obtaining relations, and characteristic values needed by the decision—for example, parts, interfaces, installed software, or parameter values. State the supporting evidence and interval, then name the subjects and conditions to which every description or change applies. Keep candidate and intended configurations modal.
7. Choose a baseline only for comparison. Identify the reference episteme and its decision. Keep it unchanged for that comparison; establish actual configuration and decision authority separately.
8. Check collisions and return the basis. Align bearer, boundary, scheme, edition, interval, and tolerance before comparing. Classify each problem by the action it requires—for example, repair an actual incompatibility, reconcile contradictory descriptions, qualify a lossy mapping, obtain missing evidence, or accept a harmless naming difference. State receiving Work, the Agent with revision authority, blockers, and the smallest reopen condition.

The numbered presentation is an A.22.CGUS learning unfolding, not a lifecycle. Work may overlap—for example, identification, design, realization, integration, observation, or change Work—but receiving Work can rely only on claims whose bearer and effectivity are known for that use.