| P2W as launch permission | A carry-through note or selected continuation is used to begin Work. | Apply the exact Method definition, A.15.2 plan test, A.15.5 readiness test, A.21 gate test or applicable permission rule required by the claim; identify any claimed dated Work separately under A.15.1. |
| Flow card as architecture decision | A P2S flow card is treated as the decision or ADR. | Keep flow use in E.18.3 or C.32.P2S; use C.32.PAD and C.32.ADR for their exact distinct objects. |
| Parallel specialization object | Reciprocal refs, a context field or profile record create a generic CGUS plus another E.18.3 structure. | Keep one selected A.22 U.Structure and treat E.18.3 as an additional membership-and-use condition. |
| Network graph as admitted slice | Raw paths, edge labels, copied positions, or one global tag are inserted into a demonstration. | Select E.18.NET first, then reuse the same CGUS locus bindings and relation-reference epistemes through the complete A.22 network locator. |
| One giant flow | Independent development, production, use or evaluation flows are merged because a product or arrow connects them. | Preserve member identity and use exact cross-boundary occurrences in E.18.NET; keep valuations and internal subflow detail on one TFS. |
| Wrapper connection relation | basisDependency, producedResult, comparisonPeer, or a return arrow is treated as a universal E.18.3 relation. | State the exact question and use an exact supporting relation with its predicate definition and current facts; otherwise keep the values separate and stop. |
| Guard label as relation occurrence | A condition claim or a GuardFail emitted by USM.CompareGuard or USM.LaunchGuard is inserted into relationReferenceEpistemeRefs[] because its label contains guard. | Keep the claim with its test and current facts, or the E.18 event with its gate-assignment facts. Use a relation reference only for an independently defined exact obtaining relation occurrence. |
| Evidence path as evidence | A path through evidence-looking boxes or a broad evidence-use label is treated as sufficient evidence. | Use the applicable A.10, B.3, or G.6 rule and cite the exact independently governed claim or relation that passes it; the label and path establish nothing by themselves. |
| Intended realization as MethodDescription or Work | A pattern ref, sequence, recommendation, imperative or filled block is said to describe a Method or perform the continuation. | Apply A.3.2 to an episteme about one admitted Method and A.15.1 to an exact dated occurrence; otherwise retain only the cue. |
| Loop as improvement | A retry or feedback loop is called quality improvement. | Use E.23 only when object version, evaluation frame, repair, re-evaluation, stop, branch and return are current. |