ME.7:4 - Solution
Recover the proposed whole’s semantics, test whole and participant identity separately from relation truth, and return the strongest branch the evidence supports.
ME.7:4.1 - Pattern-Use Unfolding
- Name the receiving use. State the result or preserved condition, situation family, intended users or performers, consuming decision, configuration or edition, and time window.
- Recover whole semantics. State the reusable operations or invariant, entry and exit, applicability, participants, permitted variation, bounds, stops, and reidentification rule. If these cannot be stated, return the missing-account question.
- Preserve participant statuses. Identify each Method under
A.3.1where supported. Keep candidate accounts and other subjects at their existing statuses. - Name the relation sets. State every load-bearing proposed or obtaining relation, including Method composition, Work order or overlap, result use, allocation, support/provider access, authority, and description correspondence as applicable. Do not infer one relation from another.
- Test the positive branch. Record an obtaining composition only when the whole and parts are identified as Methods and the required
B.1.5relations are shown to obtain within the bounded claim. - Return the prospective branch when needed. State the candidate whole, participant statuses, proposed relation sets, guards, adapters, alternatives, recovery, variation points, burdens and unresolved conditions needed for the receiving use. A traceable proposal can answer that use while its stronger whole claim remains unresolved.
- Lower independently. When whole semantics, identity, or one relation remains too weak even for a useful candidate, return the supported fragment, relation claim, WorkPlan question, or stop. Do not pad the account to look complete.
- Choose a useful continuation when needed. Use C.11.DUA to compare the result a realizable implementation or trial could add with its full burden, including access, allocation, authority and the available window. When that Work is selected, name its observations, acceptance and failure conditions, authority and reconsideration rule; prepare a WorkPlan where coordination needs one. Otherwise finish with the supported account or lower result and the limitation that matters to its recipient.
ME.7:4.2 - Record the Result
| Result position | Required content |
|---|---|
| use and whole semantics | Intended result/preserved condition, situation, operations or invariant, applicability, participants, variation, bounds, and reidentification. |
| participant account | Each subject, kind or status, identity basis or open condition, and proposed contribution. |
| relation sets | Each direct relation, truth status, evidence, guard, and receiving use. |
| branch verdict | Obtaining composition result, prospective candidate account, or lower return with decisive reason. |
| prospective content | Guards, adapters, alternatives, recovery, stops, burdens, and variation points when the lower branch applies. |
| continuation, when selected | Later Work and observations, authority, acceptance/failure and reconsideration condition; a realization/test WorkPlan where its coordination needs one. |
ME.7:4.3 - What Changes in Practice
Practitioners can write and test a coherent proposed Method without pretending that documentation created it. A positive composition claim becomes stronger because its identity and relation evidence are explicit; a prospective account remains useful for comparison through its guards, variation, recovery and stated limits. A selected implementation or trial adds the continuation needed to learn more.