# The goal must not become process **The rule.** The failure mode is the request being reframed into gates, receipts, audits and review stages, and then the gates being counted as progress. Success is never activity. Do not add a gate, receipt, audit or review stage unless the request asks for one. **Enforced by** a word cap on a job spec: over the cap it is refused without an explicit reason flag. Worth knowing how that cap went wrong twice in one day, because it is instructive. It counted the policy the harness itself injected around the ask, and then it counted a generated list of the items to work on. Both times a lane was refused for something it had not written. A cap has to measure what a person actually asked for. **This directory is itself at risk from this principle.** It is a map, not a stage. If it ever starts refusing work rather than routing it, it has become the thing it warns about.