---
id: RT-GATE-8
family: RT-GATE
level: core
profiles: [runtime, editor-client]
posture: normative-target
added: "1.0"
changed: "1.0"
source: https://flowdrop.io/spec/rules/rt-gate/rt-gate-8
specification: FlowDrop Workflow Specification 1.0-draft
licence: CC BY 4.0
---

# RT-GATE-8 — Governance can revoke a waiver already stored

*RT-GATE (Part II) · level: core · profiles: runtime, editor-client · added in 1.0*

A waiver was legal when the author stored it. Whether it is still permitted is asked at the moment the gate would fire, against the settings that hold now.

## The rule

> **Normative.** This is the rule.
>
> 1. Whether an author was allowed to make an instance-level confirmation choice is checked at gate time against the current governance settings, not at the time the choice was stored.
>
> 2. Withdrawing the waive control therefore re-gates every instance that had waived, and a stored choice whose control is no longer granted is ignored.
>
> 3. The configuration surface offered to an author must offer exactly the granted controls plus the option to defer to the policy; where no control is granted no such field is offered at all, so a value that is not allowed has no route through which to arrive, and one already stored is inert.

## Related rules

- Names: RT-GATE-7
- Referenced by: RT-GATE-7, RT-GATE-9, RT-GATE-14

---

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.