PSD.6:4.4 - Combine contributions through explicit joins

Combine only when the second Method contributes something material the first cannot provide at acceptable effort. Name the result or preserved condition passed between them, its meaning, the receiving precondition, and what happens when the join fails.

An attributed concern map can supply candidate objectives for examination. It cannot supply legitimate numerical weights without the separate elicitation and value assumptions those weights require. A qualitative scenario can supply a condition for technical analysis, not its probability. Keep such conversions as explicit additional work or leave the outputs uncombined.

Recover order from dependence. An analysis may need a specific formulation before it can run, while participation inquiry and technical evidence collection can proceed concurrently once their common question is clear. Their later join still needs compatible subject, conditions, meanings, and limits. Document order, calendar order, and simultaneous use do not establish Method composition.

When the engagement needs one composite U.Method, first identify the whole under A.3.1, then use B.1.5 to qualify its independently identified part Methods and whole-forming claims. State the whole action, applicability, accepted inputs, result, required joins, allowed variations, exposed interactions, and failure or stop conditions. A different part, ordering, or interface outside the permitted variations can identify another Method.

If several Methods are merely coordinated without a recoverable whole, return that bounded arrangement honestly. It may be useful interim planning content, but it is not yet the promised engagement Method. Name the missing whole-action or join question rather than relabeling the activity list.