C.32.MWA:4.1 - Eight actions

1. Choose a truthful entry. For an obtaining organization of Method use, anchor one independently admitted representative performed Work occurrence and the useful result at stake; establish the other relied-on relations separately. For a possible-future organization, anchor an intended-use case, WorkPlan, or another correctly typed prospective account; state what would put that proposal into use and how later representative Work would test it. Keep actual development or support Work separate from the proposed use. Actual and prospective claims can coexist in the same account.
2. Name the subject and participants. State the subject under discussion (EntityOfConcern) and the actual kinds of the participants before classifying rows or positions. A source word such as practice, layer, role, model, or provider does not settle those kinds.
3. Build alternatives for the question. State whether the alternatives are competing architecture accounts of the same arrangement, proposed changes to that arrangement, or both. Competing accounts can reveal a relation that a sequence-only description misses; proposed changes alter how the Methods would be used or supported. Keep those comparisons distinct. Prepare alternatives that can change the decision or fail on different cases. When NQD is the current generation test, retain NQD-distinct candidates: their novelty is not a relabeling, their use-value preserves the declared constraints, and their diversity exposes different failure modes. Do not accept the source’s first layout as the option set, and do not turn NQD into one scalar score.
4. Recover each relation actually used. In ordinary words first, state whether the source claim concerns Method composition or order, Work parthood or overlap, a subject relation, description or model use, a capability or provider dependency, cultural dynamics, or another admitted relation. Use the pattern that defines or constrains that relation when the claim matters to the answer. For structures of a Method and its uses, C.30.ASV:4.5a helps select the question before drawing its representation.
5. Separate the described objects from their descriptions. Keep identified Methods, Work, Systems and their relations distinct from the descriptions, models, views and coarse-grained accounts about them. A description can itself be used in Work; name that use separately from what it describes. State the correspondence and the distinctions each description preserves or loses.
6. Reidentify a whole when needed. Use B.2 when the previously identified Method, Work, System, or Discipline whole cannot carry the current claim. Reidentify a selected structure under A.22’s four identity discriminators when the current claim requires a different selected structure. Do not keep the old identity merely to preserve a neat stack.
7. Compare conflict and moved burden. Expose conflicts between candidate structures. For every apparent local repair, ask what residual, constraint, cost, evidence burden, delay, or loss moved to another structure or scope. Compare the alternatives against the named architecture question, not against visual tidiness.
8. Keep deliberate and distributed change distinct. Separate a project’s architecture choice or intervention from cultural generation, transmission, recognition, selection, rejection, retention, and loss. A project can influence those processes without controlling or proving them.