SYSE.12:4.1 - Perform the Move

1. Name practitioner Work and result. State the practitioner Agents or inclusion rule, Work family, Method, subject, expected result, current configuration, interval, and receiving decision.
2. Recover the current enabling arrangement. Identify actual Systems—such as tools, model or data stores, compute resources, AI assistants, laboratories, manufacturing cells, integration environments, evidence stores, or support Systems—only where their relations change the Work. Name provider Agents, interfaces, resources, conditions, and failures.
3. Separate capability holders. State the capability demanded of practitioners and the holder, Work family, envelope, measures, qualification window, currentness, and evidence for each platform or provider capability. Support each capability claim with evidence that bears on the named holder performing the Work family in that envelope. Administrative or descriptive records count only when their evidence relation supports that claim.
4. State conditions and direct relations. Name the conditions that bound the claim—for example, access, configuration, performance, evidence continuity, support, exception, fallback, cost, or resource conditions. Then state each direct relation used by the decision: platform participation in Work; production of a named result by a named Work occurrence; supply of the result or access to it from a named provider to a named receiver; receipt or use by that receiver; resource availability or use; applicable promise content; or another governed relation.
5. Use Method repertoire and architecture when they change the choice. A compatible SYSE.15 result can supply available Methods and applicability limits; a compatible SYSE.20 result can supply Method, Work, enablement, and conflict structures. Otherwise use a qualified source or name the missing result.
6. Generate and choose among real alternatives. Build a C.11 option set from feasible complete arrangements. Candidates may retain the current arrangement, change a capability or relation, compose existing Systems, obtain or build a part, branch for a profile, preserve a bypass, or retire a harmful arrangement. Name the deciding Agent, authority, accepted losses, and questions outside that authority.
7. Perform selected platform-development Work. When step 6 selects a change, record the performing Agents, assignments when relevant, Methods, temporal extents, results, actual transformations, resulting configuration, and evidence. A decision record does not change the platform. When the current arrangement is retained, continue to the readiness or use assessment that the receiving decision needs without creating development Work.
8. Issue the pre-use readiness assessment. State only capability and condition claims supported before the practitioner Work, with their evidence cutoff, currentness window, limits, fallback, and stop.
9. Observe use and issue a later assessment. Identify the practitioner Work occurrence and the actual platform participation, provision Work, or resource relation. Observe the consequences needed by the decision—for example, burden, delay, error, rework, recovery, evidence continuity, or results involving the project system-of-interest. Record the later assessment separately and use it only for later decisions.
10. Return and reopen locally. Supply only the supported claims needed by each receiving decision—for example, capability, condition, participation, provision, use, failure, or platform-change claims. Reopen only the claim affected by a changed Work, Method, practitioner population, configuration, provider, condition, evidence basis, or consequence for the project system-of-interest.

This is an A.22.CGUS learning unfolding, not a calendar sequence. Platform development, practitioner Work, support, change of the project system-of-interest, and evidence Work can overlap. Every claimed use still needs an obtaining relation, and later evidence cannot justify earlier reliance retroactively.