E.18:5.9 - S9 - Transport and crossings

• A GateCrossing records one selected-structure transition between exact source and receiving positions and CtxState bindings at one exact gate whose profile and decision test come from A.21. Cite A.2.6 for locality and scope membership, the current plane or units declaration and conversion rule, each versioned value and exact edition plus G.11 when refresh is current, A.21 for DesignRunTag and the gate decision, and A.15.5 for a prospective work-entry boundary. If no current predicate, applicability condition, occurrence rule, conversion rule, or decision test can state a claim on which the crossing depends, return missing-governor. If the governor exists and the available case basis is sufficient to apply its positive test but that test fails, return factually unsupported; if a fact or declaration needed to decide the test is unavailable, return missing-information. State a negative crossing only under an applicable non-obtaining criterion or complete closure basis and satisfying facts.
• A semantic F.9 Bridge is additional, not constitutive. Use it only when the case identifies two exact F.17 SchemeSenseCell values from different semantic contexts and the Bridge predicate actually obtains. Keep the proposed structural use in a separate C.2.1 claim, recover current A.10 or B.3 reliance when relied on, and keep any Bridge Card or CL optional and non-constitutive.
• An EntityOfConcern change remains with A.6.4. E.18 may place the independently identified r, q, and current-case judgement; it creates none of them, records no operation application by implication, and supplies no KindBridge or mandatory CL. T^D↔T^R is handled at the exact A.21 gate with DesignRunTagFrom and DesignRunTagTo and the current A.15.5 or publication locus, without implying Work occurred.