--- id: RT-GATE-11 family: RT-GATE level: core profiles: [runtime] posture: normative-target added: "1.0" changed: "1.0" source: https://flowdrop.io/spec/rules/rt-gate/rt-gate-11 specification: FlowDrop Workflow Specification 1.0 licence: CC BY 4.0 --- # RT-GATE-11 — A gated node whose executor cannot be resolved never executes *RT-GATE (Part II) · level: core · profiles: runtime · added in 1.0* Fail-closed here means error, not ask. Reading a missing executor as "no side effects" silently ungates the node; asking about a call that can never run trains operators to rubber-stamp. ## The rule > **Normative.** This is the rule. > > 1. Where a node's confirmation requirement is derived from its executor and that executor cannot be resolved (no such executor is defined, or its implementation is unavailable), the node MUST NOT execute. > > 2. It MUST NOT raise a confirmation prompt. > > 3. The derivation fails, and the node MUST fail as any node with an unresolvable executor does. > > 4. An implementation MAY elsewhere let callers probe an executor's declarations without raising, treating an unresolvable one as declaring nothing. > > 5. That leniency MUST NOT be used at the gate, where it would read a missing executor as harmless. ## Why Recorded under [OPEN-25](https://flowdrop.io/spec/rulings/open-25). ## Related rules - Names: RT-GATE-1, RT-GATE-7 - Referenced by: RT-GATE-7 --- Rule identifiers are permanent and are never renumbered. This specification carries no implementation status: each implementation publishes its own standing against these rules. Licensed CC BY 4.0.