schema_version: "1.0"

id: "FM-ISC-003"

title: "FM-ISC-003 — Urgency Substitution"

slug: "fm-isc-003-urgency-substitution"

type: "failure_mode"

status: "draft"

version: "0.1.0"

last_updated: "2026-06-19"

summary: "Urgency Substitution occurs when immediacy, pressure, speed, escalation, crisis framing, deadline force, emotional intensity, or response velocity substitutes for correct signal classification, consent, sequencing, repair validity, context, proportionality, or coherence."

canonical_url: "/archive/failure-modes/registry/interactions-signals-couplings/fm-isc-003-urgency-substitution"

citation_id: "FM-ISC-003-v0-1-0"

canon:

tier: "registry"

state: "draft"

source: "UTS — Failure Modes Registry"

source_id: "FM-ISC-003"

classification:

family: "failure-modes"

module: "interactions-signals-couplings"

module_group: "isc"

density: "advanced-reference"

audience:

• "UTS readers"
• "interaction researchers"
• "signal systems researchers"
• "cybernetics researchers"
• "AI alignment researchers"
• "interface researchers"
• "restoration researchers"
• "justice researchers"
• "coherence researchers"
• "machine readers"

tags:

• "failure-modes"
• "isc"
• "interactions"
• "signals"
• "couplings"
• "urgency-substitution"
• "fm-isc-003-urgency-substitution"
• "urgency"
• "crisis-framing"
• "sequencing"
• "signal-misclassification"
• "consent"
• "coherence"

aliases:

• "Urgency Substitution"
• "Urgency Override"
• "Crisis Substitution"
• "Speed Over Coherence"
• "Immediacy Substitution"
• "Deadline Capture"
• "Pressure-Based Coupling"
• "Crisis-Framed Misrouting"
• "Velocity Substitution"
• "Urgency-as-Validity"

related:

laws:

• "Urgency Must Not Substitute for Coherence"
• "Speed Must Not Override Signal Classification"
• "Crisis Framing Must Remain Auditable"
• "Consent Must Survive Urgency"
• "Sequencing Must Survive Pressure"
• "Emergency Action Requires Restoration Path"
• "Choice Under Clarity"
• "Signal Misclassification"
• "Hidden Debt Accumulation"
• "Temporal Audit Asymmetry"
• "False Calm"
• "Pseudo-Coherence"

invariants:

• "Urgency Requires Classification"
• "Pressure Must Preserve Consent Validity"
• "Fast Response Must Remain Reversible Where Possible"
• "Emergency Action Must Preserve Auditability"
• "Urgency Must Not Erase Context"
• "Crisis Framing Must Not Create False Authority"
• "Velocity Must Remain Subordinate to Coherence"

operators:

• "Τ — Trajectory / Time"
• "D — Damping"
• "Ψ — Observation / Interface"
• "Γ — Selection"
• "Au — Auditability"
• "BΣ — Boundary Integrity"
• "K — Constraint / Load"
• "O — Coherence"
• "H — Hidden Debt"
• "Λ — Compatibility"
• "R — Restoration Capacity"
• "Φ — Flow / Resource Movement"
• "G — Gain"

gates:

• "Urgency Classification Gate"
• "Sequencing Gate"
• "Consent Gate"
• "Context Gate"
• "Proportionality Gate"
• "Auditability Gate"
• "Reversibility Gate"
• "Emergency Authority Gate"
• "Local Coherence Gate"

diagnostics:

• "Urgency Validity"
• "Signal / Urgency Fit"
• "Sequencing Integrity"
• "Consent Preservation"
• "Context Completeness"
• "Proportionality"
• "Reversibility"
• "Hidden Debt"
• "Auditability"
• "Local Coherence"

failure_modes:

• "FM-ISC-002 — Signal Misclassification"
• "FM-ISC-001 — Identity-Binding Signal Capture"
• "FM-ECO-016 — Urgency Substitution"
• "FM-ECO-012 — Late Delivery"
• "FM-ECO-013 — Conditional Coercive Delivery"
• "FM-C-008 — Over-Damped Brittleness"
• "FM-C-011 — Zero-Slack Collapse"
• "FM-C-019 — Emergency Override Drift"
• "FM-CORE-002 — Hidden Debt Accumulation"
• "FM-CORE-006 — U4 Truth Substitution"
• "FM-JC-007 — Manufactured Consent"
• "FM-R-005 — Stabilization Freeze"

restoration_arcs:

• "Urgency Classification Audit"
• "Sequencing Restoration"
• "Consent Revalidation"
• "Context Re-expansion"
• "Proportionality Recalibration"
• "Emergency Authority Review"
• "Reversibility Restoration"
• "Hidden Urgency Debt Accounting"
• "Repair Path Reattachment"
• "Local Coherence Restoration"

modules:

• "Interactions / Signals / Couplings"
• "Cybernetics"
• "Interfaces"
• "AI Governance"
• "Justice"
• "Restoration"
• "Economy"
• "Diagnostics"
• "Coherence"

navigation:

order: 1503

parent: "failure-modes"

visible: true

provenance:

created_from: "failure-mode-registry-production"

source_thread: "UTS Failure Modes Registry production"

source_file: "content/archive/failure-modes/registry/interactions-signals-couplings/fm-isc-003-urgency-substitution.md"

notes: "Expanded from ISC family list entry and aligned to normalized metadata structure. Distinct from FM-ECO-016 as the general interaction/signal/coupling form; FM-ECO-016 is the economy-specific expression. This entry focuses on urgency, crisis framing, speed, deadlines, pressure, or escalation substituting for signal classification, consent, sequencing, proportionality, auditability, or coherent response."

entry:

failure_mode_id: "FM-ISC-003"

failure_family: "Interactions / Signals / Couplings"

production_treatment: "General Interaction Entry"

domain_specific_expressions:

• "FM-ECO-016 — Urgency Substitution"

parent_modes:

• "FM-ISC-002 — Signal Misclassification"
• "FM-CORE-006 — U4 Truth Substitution"
• "FM-CORE-002 — Hidden Debt Accumulation"
• "FM-C-019 — Emergency Override Drift"
• "FM-JC-007 — Manufactured Consent"

first_gate_failure: "Urgency Classification Gate"

primary_hidden_debt: "Hidden debt accumulates when urgency compresses classification, consent, context, sequencing, or auditability, causing fast action to create unresolved burden, coercion, misrouting, or future repair debt."

primary_inversion: "Urgency becomes validity; the system treats pressure, speed, deadline, intensity, escalation, or crisis framing as proof that the action is correct, necessary, or allowed."

primary_boundary_pattern: "The boundary between urgent timing and valid response collapses; immediacy is allowed to override signal classification, consent, proportionality, or repair sequencing."

primary_signature: "Pressure rises; classification narrows; consent/context checks are bypassed; response accelerates; mismatch or coercion appears; hidden debt accumulates beneath speed."

FM-ISC-003 — Urgency Substitution

Status: Draft

Archive Type: Failure Mode

System: Universal Theory Stack

Parent: Failure Modes

Canon Tier: Registry

Registry: Failure Modes Registry

Entry ID: FM-ISC-003

Family: Interactions / Signals / Couplings

Production Treatment: General Interaction Entry

Domain-Specific Expression: FM-ECO-016 — Urgency Substitution

Parent Modes: FM-ISC-002 — Signal Misclassification; FM-CORE-006 — U4 Truth Substitution; FM-CORE-002 — Hidden Debt Accumulation; FM-C-019 — Emergency Override Drift; FM-JC-007 — Manufactured Consent

0. Interaction Scope Note

This entry is conceptual and systems-oriented.

It does not treat urgency, speed, emergency response, rapid coordination, deadline awareness, escalation, triage, crisis action, immediate protection, or fast repair as inherently failed.

Some conditions are genuinely urgent.

Some systems must act quickly to preserve life, prevent harm, protect boundaries, or stop cascading failure.

Urgency can preserve coherence when it is:

• correctly classified
• proportionate
• time-bounded
• consent-aware where possible
• context-aware
• reversible where feasible
• auditable
• tied to real risk
• not used to bypass responsibility
• followed by repair
• followed by review
• not treated as permanent authority
• compatible with affected-node protection

The failure begins when urgency substitutes for validity.

The issue is not speed.

The issue is pressure being treated as proof.

Urgency Substitution occurs when the demand to act quickly replaces the work of determining whether the action is coherent.

1. Definition

Urgency Substitution occurs when immediacy, pressure, speed, escalation, crisis framing, deadline force, emotional intensity, or response velocity substitutes for correct signal classification, consent, sequencing, repair validity, context, proportionality, or coherence.

The substituting urgency may appear as:

• deadline pressure
• crisis language
• emergency framing
• “act now” demands
• escalation pressure
• emotional intensity
• reputational urgency
• political urgency
• economic urgency
• relational urgency
• operational urgency
• security urgency
• compliance urgency
• delivery urgency
• triage urgency
• scarcity urgency
• emergency authority
• platform response velocity
• AI refusal velocity
• user-support escalation
• rapid settlement pressure
• forced decision windows
• time-boxed consent
• “no time to explain”
• “we need alignment now”

The core failure is:

urgency↑
classification↓
consent/context↓
response velocity↑
coherence↓
H↑

Urgency Substitution is not acting fast.

It is acting as if fastness itself validates the action.

2. Core Pattern

The core pattern is:

1. A signal, need, risk, demand, conflict, or opportunity appears.
2. Urgency rises.
3. The system compresses classification, consent, context, sequencing, and audit.
4. Response is selected according to pressure rather than validated fit.
5. The response may appear decisive, protective, efficient, or responsible.
6. Mismatch, coercion, misrouting, or repair debt appears downstream.
7. The system cites urgency as justification.
8. Hidden debt accumulates because the action cannot be fully inspected or repaired in time.
9. Restoration requires reopening classification and repairing debt created by urgency.

This failure often appears as:

we had to act quickly

while the hidden truth may be:

speed does not prove the action matched the signal

or:

there was no time for process

while the overlooked condition is:

there still needed to be enough classification to avoid incoherent action

The restorative question is:

what did urgency allow the system to skip, and what debt did that create?

Urgency Substitution turns time pressure into authority.

3. Failure Signature

Typical signature:

pressure↑
classification compression↑
consent bypass↑
context loss↑
fast response↑
misfit / debt↑
H↑

Extended signature:

deadline replaces consent
crisis label replaces evidence
speed replaces sequencing
escalation replaces classification
emotional intensity replaces proportionality
emergency authority replaces accountability
rapid closure replaces repair validation

Common forms include:

a team forces agreement because a deadline is near
an organization labels dissent as obstruction during crisis
a platform rapidly enforces policy without context review
an AI system refuses or redirects quickly without classifying user intent correctly
a security team bypasses audit and never reconstructs the decision chain
a justice process pressures settlement because closure is urgent
a company cuts support because cost urgency dominates repair
a relationship demands immediate reassurance instead of allowing boundary clarification
a public institution invokes emergency to bypass consent and then normalizes the bypass

The defining condition is not that response is fast.

The defining condition is that speed or pressure replaces the validation needed to make the response coherent.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: stronger nodes use urgency to override slower consent, repair, or audit pathways.
• U2 — Configuration / Boundaries: emergency pathways lack sufficient gates or expiration.
• U3 — Execution / Runtime: operational routines prioritize velocity over classification.
• U4 — Information / Truth: urgency framing substitutes for signal truth.
• U5 — Coordination / Time: primary layer; time pressure compresses sequencing and review.
• U6 — Coherence Field: crisis intensity creates felt legitimacy.
• U7 — Memory / Recurrence: previous emergency patterns normalize urgency overrides.
• U8 — Environment / Field: external markets, politics, platforms, or institutions reward fast visible response.

Common manifestation layers:

• U2 — Boundaries: emergency exceptions override normal gates.
• U3 — Execution: response accelerates.
• U4 — Truth: urgency becomes justification.
• U5 — Time: sequencing collapses.
• U6 — Field: urgency aura suppresses challenge.
• U7 — Memory: urgency pathways repeat.

Urgency Substitution is primarily a U5 temporal compression / U4 justification failure.

The system lets time pressure decide what classification, consent, or repair cannot safely decide.

5. Typical Development Sequence

A common development sequence is:

1. A signal appears under time pressure.
2. The system experiences rising urgency.
3. The system narrows the option space.
4. Classification is simplified.
5. Consent, context, sequencing, or auditability is treated as too slow.
6. The system acts quickly.
7. The action produces secondary burden.
8. The system defends the action by citing urgency.
9. The skipped gates are not reconstructed.
10. Urgency debt becomes hidden debt.
11. The exception becomes easier to reuse.

The loop often looks like:

pressure → skipped gates → fast action → hidden debt → future pressure

Another common loop is:

urgency justifies bypass → bypass creates harm → harm creates more urgency → bypass repeats

Urgency Substitution becomes self-reinforcing when the debt created by rushed action generates the next crisis.

6. Diagnostic Markers

Diagnostic markers include:

• “No time” is used to bypass classification, consent, or audit.
• Deadline pressure forces agreement.
• Emergency framing persists after emergency conditions end.
• Crisis language prevents contextual review.
• The system cannot explain what signal class justified the response.
• Fast response produces recurring repair debt.
• Affected nodes are pressured to accept terms immediately.
• Boundary or constraint signals are overridden because urgency is invoked.
• Response speed is celebrated even when mismatch appears.
• Post-action review is absent.
• Emergency powers become normalized.
• Restoration improves when urgency is classified separately from validity.

Useful diagnostics:

• Urgency Validity: Tests whether urgency is real, inflated, or manufactured.
• Signal / Urgency Fit: Determines whether the signal actually requires rapid response.
• Sequencing Integrity: Tests whether necessary order was preserved.
• Consent Preservation: Determines whether consent remained valid under pressure.
• Context Completeness: Measures context lost due to speed.
• Proportionality: Tests whether response scale matched risk and time window.
• Reversibility: Determines whether rushed actions can be undone or repaired.
• Hidden Debt: Tracks burden created by bypassed gates.
• Auditability: Reconstructs urgency decisions.
• Local Coherence: Tests whether fast action improved real conditions.

7. Related Gates

Relevant gates include:

• Urgency Classification Gate: Fails when urgency is accepted before being classified.
• Sequencing Gate: Fails when steps occur out of coherence order.
• Consent Gate: Fails when pressure invalidates consent.
• Context Gate: Fails when relevant conditions are skipped.
• Proportionality Gate: Fails when urgency inflates response beyond fit.
• Auditability Gate: Fails when fast action leaves no trace.
• Reversibility Gate: Fails when irreversible action is rushed without sufficient validation.
• Emergency Authority Gate: Fails when emergency powers lack limit, review, or expiration.
• Local Coherence Gate: Fails when fast response worsens the field.

The first common gate failure is usually the Urgency Classification Gate.

The system treats urgency as self-evident rather than signal-classified.

8. Related Operators

Relevant operators include:

• Τ — Trajectory / Time: Primary operator; urgency compresses available time and sequence.
• D — Damping: Should regulate urgency; may collapse under pressure.
• Ψ — Observation / Interface: Frames the condition as crisis, deadline, or emergency.
• Γ — Selection: Selects rapid response pathway.
• Au — Auditability: Must preserve decision trace under speed.
• BΣ — Boundary Integrity: Protects consent, boundary, and role boundaries under urgency.
• K — Constraint / Load: Rises when rushed response shifts burden.
• O — Coherence: May appear high through decisive action.
• H — Hidden Debt: Accumulates through skipped gates and rushed mismatch.
• Λ — Compatibility: Tests whether response fits signal and context.
• R — Restoration Capacity: Repairs urgency-created debt.
• Φ — Flow / Resource Movement: Routes resources or force under urgency.
• G — Gain: Incentivizes urgent framing where speed benefits power or optics.

Common operator pattern:

signal appears
Ψ frames urgency
Τ compresses sequence
D fails to slow classification
Γ selects fast response
BΣ consent / boundary checks weaken
Au decision trace drops
O appears improved through action
H accumulates

The core operator inversion is:

urgent → valid

instead of:

urgent + correctly classified + proportionate + consent-aware + auditable → valid fast action

Urgency Substitution turns temporal pressure into proof.

9. Related Laws and Invariants

Related Laws

• Urgency Must Not Substitute for Coherence: speed cannot validate action alone.
• Speed Must Not Override Signal Classification: fast response still requires signal typing.
• Crisis Framing Must Remain Auditable: emergency labels require inspection.
• Consent Must Survive Urgency: pressure can invalidate apparent agreement.
• Sequencing Must Survive Pressure: order matters even in time compression.
• Emergency Action Requires Restoration Path: bypassed gates create repair obligations.
• Choice Under Clarity: pressured choice may lack clarity.
• Signal Misclassification: urgency can misclassify signal type.
• Hidden Debt Accumulation: skipped gates store future burden.
• Temporal Audit Asymmetry: rushed decisions become harder to audit later.
• False Calm: rapid stabilization may hide unresolved debt.
• Pseudo-Coherence: decisive action can mimic coherence.

Related Invariants

• Urgency Requires Classification: urgency itself is a signal requiring validation.
• Pressure Must Preserve Consent Validity: agreement under pressure must be checked.
• Fast Response Must Remain Reversible Where Possible: reversibility protects coherence.
• Emergency Action Must Preserve Auditability: speed cannot erase the decision chain.
• Urgency Must Not Erase Context: compressed time still requires sufficient context.
• Crisis Framing Must Not Create False Authority: emergency labels do not grant unlimited legitimacy.
• Velocity Must Remain Subordinate to Coherence: response speed serves coherence, not the reverse.

10. Common False Positives

Not every urgent action is Urgency Substitution.

Common false positives include:

• Emergency response with valid risk classification.
• Rapid action that protects affected nodes.
• Time-sensitive action with post-action audit.
• Fast response that remains proportionate and reversible.
• Deadline action with free and informed consent.
• Crisis triage that preserves later repair.
• Emergency authority with clear expiration and review.
• Rapid refusal where the signal is correctly classified as harmful or unsafe.
• Fast security response followed by reconstruction and remediation.
• Immediate boundary enforcement against real threat.
• Temporary bypass paired with hidden-debt accounting.
• Urgent repair that reduces burden without suppressing context.

Clarifying rule:

This is not Urgency Substitution unless urgency, pressure, speed, deadline, crisis framing, or escalation substitutes for signal classification, consent, sequencing, proportionality, context, auditability, or coherence.

11. Common False Repairs

Common false repairs include:

• apologizing for urgency while preserving bypass effects
• adding faster review instead of better classification
• creating emergency templates with weak gates
• saying “next time we will communicate better” without restoring consent
• treating deadline pressure as unavoidable
• performing post-action justification instead of audit
• reclassifying coercion as necessary speed
• making emergency pathways permanent
• increasing urgency training without proportionality gates
• adding escalation channels that intensify pressure
• using rapid response dashboards as proof of coherence
• reversing only visible harm while keeping hidden debt
• asking affected nodes to accept decisions because “there was no time”
• turning urgency-created damage into ordinary repair backlog
• treating speed as accountability

False repair often produces the loop:

urgency bypass exposed → emergency process improved → bypass remains available

Another common loop is:

rushed action creates debt → debt creates crisis → crisis justifies more rushed action

The repair fails because it improves the speed pathway without restoring classification, consent, or auditability.

12. Restoration Direction

Restoration requires classifying urgency as a signal, restoring skipped gates where possible, auditing emergency action, repairing urgency-created debt, and preventing urgency from becoming standing authority.

Primary restoration direction:

classify urgency,
restore skipped gates,
audit rushed action,
and repair urgency-created debt

A fuller restoration path includes:

1. Name the urgent frame. Identify the deadline, crisis, pressure, escalation, threat, or time limit.
2. Name the signal. Identify what condition was interpreted as urgent.
3. Classify urgency. Determine whether urgency was real, inflated, manufactured, inherited, or misrouted.
4. Map skipped gates. Identify what classification, consent, context, audit, or sequencing was bypassed.
5. Audit decision chain. Reconstruct who decided, under what information, and with what authority.
6. Check proportionality. Determine whether response matched risk and time window.
7. Revalidate consent. Confirm whether affected-node agreement was valid under pressure.
8. Restore context. Reopen information compressed by urgency.
9. Reverse where possible. Undo rushed actions that lacked valid grounding.
10. Repair urgency debt. Address harms, burdens, coercion, or misrouting created by the bypass.
11. Install emergency review. Require post-action audit and expiration.
12. Protect boundaries under pressure. Prevent urgency from overriding valid limits.
13. Add slow-path triggers. Require slowing when classification uncertainty is high.
14. Prevent recurrence. Block urgency from satisfying coherence gates by itself.

A valid restoration path should reduce:

urgency inflation
classification compression
consent invalidity
context loss
sequencing collapse
emergency-authority drift
urgency-created hidden debt
H

Urgency Substitution is not repaired by acting slower in every case.

It is repaired by making speed answerable to coherence.

13. Cross-Module Links

• Interactions / Signals / Couplings: Core ISC failure where urgency distorts signal classification and response coupling.
• Cybernetics: Crisis framing can destabilize feedback loops and compress corrective pathways.
• Interfaces: Interfaces can force rapid decisions, time-box consent, escalate pressure, or hide slow-path alternatives.
• AI Governance: AI systems may over-refuse, over-escalate, or rapidly misroute users under safety urgency without context classification or redress.
• Justice: Settlement, testimony, consent, and compliance under deadline pressure can be invalid or coercive.
• Restoration: Urgent action must include post-action repair, audit, and hidden-debt accounting.
• Economy: FM-ECO-016 expresses this failure in delivery, markets, contracts, budgets, and institutional urgency.
• Diagnostics: Requires urgency validity, sequencing integrity, consent preservation, proportionality, and hidden-debt diagnostics.
• Coherence: Coherence requires that urgency alter timing without replacing truth, consent, or fit.

14. Relationship to Parent / Child Modes

Production treatment: General Interaction Entry

This mode maps upward to:

• FM-ISC-002 — Signal Misclassification
• FM-CORE-006 — U4 Truth Substitution
• FM-CORE-002 — Hidden Debt Accumulation
• FM-C-019 — Emergency Override Drift
• FM-JC-007 — Manufactured Consent

Domain-specific expression:

• FM-ECO-016 — Urgency Substitution

Sibling or related ISC modes include:

• FM-ISC-001 — Identity-Binding Signal Capture
• FM-ISC-002 — Signal Misclassification
• FM-ISC-014 — Reflection Without Integration

Related cross-family modes include:

• FM-ECO-016 — Urgency Substitution
• FM-ECO-012 — Late Delivery
• FM-ECO-013 — Conditional Coercive Delivery
• FM-C-008 — Over-Damped Brittleness
• FM-C-011 — Zero-Slack Collapse
• FM-C-019 — Emergency Override Drift
• FM-CORE-002 — Hidden Debt Accumulation
• FM-CORE-006 — U4 Truth Substitution
• FM-JC-007 — Manufactured Consent
• FM-JC-012 — Silence Misread as Stability
• FM-R-005 — Stabilization Freeze
• FM-AIX-012 — Guardrail Meaning Compression

Aliases preserved from source material:

• Urgency Substitution
• Urgency Override
• Crisis Substitution
• Speed Over Coherence
• Immediacy Substitution
• Deadline Capture
• Pressure-Based Coupling
• Crisis-Framed Misrouting
• Velocity Substitution
• Urgency-as-Validity

15. Minimal Entry Version

Definition: Urgency Substitution occurs when immediacy, pressure, speed, escalation, crisis framing, deadline force, emotional intensity, or response velocity substitutes for correct signal classification, consent, sequencing, repair validity, context, proportionality, or coherence.

Signature:

pressure↑
classification compression↑
consent bypass↑
context loss↑
fast response↑
misfit / debt↑
H↑

Restoration direction:

• name the urgent frame
• name the signal
• classify urgency
• map skipped gates
• audit decision chain
• check proportionality
• revalidate consent
• restore context
• reverse where possible
• repair urgency debt
• install emergency review
• protect boundaries under pressure
• add slow-path triggers
• prevent recurrence

16. Machine-Readable Summary

failure_mode:
  id: "FM-ISC-003"
  name: "Urgency Substitution"
  family: "Interactions / Signals / Couplings"
  production_treatment: "General Interaction Entry"
  domain_specific_expressions:
    - "FM-ECO-016 — Urgency Substitution"
  parent_modes:
    - "FM-ISC-002 — Signal Misclassification"
    - "FM-CORE-006 — U4 Truth Substitution"
    - "FM-CORE-002 — Hidden Debt Accumulation"
    - "FM-C-019 — Emergency Override Drift"
    - "FM-JC-007 — Manufactured Consent"
  primary_failure: "Urgency, pressure, speed, deadline, crisis framing, or escalation substitutes for signal classification, consent, sequencing, proportionality, context, auditability, or coherence."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ISC-003"
  scope_note: "Conceptual and systems-oriented; does not treat urgency, speed, emergency response, rapid coordination, deadline awareness, escalation, triage, crisis action, immediate protection, or fast repair as inherently failed."
  aliases:
    - "Urgency Substitution"
    - "Urgency Override"
    - "Crisis Substitution"
    - "Speed Over Coherence"
    - "Immediacy Substitution"
    - "Deadline Capture"
    - "Pressure-Based Coupling"
    - "Crisis-Framed Misrouting"
    - "Velocity Substitution"
    - "Urgency-as-Validity"
  signature:
    - "pressure↑"
    - "classification compression↑"
    - "consent bypass↑"
    - "context loss↑"
    - "fast response↑"
    - "misfit / debt↑"
    - "H↑"
  primary_layers:
    origin:
      - "U1 — Power / Budgets"
      - "U2 — Configuration / Boundaries"
      - "U3 — Execution / Runtime"
      - "U4 — Information / Truth"
      - "U5 — Coordination / Time"
      - "U6 — Coherence Field"
      - "U7 — Memory / Recurrence"
      - "U8 — Environment / Field"
    manifestation:
      - "U2 — Boundaries"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U5 — Time"
      - "U6 — Field"
      - "U7 — Memory"
  state_variables:
    - "Τ"
    - "D"
    - "Ψ"
    - "Γ"
    - "Au"
    - "BΣ"
    - "K"
    - "O"
    - "H"
    - "Λ"
    - "R"
    - "Φ"
    - "G"
  first_gate_failure: "Urgency Classification Gate"
  restoration:
    - "Urgency Classification Audit"
    - "Sequencing Restoration"
    - "Consent Revalidation"
    - "Context Re-expansion"
    - "Proportionality Recalibration"
    - "Emergency Authority Review"
    - "Reversibility Restoration"
    - "Hidden Urgency Debt Accounting"
    - "Repair Path Reattachment"
    - "Local Coherence Restoration"