Emergency Authority Matrix¶
Reference matrix — instantiates Emergency Authority Activation and Constraint
A pre-authored lookup table whose rows are severity tiers and whose cells say what powers each tier unlocks, how they are bounded, and which limits never relax at any level.
The most expensive argument in a crisis is the one about what "emergency powers" actually means, and it is exactly the argument nobody has time for. Emergency Authority Matrix removes it by settling the answer in advance, in cold blood. It is a standing reference table computed before any incident: the rows are graded severity tiers, and each cell states what that tier unlocks (which decisions, access, procurement, or command rights become available), how the unlocked power is bounded (to what purpose, domain, and duration), and — running orthogonally across every tier — a floor of limits that never relax no matter how severe the crisis. Its defining idea is that it is a lookup, not an act and not a record: it does not turn anything on and it does not track anything that happened. It only answers, for a given level, "what may we do here, and what remains forbidden?"
Example¶
A SaaS company defines three incident tiers for its production systems. SEV-3 (degraded performance): the on-call engineer may self-elevate to read-only access on production dashboards, no approval needed. SEV-2 (partial outage): they may grant themselves time-boxed write access to the affected service, but only paired with a second engineer and only on that service. SEV-1 (full outage or active data-loss risk): break-glass root access is unlocked, the change-freeze may be bypassed, and new infrastructure may be provisioned — but three limits hold at every tier and are printed as the floor of the table: customer-data encryption may never be disabled, personal data may never be exfiltrated, and the billing ledger may never be altered.
When a SEV-1 fires at 03:00, the responder does not convene a meeting to discover what break-glass permits. They read the SEV-1 row: root is available, the freeze is lifted, and the three floor prohibitions are bright lines they may not cross even to end the outage faster. The matrix has already made the scope decision; the crisis just executes it.
How it works¶
What distinguishes the matrix from a policy memo is its structure — a cross-product with typed cells, authored and version-controlled before it is ever needed:
- Tiered rows — a small, ordered set of severity levels, each a discrete rung, so that "how bad is it?" maps to exactly one row and one set of powers.
- Typed cells — every power at every tier is one of three states: unlocked, conditionally unlocked with a named constraint attached (a second approver, a time box, a single service), or permanently prohibited.
- Purpose binding in the cell — each unlocked power carries the purpose it is granted for, so an action outside that purpose is visibly out of the cell even if the raw permission exists.
- An orthogonal floor — a register of non-derogable limits that applies identically across all rows, drawn once and immune to tier escalation.
Tuning parameters¶
- Tier granularity — how many severity rows. More tiers fit the response precisely to the harm; fewer are faster to reason about and harder to game.
- Envelope width per tier — how much each tier unlocks. Wider tiers respond to more without escalating but edge toward unbounded power; narrower tiers stay tight but force more escalations mid-crisis.
- Constraint tightness per cell — how heavily each unlocked power is conditioned. Tighter binding curbs misuse but slows the very response the tier was meant to speed.
- Floor size — how much sits in the non-derogable register. A larger floor protects more absolutely but can block a genuinely needed action; a thin floor is permissive but risks eroding hard limits.
- Default stance for the unlisted — whether an action not named in a row is denied or allowed. Default-deny is safer and surfaces gaps; default-allow is flexible but invites scope creep.
When it helps, and when it misleads¶
Its strength is that it converts scope from a real-time judgment call into a pre-agreed reading, and in doing so it makes scope creep visible: an action that is not in the tier's row is, by construction, out of bounds. The floor gives responders and overseers a shared bright line that survives the pressure of the moment.
Its failure mode is the matrix that is authored once and never war-gamed — it silently encodes the last crisis and mis-fits the next — or the tier defined so broadly ("SEV-1 means do whatever it takes") that it reintroduces the unbounded power the archetype exists to prevent. The classic misuse is live-editing the table mid-incident: quietly widening a tier's powers during the crisis to fit what someone already wants to do, which turns the constraint into a rubber stamp. The discipline that guards against this is to version- and change-control the matrix like code, rehearse it against scenarios before you need it, and treat the floor as inviolable even under pressure — the same logic as a graded readiness scale such as DEFCON, where each level maps to a defined posture set before the confrontation, not during it.[n1]
How it implements the components¶
Emergency Authority Matrix fills the what-is-permitted side of the archetype — the standing definition of powers and their bounds:
severity_tier_map— the ordered rows are the tier map: the graded levels a crisis is classified into.authority_expansion_envelope— each row's unlocked cells are the envelope of powers that tier makes available.scope_and_purpose_constraint— the per-cell conditions and purpose bindings are how the envelope is held to its intended use.non_derogable_constraint_register— the orthogonal floor is the register of limits that never relax at any tier.
It does not verify a trigger, authenticate who flips the switch, or announce activation (emergency_trigger_condition, activation_authority_holder, emergency_communication_channel) — that is its nearest twin Crisis Declaration Protocol, which selects and turns on a row this table merely defines. And it does not record which of these powers were actually exercised (audit_and_accountability_record) — that is Emergency Action Log.
Related¶
- Instantiates: Emergency Authority Activation and Constraint — this matrix supplies the standing definition of powers, bounds, and hard limits the whole authority state is measured against.
- Sibling mechanisms: Crisis Declaration Protocol · Emergency Action Log · Incident Command Structure · Temporary Privilege Elevation · Sunset Clause · After-Action Authority Review
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Emergency Authority Matrix operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it a pre-authored lookup table whose rows are severity tiers and whose cells say what powers each tier unlocks, how they are bounded, and which limits never relax at any level.
Independent corroboration: The frozen evidence defines Emergency Authority Matrix as 'A pre-authored lookup table whose rows are severity tiers and whose cells say what powers each tier unlocks, how they are bounded, and which limits never relax at any level', so its operative form is Rule, Policy & Commitment.
Nearest alternative: Representation, Specification & Plan — The matrix externalizes the authority mapping, but its tier-to-power cells prescribe standing permissions and limits rather than merely describing them.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Disaster Management & Risk Reduction
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Specialized
Rationale: Incident-management doctrine cohered severity-tier matrices that pre-map crisis levels to command powers and operational limits.
Related originating lineages:
- Military & Strategic Studies — Military command readiness contributed graded authority and command-level activation tables.
- Public Administration & Policy — Public governance supplies nonwaivable limits and accountable delegation across emergency tiers.
Review resolution: The current reviewers agree that disaster_management is primary. For the reported differences (alternate_origin_disagreement, encyclopedia_synthesis_disagreement), the evidence supports cross_disciplinary_synthesis, specialized, and military_strategic_studies, public_administration_policy; these choices preserve materially formative origins without conflating later domain reach.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The non-derogable floor is separable enough that some designs make it its own artifact; keeping it inside the matrix has a specific virtue — the never-relax limits are printed in the same place, and read at the same moment, as the powers being granted, so a responder cannot see what a tier unlocks without also seeing what it can never touch.
[n1] DEFCON (Defense Readiness Condition) is a five-level graded alert scale used by the U.S. military in which each numbered level corresponds to a predefined readiness posture. It is a canonical severity-tier map: the levels and what each entails are fixed in advance, so escalation is a lookup into a known row rather than an improvisation. ↩