SYSE.3:4.4 - Recurse only when the next action depends on it

Open another branch when the current transformer System, capability, Method, tool, or platform contribution must itself be brought about or changed before the current branch can proceed. Apply the same questions to that branch. Do not introduce fixed builder levels: a transformer System can serve several branches or projects, and evidence from a later branch can change an earlier branch claim.

When several branches must be considered together, begin with a Plain provisional realization-network description. Name the proposed members and the missing cross-branch relation or binding. Use E.18 only for one selected transformation-flow structure whose identity is established. Use E.18.NET only after at least two independent member structures, the obtaining cross-flow relation occurrences, the endpoint bindings, applied constraints, and the current use frame are recoverable. Until then, the episteme describes a proposed realization network; it is not the selected network itself. When a cross-branch arrow uses a generic cue—for example creates, builds, uses, supplies, or depends on—replace it with the actual production, participation, use, evidence, integration, configuration, supply, or other relation through the pattern that defines it. If the relation kind or case facts are not yet available, keep the dependency as a provisional claim and name what must be established.

Keep each DesignRunTag local to one leaf-position binding. Represent any wider dependency or Work order through the direct relations that establish it.