A.21:4.7 - Optional LaunchGate use

Use LaunchGate only when an A.21 gate-decision relation is current for one prospective workEntryClaimRef, WorkPlan or PlanItem entry question, and bounded attempted action. The gate refers to that prospective claim; it never targets a not-yet-existing Work individual.

A.15.5 remains the ordinary route for full-kit and work-entry readiness. Add a LaunchGate only when the selected transformation-flow structure actually contains that gate use. Freshness, design-run-tag consistency, A.20 ingress validity, structural crossing, and SquareLaw are checks only when their exact claims, rules, and defining patterns are current. No one of them is mandatory merely because the word “launch” appears.

If a required ingress A.20 summary is not satisfied and the applied profile defines a pre-run barrier, the aggregate is block. Other available results remain visible; deferred checks remain notRun.