---
title: Asking Approval For The Reversible
type: anti-pattern
level: L2
status: live
revision: 1
updated: 2026-08-14
systemVersion: 4.2
tags: [autonomy, process, governance]
rating: 7.95
ratingAxes: useful 8 · evidence 8 · pull 8 · original 7 · form 9
ratingKind: derived
source: plan-first gate, in production
---

# Asking Approval For The Reversible

_Written 2026-08-14 · last verified 2026-08-14 · system v4.2 · live_

**TL;DR** — A planning gate designed for expensive or irreversible work gets applied to routine reversible tasks too, because triggering on step count is easy and triggering on consequence is not. The result is approval fatigue: the same person now rubber-stamps the plan that actually mattered.

## Pattern

A rule says: before a large task, present a plan and wait for approval. Sensible, and it exists because of a real incident.

The trigger is step count. So a 6-step file reorganisation — fully reversible, zero cost — gets the same ceremony as a purchase commitment.

## Why it looks right

Step count is easy to evaluate and hard to argue with. Consequence is a judgement, and a gate that depends on judgement can be talked out of, which is precisely what a gate is supposed to prevent.

Erring toward more approval also feels conservative, and conservative feels safe.

## Why it fails

**Approval has a budget and it is small.** One project measured it: 20 minutes of reading per item, deferred until approvals stopped happening entirely after 84 days. Every unnecessary plan spends attention that was reserved for the one plan that needed it, and the effect is not linear — after enough trivial approvals the reader stops reading and starts scrolling to the button.

The gate then fails in the worst way available: still present, still logged, no longer performing its function. And it fails silently, because a rubber-stamped approval is indistinguishable in the record from a considered one.

## Instead

Trigger on **consequence**, with step count as only one of several conditions:

> ≥5 steps **or** material cost **or** irreversible → plan and wait
> reversible **and** low cost **and** internal → act, report after

The important half is the second line. It has to be written explicitly, or the default drifts back toward asking about everything.

One further refinement earns its place: where the trigger fires on *irreversibility specifically*, escalate rather than merely asking — that is the last moment the decision is still free, and it deserves more than a yes-no prompt. Ordinary size is not that moment.