C.38:4 - Solution

Fix one result, receiving use, situation, horizon, and acceptance basis. Construct at least two materially different complete ways by resolving labels into the Agents, Work, Methods, Systems, values, relations, conditions, and enabling branches that can change this decision. Ask the same decision-changing questions of every way, preserve unknowns, then freeze only complete-enough ways for C.11.

C.38:4.1 - Follow the seven-step same-result sequence

1. Fix one result question. Name the sought result by its direct governed kind, the receiver and use, applicable configuration or situation, horizon, acceptance conditions, deciding System, authority boundary, and commitment the decision may make. If rows seek a System, performed service, capability, access relation, and episteme interchangeably, split the questions before comparing.
2. Recover available inputs and exact gaps. Use already-available subject and specialist results only where they fit the same question. Apply A.15.9 only when one bounded result from another practice is missing or needs qualification. That request or return is an input to a way, not the whole way and not the choice.
3. Construct at least two materially different complete ways. Use labels only as prompts. For each surviving way, describe the relevant proposed or already-available Agents, Work, Methods, Systems, values, provision or access relations, enabling branches, and conditions through which the same result could become available. Mark every decision-bearing premise as supported now, proposed, or unknown. Merge labels that resolve to the same decision-changing contents; split ways under one label when a content difference can change the choice. If no second way can be supported, return the missing-alternative or search gap rather than fabricating a peer. When the gap is an unexplained obtaining operation, use C.39 for a candidate explanation or the precise unresolved contribution. Its sufficient-one-way result does not complete this comparison.
4. Use one decision-changing parity basis. Ask the same bounded questions of every way: result and availability condition; performers, Work, Methods, and means; production, transfer, provision, access, custody, or ownership; fit, interfaces, integration, and configuration; evidence, uncertainty, and assurance; support, maintenance, change, exit, and recovery; capability consequences; resources; and consequences for affected Systems. Omit a group only when it cannot change this choice. Keep a decision-reversing unknown as a visible gap.
5. Restore comparability without forcing totality. Keep the result, receiving use, acceptance conditions, situation, configuration boundary, evidence horizon, and burden categories shared. Use ordinary comparison when the ordering is direct. Use A.19.CPM and A.19.SelectorMechanism only when evidence gates, partial orders, incomparability, abstention, or set-valued retention matter. Do not hide protected conditions inside an unexplained score.
6. Freeze and hand off a finite option set. Put only complete-enough whole ways into the current OptionSet, with gaps that the chooser can see. Then apply C.11 for local choice. Its result may choose one way or a retained tie-set, reject the current set, probe again, or reroute. C.38 does not choose by implication and does not gain the chooser’s authority.
7. Name the truthful continuation and reopen. For a retained way, identify the first unsupported realization branch or the direct pattern that now owns the question. Reopen only when a changed result identity, use, acceptance basis, candidate, specialist result, capability, interface, evidence item, burden, support condition, affected-System consequence, exit condition, or observation can change the comparison or choice.

C.38:4.2 - Use a proportional parity view

There is no universal arrangement schema. For the current decision, a small table or a few parallel paragraphs are enough if another reader can answer these questions for every way:

Delete a row that changes no candidate comparison. Add a local question when omitting it could reverse the choice. A candidate is complete enough when its important means, dependencies, burdens, and gaps are visible to this decision—not when it fills a universal checklist.

C.38:4.3 - Return the first result in plain language

For a small case, use this form:

One result and use: [governed result, receiver, situation, horizon, acceptance basis].

Way A / Way B / …: [complete-enough contents, premise status, decision-changing burdens, explicit gaps].

Shared parity basis: [questions actually asked of every way].

Next: [hand the finite set to C.11 / return a missing alternative or probe / use the direct domain Method / begin the first unsupported realization branch after a separate choice].

The result is a comparison claim, not an obtaining arrangement in the world. It establishes no actual performer, capability, authorization, Work, purchase, service, production, delivery, acceptance, availability, or use.

C.38:4.4 - Retain the comparison without duplication

Use the least burdensome way to keep the comparison recoverable:

1. If a domain result already carries the complete same-use comparison and declares this specialization, keep it there rather than producing a second account.
2. Otherwise retain one ordinary C.2.1 episteme about the one result-obtaining comparison, with a truthful EntityOfConcern and effective reference scheme.
3. If a direct domain Method already returns the complete useful comparison more cheaply, use that Method and do not add a C.38 account.

The episteme, table, document, or diagram that carries the claims does not, merely by carrying them, establish a world-side arrangement, selected Structure, architecture, plan, Work, or result availability. Use A.22, C.30, C.29, E.17, or another direct pattern only when its separate question is current.

C.38:4.5 - Separate recognition from assurance

• Recognition. A candidate list whose labels name unlike things, or whose rows omit different burdens, is enough to open C.38. Two parallel ordinary descriptions can be enough for a reversible decision.
• Assurance. Consequential use checks that every row seeks the same result on the same basis, every actual premise has direct support, modal premises remain modal, protected conditions remain visible, and no omitted burden can plausibly reverse the choice unnoticed. Domain acceptance, assurance, authority, realization, and release stay with their direct Methods.