E.18.1:4.0b - Conditional structure extension through E.18.3
Open this extension only when the reader must show explicit branches, joins, guards, paths, preserved structures, omitted-structure notes, or distinct stop and reconsideration questions. Identify one exact U.Structure under A.22.CGUS by its independently identified constituents, selected obtaining relation occurrences, applied constraints, and named selection-use frame. E.18.3 qualifies that selected CGUS only when it uses exact positions, bindings, and already-obtaining occurrences from one independently identified E.18 one-TFS, parent-relative internal-SubflowRef, or E.18.NET substrate. E.18.1 declares no P2W subset schema, wrapper relation, or hybrid record.
| P2W need in the structure-bearing use | Representation recovered from the direct interface | P2W boundary |
|---|---|---|
Cite the accepted starting ProblemCard@Context | Select that already identified C.22.2 episteme as one constituent only when the admitted A.22/E.18.3 structure and current use actually include it. | The accepted card remains a record; selection, a field or adjacency does not make it the structure, a position, a relation occurrence, MethodDescription or Work. |
| Expose transformation-flow topology or positions | Use the exact positions and bindings from the independently identified E.18 substrate plus separately admitted relation-reference epistemes or obtaining occurrence refs needed by the stated decision or use. | Each value and relation keeps its own identity and obtaining basis; citing E.18.3 or a neighboring pattern neither identifies nor routes it, and P2W neither shortens the interfaces nor turns display order into project-work order. |
| Preserve the carried claim and why the decision or use needs it | Use conversational P2W content or the compact C.2.1 episteme in 4.1; cite an exact source, derivation, or current-use relation only when its direct predicate and current facts show that it obtains. | P2W adds no carried-claim field to structure identity, and file history or shared wording creates no source-use relation. |
| State a stop or reconsideration question | Use the admitted structure’s named selection-use frame and the exact condition basis: an applied claim with its test and current facts, an E.18 GuardFail event with its gate-assignment facts, or an independently defined obtaining guard-relation occurrence. Then state the ordinary stop or reconsideration question; add a neighboring relation only when its exact occurrence obtains. | P2W contributes only the local continuation that stops or reopens; a boundary sentence creates no relation, gate, permission, or Work. |
Before choosing the structure branch, distinguish three cases. Several FlowValuation values that resolve to one exact TransformationFlowStructure remain valuations of that one TFS. A detailed internal portion that resolves only through the same TFS positions and internal U.Transfer occurrences remains one parent-relative SubflowRef. Two or more independently identified TFS or nested-network values connected across their boundaries by exact already-obtaining relations require one E.18.NET TransformationFlowStructureNetwork; do not flatten them into one giant TFS. Every network member retains its own boundary, Work, actual transformations, valuations and leaf-local position binding or DesignRunTag. Each nested boundary reference resolves through one finite acyclic memberPath[] to an exact ExposedFlowPositionRef; each selected cross-boundary claim cites its exact obtaining occurrence and complete ordered endpoint bindings through one resolvable NetworkCrossFlowRelationRowRef. Membership is acyclic; a feedback relation may cycle only when its exact predicate and occurrence facts permit that cycle.
If explicit structure is not required, use the stable conversational core. If replay but not structure is required, use 4.1. If the next question is work-facing, apply the A.15 family before claiming a plan, readiness, launch or dated U.Work. Use A.3.4 for each actual transformation and A.15.PROD only for the exact production-work, identity-inception or completion claim currently made. G.11 handles source currentness; E.18 handles one-TFS slice-local refresh; E.18.NET handles independent members and exact cross-member occurrences. P2W reopens only the smallest affected application.