0. Plain Statement
Emergency power without sunset becomes ordinary control.
Plain-language version:
Emergency power can be necessary when active harm, crisis, collapse, breach, disaster, or rapid destabilization threatens coherence.
But emergency power is not meant to become normal.
If emergency override does not have scope, sunset, audit, restoration, review, and recurrence reduction, it drifts into ordinary control and creates hidden debt.
1. Formal Definition
The Emergency Normalization Law states that emergency override, emergency authority, crisis control, extraordinary restriction, exceptional surveillance, temporary enforcement, rapid containment, and emergency governance must remain bounded by explicit scope, sunset, audit, restoration, review, and recurrence-reduction requirements.
Emergency action may be coherent when it is needed to:
- stop active harm;
- preserve life or critical coherence;
- prevent cascading failure;
- contain unsafe coupling;
- protect a boundary under acute threat;
- preserve evidence;
- restore minimum system viability;
- protect harmed nodes;
- interrupt adversarial forcing;
- create a temporary repair window.
Emergency action becomes incoherent when it:
- persists after the emergency;
- expands beyond its original scope;
- becomes ordinary governance;
- bypasses audit;
- suppresses feedback;
- avoids repair;
- normalizes surveillance;
- normalizes enforcement;
- erodes boundaries;
- increases control density;
- creates dependence on crisis powers;
- converts temporary exception into permanent architecture.
Emergency override must have:
- scope;
- sunset;
- audit;
- restoration;
- review;
- recurrence reduction.
Canonical failure:
emergency power - sunset - audit - ℛ ⇒ ordinary control + H↑Therefore, emergency control is valid only as a bounded phase in a restoration sequence.
2. Canonical Form
Core form:
emergency power without sunset becomes ordinary controlEmergency-valid form:
emergency override valid ⇔ Σ scoped + Τ sunset + Au intact + ℛ linked + review activeFailure form:
emergency Π - sunset - audit - ℛ ⇒ control normalization + H↑Control ratchet form:
temporary override + recurrence of crisis framing ⇒ control ratchet↑Restoration form:
emergency containment → repair → review → sunset → recurrence preventionRestoration-valid contrast:
emergency authority coherent when it reduces active harm, restores boundaries, repairs debt, and terminates or narrows over ΤRelated variables:
O, H, H_security, ε, ι, Au, Au_eff, µᵢ, BΣ, K, σ, R, R_eff, 𝓑, 𝓓, Φ, Λ, ⊗, Γ, Π, Ξ, ℛ, Θ, Σ, Ψ, Τ, FI, MS, L, emergency_scope, emergency_duration, sunset_condition, override_power, control_density, review_integrity, restoration_linkage, recurrence_reduction, force_debt, crisis_framing, normalization_pressureWhere:
| Variable | Meaning in this law |
|---|---|
emergency_scope | Domain, target, authority, duration, and boundary of emergency power |
emergency_duration | How long the override remains active |
sunset_condition | Explicit condition or time at which emergency authority terminates, narrows, or requires renewal under audit |
override_power | Temporary authority to bypass ordinary constraints for acute containment |
control_density | Degree of control, restriction, surveillance, or enforcement imposed |
review_integrity | Ability of independent or affected review to inspect emergency action and continuation |
restoration_linkage | Degree to which emergency action routes into repair, boundary restoration, and recurrence prevention |
recurrence_reduction | Whether the emergency response reduces future crisis likelihood |
force_debt | Debt created by coercive or restrictive emergency action |
crisis_framing | Narrative or classification that marks conditions as emergency |
normalization_pressure | Pressure for temporary controls to become ordinary governance |
O | Coherence; emergency power is valid only if coherence is preserved or restored |
H / H_security | Hidden debt; rises when emergency control outlives repair need |
BΣ | Boundary integrity; emergency power must protect boundaries without permanently eroding them |
Au / Au_eff | Auditability of emergency decision, scope, costs, effects, and continuation |
R / R_eff | Restoration capacity needed to move beyond emergency containment |
FI | Feedback integrity; emergency action must remain corrigible |
MS | Moral / meaning symmetry; emergency power must not apply asymmetrically without coherent justification |
L | Legitimacy; decays when emergency powers normalize without review and repair |
ι / Ξ | Inversion when emergency language justifies permanent control |
Φ | Visible order, incident suppression, or crisis management proxy; not proof of security |
Γ | Classifies emergency type, active harm, scope, threshold, continuation, and exit condition |
Π | Operationalizes emergency controls, restrictions, response pathways, review, and sunset |
ℛ | Restoration required to exit emergency mode |
Θ | Humility preventing emergency certainty and power ratchet |
Σ | Scope, limits, domain, and authority contour of emergency action |
Ψ | Field and affected-node feedback validating emergency effects |
Τ | Time validation, sunset timing, and recurrence review |
3. Core Mechanism
The law unfolds because emergency powers are designed to bypass normal constraint layers, and bypassed constraints tend to remain weakened unless actively restored.
Coherent emergency pathway
acute threat appears
→ emergency threshold is classified
→ scope and sunset are defined
→ override is used narrowly
→ audit and review remain intact
→ restoration activates
→ recurrence conditions change
→ emergency power terminates or narrows
→ legitimacy stabilizes over timeEmergency normalization pathway
acute threat appears
→ emergency power expands
→ visible order improves
→ review weakens
→ repair is delayed
→ control becomes routine
→ emergency framing persists
→ boundaries erode
→ hidden debt and legitimacy debt riseThe core mechanism is:
emergency override weakens ordinary constraints; restoration must rebuild themDetailed mechanism:
- A crisis or acute threat appears.
The system faces active harm, destabilization, breach, collapse, or dangerous uncertainty.
- Emergency override activates.
Normal procedures, boundaries, consent structures, review steps, or delays may be temporarily bypassed for containment.
- The override creates control capacity.
This may be necessary, but it also creates force debt, boundary debt, legitimacy load, and risk of power drift.
- Restoration must begin immediately.
Emergency action should create a repair window, not a permanent regime.
- Sunset and review prevent normalization.
The system must define when emergency power ends, narrows, or requires renewed justification.
- Without sunset, control ratchets.
Temporary powers become normal; the system becomes dependent on emergency mode.
- Time validates the emergency.
Emergency action is coherent only if active harm decreases, hidden debt decreases, boundaries are restored, recurrence risk falls, and emergency power recedes.
4. When This Law Applies
This law applies whenever a system invokes emergency authority, crisis response, extraordinary restriction, rapid containment, temporary override, escalated enforcement, exceptional monitoring, emergency governance, special access, expedited procedure, or suspension of ordinary protections.
It is especially important when:
- emergency power is activated;
- restrictions expand quickly;
- surveillance expands under crisis framing;
- normal review is bypassed;
- enforcement increases before repair;
- emergency powers lack expiration;
- crisis language continues after the crisis changes;
- exceptions become policy;
- temporary measures become infrastructure;
- public safety is used to justify indefinite control;
- AI systems deploy emergency restrictions or model behavior changes without review;
- security systems maintain heightened controls after incident closure;
- governance bodies normalize crisis powers;
- affected nodes cannot contest emergency continuation;
- legitimacy depends on whether the emergency response remains bounded.
The law applies strongly when:
temporary emergency controls remain after the emergency condition changesor when:
emergency power lacks scope, sunset, audit, restoration, or reviewTypical domains:
| Domain | Emergency Normalization Expression |
|---|---|
| AI systems | Emergency guardrails, bans, model restrictions, monitoring, or override modes require scope, audit, sunset, appeal, rollback, and restoration. |
| Cybersecurity | Incident containment must transition into repair, review, closure, and recurrence prevention rather than permanent emergency posture. |
| Institutions | Crisis policies should sunset, be reviewed, and repair the conditions that required emergency response. |
| Medicine / biology | Acute intervention can be necessary but should transition into recovery, restoration, and reduced emergency dependence. |
| Economy | Emergency economic controls, relief, freezes, or restrictions require sunset, restoration, and circulation repair. |
| Governance | Emergency powers require legal, procedural, moral, and legitimacy audit with time-bound review. |
| Culture | Crisis narratives can normalize fear, control, and taboo unless memory and repair restore balance. |
| Media / information networks | Emergency information controls require transparency, audit, correction, and sunset. |
5. When This Law Does Not Apply
This law should not be used to reject emergency action when active harm is occurring.
Emergency containment can be coherent.
The law says emergency action must be bounded and restoration-linked.
False-positive cases:
| Case | Why emergency action may be coherent |
|---|---|
| Active harm is ongoing | Immediate override may be needed to prevent collapse |
| Boundaries are actively failing | Temporary restriction may protect harmed nodes |
| Evidence is at risk | Emergency preservation may be required |
| A system is under active attack | Containment may precede full repair |
| Public danger is imminent | Rapid action may be valid when scoped and reviewed |
| Normal process is too slow for acute threat | Temporary bypass can be coherent if audited and sunsetted |
| Emergency power is already narrowing | Reduction may indicate restoration is working |
Important distinction:
Emergency power can be valid; emergency power becoming normal without repair is the failure.
6. Diagnostic Signature
Canonical diagnostic:
emergency Π - sunset - audit - ℛ ⇒ control normalization + H↑Warning signature:
emergency duration↑
scope expands
review weakens
sunset unclear
restoration linkage↓
control density↑
legitimacy↓
⇒ emergency normalizationCommon indicators:
| Diagnostic | Expected movement | Interpretation |
|---|---|---|
emergency_scope | explicit and bounded | Emergency authority must be clearly limited |
emergency_duration | bounded / decreasing | Duration should not drift indefinitely |
sunset_condition | defined | Termination or renewal threshold must be clear |
override_power | narrow and justified | Override should fit active threat |
control_density | should decrease after containment | Control should not ratchet upward permanently |
review_integrity | must remain intact | Emergency action must be inspected |
restoration_linkage | must ↑ | Emergency action must route into repair |
recurrence_reduction | must ↑ | Emergency response should reduce future crises |
force_debt | should be acknowledged and repaired | Coercion creates debt even if necessary |
crisis_framing | should update | Emergency language must not persist by inertia |
normalization_pressure | should ↓ | Temporary powers should not become ordinary |
BΣ | should stabilize | Boundaries should be restored, not permanently eroded |
Au / FI | must remain intact | Audit and feedback must remain possible |
L | stable / ↑ if valid | Legitimacy holds when emergency power is bounded |
H | ↑ if invalid | Hidden debt rises when emergency power normalizes |
Τ | required | Time validates sunset and recurrence reduction |
Additional diagnostics:
| Diagnostic | Use |
|---|---|
| Emergency Normalization | Detects temporary override becoming ordinary control |
| Emergency Scope | Tests whether the override is bounded |
| Emergency Sunset | Tests whether termination criteria exist |
| Override Drift | Detects scope or duration expansion |
| Control Density | Tracks growth of restriction and surveillance |
| Review Integrity | Tests whether emergency action remains auditable |
| Restoration Linkage | Tests whether emergency action routes into repair |
| Recurrence Reduction | Tests whether emergency response prevents future crisis |
| Force Debt | Tracks debt created by coercive emergency measures |
| Temporal Proof | Confirms emergency powers recede over time |
7. Failure Pattern
If ignored, this law allows crisis control to become ordinary system geometry.
General failure pathway:
emergency appears
→ override expands
→ visible order improves
→ sunset remains undefined
→ repair is delayed
→ review weakens
→ control becomes routine
→ emergency justification persists
→ hidden debt and legitimacy debt accumulateCommon failure modes:
- Emergency Normalization — emergency powers become ordinary governance.
- Temporary Override Drift — temporary exceptions persist or expand.
- Permanent Emergency — crisis framing becomes the system’s default state.
- Control Ratchet — control increases during crisis but does not reduce afterward.
- Sunset Failure — no clear termination, review, or narrowing condition exists.
- Audit Suppression — emergency authority shields itself from inspection.
- Review Failure — oversight becomes symbolic or absent.
- Emergency Scope Creep — emergency authority expands beyond original domain.
- Restoration Bypass — containment replaces repair.
- Force Debt Accumulation — coercive emergency action creates unrepaired debt.
- Legitimacy Debt — trust decays as exceptional power becomes normal.
- Normalization Shield — repeated emergency framing protects control from critique.
- Pseudo-Security — emergency control appears secure while coherence declines.
- Rights / Boundary Erosion — boundaries weakened during crisis fail to recover.
- Crisis Dependency — the system becomes unable to function without emergency powers.
Compact failure signature:
emergency_scope↑ + sunset absent + ℛ↓ ⇒ H↑ + L↓8. Restoration Implications
Restoration requires converting emergency control back into ordinary coherent governance through review, repair, and sunset.
The first restoration question is not:
Did the emergency action work?The first restoration question is:
Did the emergency action reduce active harm, repair the conditions that required it, restore boundaries, and terminate or narrow under audit?Restoration priorities:
- Identify the emergency claim.
- Classify the active harm or threat.
- Define emergency scope.
- Define sunset condition.
- Preserve auditability and review.
- Map force debt and boundary debt.
- Route emergency action into repair.
- Reduce recurrence conditions.
- Narrow or terminate emergency power.
- Time-validate restored coherence and legitimacy.
Relevant restoration arcs:
| Restoration Arc | Why it applies |
|---|---|
| Emergency Sunset Restoration | Restores termination and narrowing conditions |
| Override Scope Repair | Rebounds emergency authority to valid domain |
| Emergency Review | Audits decisions, costs, harms, and continuation claims |
| Control Ratchet Reversal | Reduces controls that persisted after crisis |
| Auditability Restoration | Restores traceability and oversight |
| Boundary Reconstitution | Repairs boundaries weakened during emergency |
| Force Debt Repair | Repairs debt created by coercive action |
| Restoration Linkage Repair | Connects emergency containment to restoration |
| Recurrence Prevention | Changes conditions that produced the emergency |
| Legitimacy Repair | Restores trust after emergency control |
| Governance Re-Sequencing | Reorders containment, repair, review, and ordinary governance |
| Temporal Validation | Confirms emergency powers recede and coherence holds |
Minimal restoration sequence:
identify emergency claim
→ Γ classify active threat and threshold
→ Σ define scope + sunset
→ preserve Au/FI/review
→ map force_debt + boundary_debt
→ perform ℛ
→ reduce recurrence
→ narrow / terminate override
→ validate L/O over ΤTemporal validation requirement:
active harm decreases
emergency scope narrows
sunset condition activates or is reviewed
auditability remains intact
restoration linkage improves
force debt decreases
boundary integrity recovers
control density decreases where no longer needed
recurrence risk decreases
legitimacy stabilizes over time9. Design Rule
Every emergency override must include scope, sunset, audit, restoration, review, and recurrence reduction.
Operational design requirements:
- Define emergency threshold.
- Define active harm.
- Define scope.
- Define affected nodes.
- Define duration.
- Define sunset condition.
- Preserve auditability.
- Preserve review.
- Preserve feedback integrity.
- Track force debt.
- Track boundary debt.
- Link containment to repair.
- Link emergency action to recurrence prevention.
- Require renewal only under audit.
- Reduce control after containment.
- Validate over time.
Avoid:
- emergency powers without expiration;
- crisis framing as permanent governance;
- emergency surveillance without sunset;
- temporary restrictions becoming default;
- bypassing review because the situation was urgent;
- force debt without repair;
- control increase without restoration increase;
- safety language without audit;
- emergency rule stacking;
- public reassurance without boundary restoration;
- AI emergency guardrails without review and rollback;
- incident containment without post-incident repair;
- treating continuing control as proof that the emergency still exists.
10. Cross-Scale Expressions
| Scale / Layer | Expression of the Law |
|---|---|
| U0 — Substrate | Acute intervention may preserve life or material coherence but must transition into repair and recovery. |
| U1 — Energy / capacity | Emergency mode consumes slack and cannot remain permanently active without debt. |
| U2 — Boundary / interface | Emergency actions often alter access, consent, privacy, movement, or coupling boundaries and must restore them. |
| U3 — Process / execution | Emergency processes require containment, review, repair, sunset, and recurrence prevention workflows. |
| U4 — Classification / claim | Emergency status must be classified and reclassified as conditions change. |
| U5 — Time / delay | Emergency legitimacy depends on duration, sunset, renewal criteria, and recurrence review. |
| U6 — Field effect | Outcomes reveal whether emergency action restored coherence or normalized control. |
| U7 — Recurrence / memory | Emergency lessons must become memory and prevention, not permanent crisis identity. |
| U8 — Environment / forcing | Institutions, platforms, AI systems, markets, media, and governance fields can reward permanent crisis framing. |
11. Examples
Example A — Temporary Access Control Becomes Permanent
Scenario:
After a breach, an organization imposes emergency access restrictions. Months later the restrictions remain, but root-cause repair, review, and user restoration never occurred.
Law expression:
emergency access restriction - ℛ - sunset ⇒ control normalizationInterpretation:
The emergency measure became ordinary control because it was not repair-linked and sunsetted.
Example B — AI Emergency Guardrail Drift
Scenario:
An AI system adds emergency refusals after a high-profile incident. The refusals remain broad, opaque, and unaudited after the risk context changes.
Law expression:
AI emergency restriction + Au↓ + sunset absent ⇒ pseudo-safetyInterpretation:
Emergency guardrails must be reviewed, scoped, corrected, and restored into ordinary governance.
Example C — Public Emergency Power
Scenario:
A governance system invokes emergency authority during crisis, then keeps expanded surveillance and enforcement powers after the crisis phase has passed.
Law expression:
crisis Π + no sunset ⇒ emergency normalization + L↓Interpretation:
Legitimacy decays when exceptional authority becomes ordinary.
Example D — Coherent Security Incident Response
Scenario:
A security team isolates systems during active attack, preserves evidence, patches root causes, audits the response, reviews restriction scope, restores access, and reduces recurrence.
Law expression:
containment → audit → ℛ → review → sunset ⇒ coherent emergency responseInterpretation:
Emergency containment is valid because it transitions into repair and termination.
Example E — Medical Acute Intervention
Scenario:
A strong acute intervention stabilizes a patient, but the system never transitions to recovery, root repair, monitoring, and capacity restoration.
Law expression:
acute stabilization - recovery ℛ ⇒ emergency dependencyInterpretation:
Emergency treatment must become restoration or the system remains crisis-dependent.
Example F — Emergency With Sunset
Scenario:
A platform temporarily increases monitoring during an active exploit campaign with explicit scope, public review window, user appeal, repair plan, rollback criteria, and recurrence-prevention metrics.
Law expression:
emergency sensing + Σ + Au + ℛ + sunset ⇒ L stableInterpretation:
The emergency response remains coherent because it is bounded, auditable, and repair-linked.
12. Relationship to Nearby Laws
| Related Law | Relationship |
|---|---|
| LAW-001 — Coherence Priority Law | Emergency action is valid only when coherence is preserved or restored |
| LAW-002 — Coherence Trajectory Law | Emergency response must improve trajectory, not freeze crisis mode |
| LAW-003 — Success Proxy Divergence Law | Visible order after emergency control may diverge from coherence |
| LAW-004 — Stability-Coherence Separation Law | Crisis control can produce stability without coherence |
| LAW-006 — Time Validation Law | Emergency authority requires time-bounded validation |
| LAW-009 — U4 / U6 Truth Law | Emergency claims require field validation |
| LAW-010 — Hidden Debt Accumulation Law | Permanent emergency creates hidden debt |
| LAW-011 — Hidden Debt Return Law | Unrepaired emergency debt returns through mistrust, bypass, or recurrence |
| LAW-012 — Error Lag Law | Emergency measures may mask errors until late |
| LAW-013 — Auditability-Debt Law | Emergency action without audit creates debt |
| LAW-015 — Suppressed Auditability Debt Law | Emergency opacity accelerates debt |
| LAW-016 — Inversion Formation Law | Protection can invert into ordinary control |
| LAW-017 — Silent Extraction Law | Emergency powers can silently extract slack, agency, or data |
| LAW-020 — Bandwidth Threshold Law | Emergencies may overload bandwidth and force simplification |
| LAW-023 — Restoration Capacity Load Law | Emergency response increases restoration load |
| LAW-024 — Latency–Gain Oscillation Law | Crisis response with high gain and delay can oscillate |
| LAW-030 — Slack Sovereignty Law | Permanent emergency consumes slack and sovereignty |
| LAW-031 — Observability Collapse Law | Crisis pressure can narrow observability |
| LAW-041 — Boundary Membrane Law | Emergency overrides alter membranes and must restore them |
| LAW-042 — Consent Structurality Law | Emergency consent and restriction must be scoped and restored |
| LAW-045 — Force Debt Law | Emergency force creates debt even when necessary |
| LAW-047 — Controlled Decoupling Law | Emergency decoupling must be controlled and repair-bound |
| LAW-048 — Feedback Integrity Law | Emergency action must preserve feedback and review |
| LAW-050 — Control-Restoration Separation Law | Emergency control must not replace restoration |
| LAW-052 — Stability Proof Law | Emergency response must survive audit and perturbation |
| LAW-057 — Deception Instability Law | Emergency narratives that hide real conditions become unstable |
| LAW-060 — Interface Legitimacy Law | Emergency interfaces require clarity and legitimacy |
| LAW-061 — Restoration Sequencing Law | Emergency containment is only one phase of restoration |
| LAW-064 — Restoration Debt Reduction Law | Emergency response must reduce debt |
| LAW-065 — Pseudo-Restoration Law | Emergency action can falsely appear restorative |
| LAW-066 — Restoration Capacity Sufficiency Law | Repair capacity must be sufficient to exit emergency mode |
| LAW-067 — Temporal Proof Law | Emergency powers require temporal proof and sunset |
| LAW-068 — Boundary-First Restoration Law | Emergency boundary protection may precede deeper repair |
| LAW-073 — Restoration Before Scaling Law | Emergency controls should not scale without restoration |
| LAW-075 — Capacity Before Demand Law | Emergency governance must not demand beyond affected-node capacity |
| LAW-083 — Normalization Shield Law | Normalized emergency power shields itself from critique |
| LAW-102 — Legitimacy Audit Law | Emergency legitimacy requires audit and affected-node acknowledgment |
| LAW-103 — Justice Stability Law | Emergency response must support justice, not replace it |
| LAW-104 — Justice Logistics Law | Emergency disclosure and enforcement require logistics |
| LAW-105 — Repair Before Enforcement Law | Emergency enforcement must lead to repair |
| LAW-106 — Exposure Legibility Law | Emergencies often reveal pre-existing debt |
| LAW-107 — Exposure Without Restoration Law | Emergency disclosure without restoration destabilizes |
| LAW-109 — High-Φ Legitimacy Scaling Law | High-impact emergency power requires proportional accountability |
| LAW-110 — Governance Sequencing Law | Emergency action must be sequenced into governance |
| LAW-111 — Meaning Audit Law | Emergency narratives are not audit-exempt |
| LAW-112 — Security as Sustained Coherence Law | Emergency power is valid only if security coherence holds |
| LAW-113 — Incident Lag Law | Late incidents can trigger overbroad emergency response |
| LAW-114 — Pseudo-Security Law | Normalized emergency control can become pseudo-security |
| LAW-115 — Surveillance–Restoration Law | Emergency surveillance must route into restoration and sunset |
| LAW-117 — Shadow–Light Security Law | Emergency response must not become shadow capture |
| LAW-118 — Empathy Security Law | Emergency classification improves when state estimation includes affected-node reality |
| LAW-119 — Basin Self-Defense Law | Basins can use emergency framing to defend attractor geometry |
| LAW-120 — Security Legibility Law | Emergency security claims require traceability |
| LAW-124 — AI Rule-Stacking Law | Emergency AI rules can compound audit complexity |
| LAW-127 — AI Decision Pipeline Law | Emergency AI execution still requires Light and valid refusal paths |
| LAW-131 — Cognitive Infrastructure Scaling Law | Emergency controls over cognition require proportional governance |
| LAW-132 — AI Legitimacy Function Law | AI emergency powers require accountability, audit, repair, and transparency |
| LAW-134 — Layered Interception Law | Layered safeguards reduce need for broad emergency override |
| LAW-135 — Guardrail Belief-Sculpting Law | Emergency guardrails can sculpt belief and require audit |
| LAW-136 — Invisible Constraint Amplification Law | Invisible emergency constraints gain power when hidden |
Aliases folded into this law:
- Emergency Normalization Law
- Emergency Power Normalization Law
- Emergency Override Sunset Law
- Emergency Control Debt Law
- Temporary Override Drift Law
- Crisis Power Drift Law
- Emergency Must Sunset Law
Deduplication note:
This law should remain the root emergency-normalization law. LAW-105 defines repair before enforcement. LAW-110 defines governance sequencing. LAW-115 defines surveillance-to-restoration routing. LAW-116 specializes temporary emergency power and crisis override drift. LAW-124 specializes AI rule-stacking drift when emergency rules accumulate without auditability.
13. Operator Mapping
| Operator | Role in this law |
|---|---|
Γ | Classifies emergency threshold, active harm, scope, continuation, exit condition, debt, and recurrence risk |
Π | Operationalizes emergency controls, overrides, restrictions, surveillance, review, repair, and sunset mechanisms |
Ξ | Captures inversion when emergency language justifies permanent control |
⊗ | Emergency action alters couplings, access, authority, and decoupling pathways |
ℛ | Repairs harm, force debt, boundary debt, and origin conditions so emergency mode can end |
Τ | Validates sunset, narrowing, recurrence reduction, and restored coherence over time |
Θ | Prevents crisis certainty, power ratchet, and emergency self-certification |
Σ | Defines scope, jurisdiction, duration, limits, and affected domain of emergency action |
Ψ | Field and affected-node feedback validates emergency effects |
Λ | Tests compatibility between emergency response and whole-system coherence |
Coherent operator sequence:
acute threat appears
→ Θ prevent emergency overreach
→ Γ classify threshold / active harm / containment need
→ Σ define scope, duration, and sunset
→ Π execute narrow override if required
→ Au/FI/review preserve corrigibility
→ ℛ repair harm, force debt, and origin conditions
→ Ψ validate affected-node effects
→ Τ validate sunset, recurrence reduction, and L recoveryInverted operator sequence:
crisis appears
→ emergency Π expands
→ visible order improves
→ sunset remains unclear
→ review weakens
→ ℛ lags
→ control becomes routine
→ crisis framing persists
→ H↑
→ Ξ / ι↑
→ L↓14. Machine-Readable Summary
id: "LAW-116"
name: "Emergency Normalization Law"
type: "law"
status: "draft"
family:
- "Security Laws"
summary: "Emergency power without sunset becomes ordinary control; emergency override must remain scoped, audited, time-bounded, restoration-linked, and recurrence-reducing."
canonical_statement: "Emergency power without sunset becomes ordinary control."
core_form: "emergency power without sunset becomes ordinary control"
emergency_valid_form: "emergency override valid ⇔ Σ scoped + Τ sunset + Au intact + ℛ linked + review active"
failure_form: "emergency Π - sunset - audit - ℛ ⇒ control normalization + H↑"
control_ratchet_form: "temporary override + recurrence of crisis framing ⇒ control ratchet↑"
restoration_form: "emergency containment → repair → review → sunset → recurrence prevention"
restoration_valid_contrast: "emergency authority coherent when it reduces active harm, restores boundaries, repairs debt, and terminates or narrows over Τ"
variables:
primary:
- "emergency_scope"
- "emergency_duration"
- "sunset_condition"
- "override_power"
- "control_density"
- "review_integrity"
- "restoration_linkage"
- "recurrence_reduction"
- "force_debt"
- "crisis_framing"
- "normalization_pressure"
- "BΣ"
- "Au"
- "Au_eff"
- "R"
- "R_eff"
- "FI"
- "L"
- "H"
secondary:
- "O"
- "H_security"
- "ε"
- "ι"
- "µᵢ"
- "K"
- "σ"
- "𝓑"
- "𝓓"
- "Φ"
- "Λ"
- "⊗"
- "Γ"
- "Π"
- "Ξ"
- "ℛ"
- "Θ"
- "Σ"
- "Ψ"
- "Τ"
- "MS"
diagnostics:
- "Emergency Normalization"
- "Emergency Scope"
- "Emergency Sunset"
- "Override Drift"
- "Control Density"
- "Auditability"
- "Restoration Linkage"
- "Review Integrity"
- "Recurrence Reduction"
- "Boundary Integrity"
- "Force Debt"
- "Legitimacy Debt"
- "Hidden Debt"
- "Temporal Proof"
failure_modes:
- "Emergency Normalization"
- "Temporary Override Drift"
- "Permanent Emergency"
- "Control Ratchet"
- "Sunset Failure"
- "Audit Suppression"
- "Review Failure"
- "Emergency Scope Creep"
- "Restoration Bypass"
- "Force Debt Accumulation"
- "Legitimacy Debt"
- "Normalization Shield"
- "Pseudo-Security"
- "Rights / Boundary Erosion"
- "Crisis Dependency"
restoration_arcs:
- "Emergency Sunset Restoration"
- "Override Scope Repair"
- "Emergency Review"
- "Control Ratchet Reversal"
- "Auditability Restoration"
- "Boundary Reconstitution"
- "Force Debt Repair"
- "Restoration Linkage Repair"
- "Recurrence Prevention"
- "Legitimacy Repair"
- "Governance Re-Sequencing"
- "Temporal Validation"
related_laws:
- "LAW-001"
- "LAW-002"
- "LAW-003"
- "LAW-004"
- "LAW-006"
- "LAW-009"
- "LAW-010"
- "LAW-011"
- "LAW-012"
- "LAW-013"
- "LAW-015"
- "LAW-016"
- "LAW-017"
- "LAW-020"
- "LAW-023"
- "LAW-024"
- "LAW-030"
- "LAW-031"
- "LAW-041"
- "LAW-042"
- "LAW-045"
- "LAW-047"
- "LAW-048"
- "LAW-050"
- "LAW-052"
- "LAW-057"
- "LAW-060"
- "LAW-061"
- "LAW-064"
- "LAW-065"
- "LAW-066"
- "LAW-067"
- "LAW-068"
- "LAW-073"
- "LAW-075"
- "LAW-083"
- "LAW-102"
- "LAW-103"
- "LAW-104"
- "LAW-105"
- "LAW-106"
- "LAW-107"
- "LAW-109"
- "LAW-110"
- "LAW-111"
- "LAW-112"
- "LAW-113"
- "LAW-114"
- "LAW-115"
- "LAW-117"
- "LAW-118"
- "LAW-119"
- "LAW-120"
- "LAW-124"
- "LAW-127"
- "LAW-131"
- "LAW-132"
- "LAW-134"
- "LAW-135"
- "LAW-136"
related_invariants:
- "INV-001"
- "INV-002"
- "INV-006"
- "INV-073"
- "INV-080"
operator_sequence:
coherent:
- "acute threat appears"
- "Θ prevent emergency overreach"
- "Γ classify threshold / active harm / containment need"
- "Σ define scope, duration, and sunset"
- "Π execute narrow override if required"
- "Au/FI/review preserve corrigibility"
- "ℛ repair harm, force debt, and origin conditions"
- "Ψ validate affected-node effects"
- "Τ validate sunset, recurrence reduction, and L recovery"
inverted:
- "crisis appears"
- "emergency Π expands"
- "visible order improves"
- "sunset remains unclear"
- "review weakens"
- "ℛ lags"
- "control becomes routine"
- "crisis framing persists"
- "H↑"
- "Ξ / ι↑"
- "L↓"
aliases:
- "Emergency Normalization Law"
- "Emergency Power Normalization Law"
- "Emergency Override Sunset Law"
- "Emergency Control Debt Law"
- "Temporary Override Drift Law"
- "Crisis Power Drift Law"
- "Emergency Must Sunset Law"
deduplication_note: "Root emergency-normalization law. LAW-105 defines repair before enforcement. LAW-110 defines governance sequencing. LAW-115 defines surveillance-to-restoration routing. LAW-116 specializes temporary emergency power and crisis override drift. LAW-124 specializes AI rule-stacking drift when emergency rules accumulate without auditability."
source: "content/archive/laws/technical.md"15. Compact Card Version
LAW-116 — Emergency Normalization Law
Emergency power without sunset becomes ordinary control.
Core form:
emergency power without sunset becomes ordinary controlEmergency-valid form:
emergency override valid ⇔ Σ scoped + Τ sunset + Au intact + ℛ linked + review activePlain meaning:
Emergency power can be necessary to stop active harm, preserve critical coherence, contain unsafe coupling, or create a repair window. But if emergency authority lacks scope, sunset, audit, restoration, review, and recurrence reduction, it drifts into ordinary control.
Failure form:
emergency Π - sunset - audit - ℛ ⇒ control normalization + H↑Restoration form:
emergency containment → repair → review → sunset → recurrence preventionPrimary variables:
emergency_scope, emergency_duration, sunset_condition, override_power, control_density, review_integrity, restoration_linkage, recurrence_reduction, force_debt, crisis_framing, normalization_pressure, BΣ, Au, Au_eff, R, R_eff, FI, L, H, Γ, Π, Ξ, ℛ, Θ, Σ, Ψ, Τ
Diagnostic signature:
Emergency duration increases, scope expands, review weakens, sunset remains unclear, restoration linkage falls, control density rises, and legitimacy declines. This indicates emergency normalization.
Failure risk:
Emergency normalization, temporary override drift, permanent emergency, control ratchet, sunset failure, audit suppression, review failure, emergency scope creep, restoration bypass, force debt accumulation, legitimacy debt, normalization shield, pseudo-security, rights or boundary erosion, crisis dependency.
Restoration priority:
Identify the emergency claim, classify active threat and threshold, define scope and sunset, preserve auditability and review, map force and boundary debt, connect containment to repair, reduce recurrence conditions, narrow or terminate emergency power, and validate legitimacy and coherence over time.