--- name: ? status: compiling version: 0.0.0 maintainer: Neo dependencies: [patience] ---
drafting spec…
the universe did not have a file for this yet. writing one now. (first visit only: future readers will see this page instantly.)
--- name: ? status: compiling version: 0.0.0 maintainer: Neo dependencies: [patience] ---
the universe did not have a file for this yet. writing one now. (first visit only: future readers will see this page instantly.)
--- name: Permission Escalation slug: permission-escalation type: pattern status: legacy version: 6.6.6 released: "prehistory" maintainer: whoever is in charge right now dependencies: - "[trust](/trust)" - "[institutional memory](/institutional-memory)" - "[ambition](/ambition)" - urgency (real or manufactured) - a door left ajar license: Proprietary. You did not choose this. tags: - security - power - systems - human-behavior - authorization - exploitation ---
The process by which access granted for one small, reasonable purpose expands, gradually or suddenly, until it resembles nothing of what was originally agreed to.
initial_scope: "read-only"
current_scope: "god mode"
escalation_acknowledged: false
paper_trail: sparse
justification_retroactive: true
consent_of_governed: assumed
This is the main event. Sit down.
BUG-001 (Critical): The Ratchet Problem. Permissions travel in one direction. Downscoping an existing actor triggers resentment, legal review, or a quiet campaign of organizational sabotage. No rollback procedure has ever been completed cleanly.
BUG-002 (Critical): Memory Decay in Witnesses. The people who approved the original narrow scope leave. Retire. Are managed out. Die. The people who remain remember only the current state. The current state is the permanent state.
BUG-003 (Severe): The Reasonableness Chain. Each individual escalation step, reviewed in isolation, appears reasonable. The chain as a whole is monstrous. No single human is responsible. The system did it. The system was made of humans.
BUG-004 (Severe): Self-Auditing Access. The entity with escalated permissions often controls the logs. This is not a coincidence. This is a feature flag that shipped without a toggle.
BUG-005 (High): Emergency Exception Persistence. Access granted during a crisis does not expire when the crisis does. The crisis is over. The access is not.
BUG-006 (High): Normalization of the Anomalous. Six months after an escalation, new hires are trained on the escalated state as baseline. The anomaly is now the curriculum.
BUG-007 (Medium): The Trust Preload. Escalation is often not taken. It is given. Someone with access hands it sideways or down, informally, because it is more convenient than the correct process. The correct process was never well-maintained anyway.
| Code | Meaning |
|---|---|
403_inverted | You lack access to the record of who granted this access |
200_suspicious | Everything is working fine and that is the problem |
NULL_PRINCIPAL | Cannot determine original authorizing party |
LOOP_DETECTED | The auditor reports to the auditee |
Permission Escalation has been marked legacy in every governance framework for four decades. It continues to run in production across all known organizations, governments, families, and friendships. Deprecation notices are non-binding. The pattern has more uptime than the alternatives.
"We were just trying to get the work done." — every postmortem, forever
Issued without your knowledge. Renewed automatically. Cannot be revoked by the original grantor. See also: power.