DOCA.6:4.3 - Construct paths from their stage-specific configurations

For every material step in a path or branch, name its own starting configuration, finite change, and resulting candidate configuration. Write S_i -> Δ_i -> S_i+1 only as compact notation for those three descriptions, not as evidence that the transition is feasible.

Recover what the starting configuration inherits: established or still-conditional capability, support, access, ongoing Work, resource demand, remaining uncertainty, and effects of earlier choices. If the earlier step has not occurred, the later starting configuration is conditional too. If the path can branch, name the condition that distinguishes the continuations and the stop when neither is supported.

State each step’s transition burden, reversibility, and effects on later options. Do not repeatedly credit the full difference from the original configuration as each later step’s contribution. Use C.11.CRC for finite comparisons with the complete relevant result, resource, affected-System/distributional, and protected coordinates. Each coordinate keeps its own scale and polarity under the common comparison basis. When step horizons or scenarios differ, obtain an adequate mapping or keep those comparison claims separate.

Use DOCA.5 to qualify the jointly necessary transitions, shared resources, timing, and inherited obligations. A sequence of individually plausible steps remains a conditional path until the necessary joint basis exists. Return a missing holder, access, support, or implementation result through A.15.9. Do not substitute a path diagram for the supplying practice’s conclusion.

A path can preserve alternatives without selecting a programme. Human capability-development programmes remain HCD.2’s composition and comparison question; authorized participants retain programme choice, and Learning Product work realizes the selected programme and pattern contributions as a Guide.