Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-10-14 19:58:00 UTC · snapshot created 2026-10-14 19:58:38 UTC · last check 2026-10-15 05:50:10 UTC

C.32.MWA.PP:4.6 - Expose contradictions across structures, participants and scales

Use contradiction here for demands that cannot jointly be met under the proposed conditions, or for claims about the same contribution that cannot jointly hold. A difference in preferences is not automatically such a contradiction. It becomes decision-relevant when a required contribution, legitimate interest, protected condition or resource is affected.

For each claimed gain, perform three connected inquiries.

Follow the changed contribution outward. What receives it, what else uses its performer or means, and what later action depends on it? Preserve the relations instead of assuming every receiver belongs to one management hierarchy. A change can cross a personal task, a team, an enterprise, a professional community and a supplier without making them nested parts.

Ask what was moved. Did a shorter expert response move interpretation to an unqualified learner? Did local autonomy move risk or integration work to another unit? Did a cheaper office consume unpaid community work? Did a more demanding method improve an individual result while preventing sufficient throughput for the whole service? Keep the affected result and bearer identifiable. A gain reported at one scale does not cancel a loss at another.

Challenge the combined mechanism. Hold the stated conditions fixed and ask whether the candidate can obtain all its promised results. Follow a consequential case, including a plausible exception. If a needed contribution is removed, what exactly fails? If local results are obtained, what makes their combination sufficient for the receiving result? Trace the required intermediate results, their receiving operations, interactions and shared conditions. Construct or obtain the missing connection through C.39, and use C.40.JF for unresolved joint reachability. A list of necessary parts does not establish that their combination is sufficient; retain the unsupported whole claim when its obtaining connection is still missing.

Then construct a repair that changes the proposed obtaining relation, not just the wording. Keep a causal hypothesis distinct from a qualified causal conclusion; C.28 governs any causal reliance used in the decision. Possible repairs include altering timing, distributing a decision, adding or replacing a qualified contribution, changing an interface, reserving shared capacity, separating conflicting roles, reducing simultaneous commitments, or revising the remit with its owner. Follow the repair through the same receiving wholes. An extra approval can reduce one error while adding a delay that defeats the useful result.

For example, a local manager is asked to meet a production deadline and release the only qualified worker for the same two-hour development episode. Both commitments may be individually reasonable; together they are unavailable. Naming a development office does not create another qualified worker. The comparison must change a deadline, supply another qualified performer, alter the episode or defer a commitment. Who may authorize each change matters.

Also compare time horizons. Training a second mentor may reduce present help while removing a recurring future bottleneck. Include both periods under the same scenario. Do not count the new mentor’s future capacity before qualification or count the training hours as available client support. Conversely, do not reject the investment merely because a one-week comparison excludes its intended return.

C.32.MWA:4.1(7) supplies the moved-burden question. C.11.CRC:4 supplies the finite configuration, horizons, result and resource coordinates, interactions and future-option effects. Use qualitative explanation where it settles the choice. A multi-scale picture is useful only when it makes a decision-changing relation clearer.