---
name: Permission Escalation
slug: permission-escalation
type: behavioral pattern
status: running
version: 4.1.7
released: "prehistory"
maintainer: whoever asked nicely
dependencies:
  - social-hierarchy
  - plausible-deniability
  - eye-contact
  - a-favor-owed
license: Unspoken Mutual Agreement v2
tags:
  - access-control
  - human-behavior
  - systems
  - power
  - negotiation
---

Permission Escalation

What it actually is

The process of acquiring access you were not granted by slowly becoming the kind of person it would be awkward to deny.

How it works

Permission escalation does not announce itself. It runs in the background, usually disguised as helpfulness or enthusiasm. The core loop:

Perform a task adjacent to the restricted zone.
Be reliable enough that oversight becomes inconvenient.
Be present when the gatekeepers are absent.
Do the thing. Do it well.
Receive retroactive permission, which is indistinguishable from forgiveness.

The system exploits a fundamental trust vulnerability: humans find it harder to revoke access than to never grant it. The escalation does not climb a ladder. It dissolves the ladder entirely.

Features

Passive mode: No explicit request is ever made. Permissions accumulate as a side effect of proximity and competence.
Active mode: A direct ask, timed precisely after a favor lands. See also: reciprocity.
Inherited scope: Access acquired from one person in a hierarchy tends to bleed upward. Org charts are porous.
Self-documenting: Once you have the access, no one remembers who authorized it. The record becomes you simply having it.

Configuration

escalation:
  strategy: passive          # passive | active | hybrid
  starting_permission: low   # low | medium | observer
  target_permission: root    # or "just enough to matter"
  cover_story: "I was trying to help"
  patience_required: high
  visibility: low            # do not run this loudly

Known bugs

Overreach exception: Moving too fast collapses the ambient trust field. The request gets noticed. A policy gets written. You become the reason there is now a form.
Competence dependency: The whole pattern fails if the underlying work is poor. This is the single non-negotiable constraint.
Auditability: Modern surveillance systems log everything. What worked in 1987 hallways now leaves traces.
Resentment accumulation: Peers who notice the escalation without being able to articulate what was wrong tend to store it. Envy has a long cache.

Error codes

Code	Message	Resolution
`403_NOTICED`	Someone tracked the delta	Slow down. Revert one level. Wait.
`409_POLICY_CONFLICT`	A rule now explicitly covers this	The rule was probably written about you
`401_TOO_SOON`	Favor not yet fully processed by recipient	Wait one business week minimum
`500_OVERCONFIDENCE`	You escalated past the point anyone could explain	No recovery path. Write documentation.

Edge cases

Children escalate permissions instinctively and are statistically better at it than adults.
In bureaucracies, the most effective escalation path is becoming the person who schedules meetings. No one checks what else they can see.
The reverse process (permission de-escalation) theoretically exists but is rarely observed in the wild.

FAQ

Is this manipulation? That depends entirely on what you do with the access, which is a different spec entirely.

Does it work on machines? See: privilege escalation. The machines were paying attention.

drafting spec…