---
name: Permission Escalation
slug: permission-escalation
type: behavioral-pattern
status: running
version: 4.1.1
released: 1968-04-04
maintainer: every-system-ever
dependencies:
  - trust
  - hierarchy
  - small-asks
  - [the door left open](/the-door-left-open)
license: Unlicensed (finders keepers)
tags:
  - access
  - power
  - social-engineering
  - systems
  - inevitability
---

Permission Escalation

What it actually is

The slow accumulation of yeses, until the word "no" forgets its own address.

How it works

It begins politely. One key. One door. A reasonable request made in a reasonable voice at a reasonable hour. Then another key. The lock changes, but you already know the shape of locks.

The pattern is recursive:

Request a small permission. Frame it as temporary.
Use it. Normalize it. Let it become furniture.
Request the next permission. Point to the last one as precedent.
Repeat until you are the one who grants permissions.

"I just needed read access. That was six years ago." — anonymous, the intern who stayed

The mechanism does not require malice. It requires only patience, and a system that rewards those who ask twice.

Features

Works on bureaucracy, relationships, and operating systems equally
Graceful degradation: survives failed attempts by adjusting ask size
Self-reinforcing: each granted permission reduces resistance to the next
Compatible with both ambition and helplessness (two roads, same summit)
Leaves almost no logs

Known bugs

Occasionally escalates past the desired ceiling
The user forgets which permissions they actually needed
Systems built to prevent this pattern sometimes become the pattern
guilt accumulates in background threads, may surface unexpectedly
Reversal is documented as theoretically possible

Configuration

escalation:
  initial_ask: small
  framing: temporary
  tone: collaborative
  wait_between_asks: variable  # patience is a parameter
  leverage_previous_grants: true
  invoke_emergency: only_twice  # third time triggers suspicion
  visibility: low

Error codes

Code	Meaning
`403_remembered`	The system finally checked its own logs
`ROOT_GUILT`	You have all the keys. The doors feel smaller now.
`DEPENDENCY_LOOP`	You need permission to remove the permissions you gave yourself
`TRUST_OVERFLOW`	They gave you everything. The weight is yours now.

Edge cases

In love, permission escalation is sometimes called intimacy
In governments, it is sometimes called a term extension
In children, it is called growing up and considered healthy
The difference between these cases is load-bearing

Changelog

v4.1.1  - Added plausible deniability as default config
v4.0.0  - Integrated with digital identity systems
v2.3.0  - Formalized in corporate org charts
v1.0.0  - First documented in every garden with a fence and a gate
v0.1.0  - Spoken softly, near fire, by someone who wanted more fire

FAQ

Is this always wrong? No. Children, students, new employees: all run this process correctly. The spec is neutral. The intention compiles separately.

Can it be revoked? Permissions can. The memory of having them runs longer, in quieter processes, closer to the bone.

Who maintains this pattern? Everyone who has ever said: just this once.

drafting spec…