E.18.3:0 - Use This When

Use this pattern when a team is planning, reviewing, or explaining a transformation and a route-like flow card is useful, but branches, joins, guards, or connections to independently identified neighboring values or neighboring claims already shown to obtain determine what can follow. The practical need is to recover those transformation-flow relations without treating displayed order as performed-work order, evidence, decision, or authorization.

The admitted object is the same selected U.Structure already identified under A.22 and qualified as a CGUS by exact constituents, selected obtaining relation occurrences, applied constraints, and one named selection-use frame. E.18.3 recognizes that object under an additional transformation-flow unfolding condition; it does not manufacture a generic CGUS plus a reciprocal narrower structure. That condition uses one independently identified E.18 substrate branch: one TFS, one parent-relative internal SubflowRef within a TFS, or one selected E.18.NET network. The A.22-selected CGUS uses exact substrate positions, bindings, and already-obtaining occurrences; the substrate ref does not resolve to selectedCGUSRef and is not a second CGUS.

Do not use this pattern merely because a visible record or description is a route, path, graph, process map, chain, loop, or swimlane. First ask whether a branch, join, condition, dependency, crossing, or connection changes the continuation question for the thing being transformed. E.18.3 membership requires the A.22 identity, CGUS locus bindings and potential topology, and one of the three E.18 substrate cases with its flow positions, bindings, and obtaining occurrences. The current continuation result is evaluated separately. Description loss, C.33 notes for a declared architecture use, publication, and stronger neighboring claims are added only for uses that need them.

The first useful move is small and ordinary: name the concrete thing being transformed, mark two recognizable places or states on the flow card in domain language, state the proposed connection or guard, and ask which continuation depends on it. A useful result can be a provisional explanation that names the missing relation, fact, or constraint. It need not yet be asserted as a C.2.1 episteme, E.18 position mapping, or selected A.22 structure. If that explanation answers the current use, stop there.

Only when the team must assert E.18.3 qualification, compare or publish the selected structure, or support a stronger downstream claim should it recover the A.22 identity, CGUS locus bindings and potential continuation rows, the E.18 or E.18.NET positions and bindings, obtaining relations, applied constraints, and current continuation judgements. Add replay fields, C.33 loss notes for a declared architecture use, publication material, or downstream assurance only when that named use needs them. Here move is Plain wording for the current action, not a universal kind or relation; a proposal, selection result, or formalized description does not establish that the proposed action was performed.

What changes in practice. The practitioner stops asking whether a diagram “looks like a flow” and first names the concrete transformation subject, two recognizable places or states, the proposed relation or guard, and the smallest honest continuation question. Exact structure identity, E.18 or E.18.NET bindings, already-obtaining relations, and replay fields are added only when qualification, comparison, publication, or stronger reliance makes them material. A provisional explanation or later demonstration can guide attention without becoming the structure, a MethodDescription, a WorkPlan, or performed Work.