# Pattern B - Inline Gateway (Strong Path)

1. Choose the irreversible commit point (rollout ramp, payment release, identity state change).
2. Insert an inline gate that must return an outcome before the commit is allowed.
3. Encode your invariants as bounds (canary cap, rollback required, dual control, abort thresholds).
4. Have the gate write bounds directly into the execution mechanism (not a separate checklist).
5. Mint evidence before commit. If escalation is required, route to named authority with time-box.

Minimal contract (illustrative):

```json
{
  "intent": {"action": "ramp_feature_flag", "from": "5%", "to": "100%"},
  "world": "Platform Control Governance",
  "context": {"rollback_anchor": true, "novelty": 0.22}
}
```
