schema_version: "1.0"

id: "FM-ECO-016"

title: "FM-ECO-016 — Urgency Substitution"

slug: "fm-eco-016-urgency-substitution"

type: "failure_mode"

status: "draft"

version: "0.1.0"

last_updated: "2026-06-19"

summary: "Urgency Substitution occurs when economic urgency, deadline pressure, scarcity pressure, crisis framing, speed demands, market timing, competitive fear, or emergency logic substitutes for actual need, coherence, phase fit, consent, capacity, auditability, or restoration priority."

canonical_url: "/archive/failure-modes/registry/economy/fm-eco-016-urgency-substitution"

citation_id: "FM-ECO-016-v0-1-0"

canon:

tier: "registry"

state: "draft"

source: "UTS — Failure Modes Registry"

source_id: "FM-ECO-016"

legacy_ids:

• "FM-ECOX-012"

classification:

family: "failure-modes"

module: "economy"

module_group: "economy"

density: "advanced-reference"

audience:

• "UTS readers"
• "economic systems researchers"
• "restoration researchers"
• "justice researchers"
• "cybernetics researchers"
• "security researchers"
• "AI governance researchers"
• "coherence researchers"
• "machine readers"

tags:

• "failure-modes"
• "economy"
• "urgency-substitution"
• "fm-eco-016-urgency-substitution"
• "fm-ecox-012-urgency-substitution"
• "urgency"
• "scarcity-pressure"
• "crisis-framing"
• "speed"
• "phase-failure"
• "consent"
• "capacity"
• "hidden-debt"
• "coherence"

aliases:

• "Urgency Substitution"
• "Economic Urgency Substitution"
• "Urgency-as-Need"
• "Speed Substitution"
• "Crisis-Framing Substitution"
• "Scarcity Pressure Substitution"
• "Deadline Capture"
• "Market-Timing Capture"
• "False Economic Urgency"
• "Emergency Logic Substitution"

related:

laws:

• "Urgency Substitution"
• "Phase Failure"
• "Late Delivery"
• "Premature Delivery"
• "Over-Delivery"
• "Under-Delivery"
• "Consent Drift"
• "Emergency Normalization"
• "Goodhart Collapse"
• "Hidden Debt Accumulation"
• "Delayed Transition Under Clarity"
• "Expansion Without Capacity"

invariants:

• "Urgency Must Not Replace Need"
• "Speed Must Preserve Coherence"
• "Emergency Logic Must Remain Auditable"
• "Timing Pressure Must Not Override Consent"
• "Fast Delivery Must Still Match Phase"
• "Crisis Must Not Become Governance Default"
• "Priority Must Follow Need, Not Pressure"

operators:

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

gates:

• "Urgency Gate"
• "Need Priority Gate"
• "Phase Gate"
• "Capacity Gate"
• "Consent Gate"
• "Damping Gate"
• "Auditability Gate"
• "Restoration Gate"
• "Local Coherence Gate"

diagnostics:

• "Urgency Validity"
• "Need Priority"
• "Phase Fit"
• "Capacity Fit"
• "Consent Validity"
• "Damping Adequacy"
• "Hidden Debt"
• "Emergency Drift"
• "Auditability"
• "Local Coherence"

failure_modes:

• "FM-ECO-002 — Over-Delivery"
• "FM-ECO-007 — Phase Failure"
• "FM-ECO-010 — Expansion Without Capacity"
• "FM-ECO-012 — Late Delivery"
• "FM-ECO-013 — Conditional Coercive Delivery"
• "FM-ECO-024 — Premature ⊕"
• "FM-ECO-028 — Repair Starvation"
• "FM-ISC-003 — Urgency Substitution"
• "FM-ISC-009 — Consent Drift"
• "FM-C-007 — Under-Damped Escalation"
• "FM-C-012 — Gain Saturation"
• "FM-SEC-010 — Emergency Normalization"
• "FM-S-010 — Hidden Debt Explosion"

restoration_arcs:

• "Urgency Validity Audit"
• "Need Priority Recalibration"
• "Phase Fit Review"
• "Capacity Check Restoration"
• "Damping Restoration"
• "Consent Revalidation"
• "Emergency Drift Rollback"
• "Speed / Coherence Rebalancing"
• "Hidden Urgency Debt Accounting"
• "Local Coherence Restoration"

modules:

• "Economy"
• "Interactions"
• "Cybernetics"
• "Scaling"
• "Restoration"
• "Justice"
• "Security"
• "AI Governance"
• "Diagnostics"
• "Coherence"

navigation:

order: 1316

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/economy/fm-eco-016-urgency-substitution.md"

legacy_source_file: "content/archive/failure-modes/registry/economy/fm-ecox-012-urgency-substitution.md"

notes: "Unified from former FM-ECOX-012 into continuous Economy namespace. Domain expression of ISC urgency substitution focused on economic pressure, deadlines, market timing, scarcity, crisis framing, and speed demands replacing need, phase fit, consent, capacity, auditability, and restoration priority."

entry:

failure_mode_id: "FM-ECO-016"

failure_family: "Economy"

production_treatment: "Domain Expression"

legacy_ids:

• "FM-ECOX-012"

parent_modes:

• "FM-ISC-003 — Urgency Substitution"
• "FM-ECO-007 — Phase Failure"
• "FM-SEC-010 — Emergency Normalization"
• "FM-C-007 — Under-Damped Escalation"
• "FM-S-010 — Hidden Debt Explosion"

first_gate_failure: "Urgency Gate"

primary_hidden_debt: "Hidden debt accumulates when urgency-driven decisions bypass need assessment, phase fit, consent, capacity checks, damping, auditability, or restoration priority, forcing affected nodes to carry the downstream cost of rushed or pressure-driven delivery."

primary_inversion: "Urgency becomes proof of importance; the system treats speed, pressure, scarcity, or crisis framing as evidence that action is coherent, even when the action is mistimed, mis-targeted, coercive, under-supported, or debt-producing."

primary_boundary_pattern: "The boundary between valid time-sensitive need and manufactured or misdirected urgency collapses; pressure gains authority over coherence."

primary_signature: "Urgency rises; priority logic narrows; capacity and phase checks are skipped; consent is compressed; delivery accelerates or reroutes; hidden debt accumulates under the claim that there was no time."

FM-ECO-016 — 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-ECO-016

Legacy ID: FM-ECOX-012

Family: Economy

Production Treatment: Domain Expression

Parent Modes: FM-ISC-003 — Urgency Substitution; FM-ECO-007 — Phase Failure; FM-SEC-010 — Emergency Normalization; FM-C-007 — Under-Damped Escalation; FM-S-010 — Hidden Debt Explosion

0. Economic Scope Note

This entry is conceptual and systems-oriented.

It does not treat urgency, speed, deadline sensitivity, emergency response, rapid delivery, competitive timing, crisis action, or time-bounded prioritization as inherently failed.

Some needs are urgent.

Some delivery windows are narrow.

Some systems must move quickly to preserve coherence.

Urgency can be valid when it is:

• tied to real need
• phase-aware
• consent-aware
• capacity-aware
• auditable
• bounded in scope
• time-limited
• restoration-aware
• followed by debt accounting
• responsive to local conditions
• able to slow down when the urgency passes

The failure begins when urgency substitutes for truth.

The issue is not speed.

The issue is pressure being mistaken for priority.

Urgency Substitution occurs when the felt or imposed need to move quickly replaces the actual work of determining what should happen, for whom, when, under what conditions, and at what cost.

1. Definition

Urgency Substitution occurs when economic urgency, deadline pressure, scarcity pressure, crisis framing, speed demands, market timing, competitive fear, or emergency logic substitutes for actual need, coherence, phase fit, consent, capacity, auditability, or restoration priority.

The substituted urgency may come from:

• deadlines
• funding cycles
• market windows
• competitive pressure
• scarcity framing
• crisis messaging
• investor pressure
• budget cliffs
• political timing
• media cycles
• sales pressure
• procurement deadlines
• emergency declarations
• launch schedules
• quarterly targets
• public optics
• institutional fear
• supply shocks
• artificial scarcity
• platform timing
• productivity demands
• growth narratives

The core failure is:

urgency↑
priority discernment↓
phase / capacity / consent checks skipped
action accelerates
H↑

Urgency Substitution is not fast response.

It is speed replacing discernment.

2. Core Pattern

The core pattern is:

1. A system encounters pressure to act quickly.
2. The pressure is framed as urgent, critical, scarce, competitive, emergency, or time-sensitive.
3. Urgency gains authority.
4. Need, phase, consent, capacity, timing, auditability, and restoration questions are compressed or bypassed.
5. Resources move, commitments are made, contracts are signed, launches proceed, or interventions occur.
6. The action is justified by the urgency rather than by coherence.
7. Affected nodes carry downstream burden from mis-sequenced or under-audited action.
8. The system records speed as responsiveness.
9. Hidden debt accumulates through rushed delivery, missed checks, coerced acceptance, or wrong priority.
10. Restoration requires separating valid urgency from pressure-substituted urgency.

This failure often appears as:

we had to move fast

while the hidden truth is:

speed replaced the checks that would have prevented debt

or:

there was no time

while the overlooked condition is:

the system did not preserve enough timing intelligence to know what time required

The restorative question is:

urgent according to what, and urgent for whom?

Urgency Substitution turns pressure into governance.

3. Failure Signature

Typical signature:

urgency↑
discernment↓
damping↓
phase fit↓
capacity checks↓
consent compression↑
H↑

Extended signature:

deadlines override readiness
scarcity framing overrides consent
market timing overrides repair
launch pressure overrides audit
crisis framing overrides proportionality
budget cliffs override need priority
speed metrics override local coherence
competitive fear overrides capacity truth

Common forms include:

funding must be spent quickly, so resources are mis-targeted
contracts must close now, so consent is compressed
products must launch before support capacity exists
aid must be distributed immediately, so phase fit is ignored
layoffs are rushed under crisis framing without burden accounting
AI systems deploy before appeal or correction capacity exists
security controls are imposed quickly without restoration pathways
emergency procurement bypasses audit and creates future debt
market opportunity overrides maintenance and repair
budget deadlines force wasteful or incoherent spending

The defining condition is not that action is fast.

The defining condition is that urgency replaces the tests that make action coherent.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: funding cycles, investor pressure, competition, authority, or scarcity narratives impose urgency.
• U2 — Configuration / Boundaries: decision boundaries allow emergency logic to bypass normal coherence gates.
• U3 — Execution / Runtime: operations accelerate without capacity or feedback.
• U4 — Information / Truth: urgency signal substitutes for need truth.
• U5 — Coordination / Time: primary origin layer; timing pressure is misclassified as priority.
• U6 — Coherence Field: crisis energy creates legitimacy aura.
• U7 — Memory / Recurrence: repeated urgency becomes normal operating rhythm.
• U8 — Environment / Field: market volatility, public pressure, or external shocks increase urgency tone.

Common manifestation layers:

• U1 — Power: pressure source dominates decision priority.
• U3 — Execution: action accelerates.
• U4 — Truth: urgency substitutes for coherence evidence.
• U5 — Time: phase and sequence checks fail.
• U6 — Field: emergency aura overrides dissent.
• U7 — Memory: crisis tempo becomes baseline.
• U8 — Environment: field pressure compresses choice.

Urgency Substitution is primarily a U5 timing-priority and U4 truth-substitution failure.

The system loses the difference between time-sensitive coherence and pressure-driven acceleration.

5. Typical Development Sequence

A common development sequence is:

1. A real or perceived time pressure appears.
2. The system frames action as urgent.
3. Speed becomes the primary value.
4. Need-priority questions narrow.
5. Phase, capacity, consent, and audit checks are treated as obstacles.
6. Action proceeds quickly.
7. The action produces under-delivery, over-delivery, mis-targeting, coercion, capacity strain, or hidden debt.
8. The urgency is used to excuse the missing checks.
9. The resulting debt creates new crises.
10. The new crises justify more urgency.
11. Emergency rhythm becomes normalized.
12. The system loses the ability to distinguish valid urgency from urgency culture.

The loop often looks like:

pressure → urgency framing → bypassed checks → hidden debt → new pressure

Another common loop is:

deadline → rushed action → repair backlog → crisis response → more deadlines

Urgency Substitution becomes self-reinforcing when debt created by rushed action produces the next urgency signal.

6. Diagnostic Markers

Diagnostic markers include:

• “No time” is used to bypass questions that directly affect harm or coherence.
• Speed is treated as proof of responsiveness.
• Capacity checks are labeled delay.
• Consent is compressed by deadlines or scarcity.
• Need priority is determined by pressure source rather than affected-node state.
• Emergency exceptions become normal pathways.
• The system cannot distinguish urgent-important from urgent-loud.
• Actions repeatedly require later repair.
• Deadlines are set by funding, optics, sales, or competition rather than receiving-state need.
• Affected nodes experience urgency as coercion.
• Delivery occurs quickly but requires rework.
• Repair is deferred because “the immediate priority” keeps moving.
• Auditability is reduced under time pressure.
• Local coherence improves when urgency is slowed and priority is recalibrated.

Useful diagnostics:

• Urgency Validity: Tests whether urgency corresponds to real time-sensitive need.
• Need Priority: Determines whether action priority matches affected-node state.
• Phase Fit: Tests whether the action fits the current phase.
• Capacity Fit: Determines whether the system can carry accelerated action.
• Consent Validity: Tests whether refusal remains viable under time pressure.
• Damping Adequacy: Measures whether speed is being paced coherently.
• Hidden Debt: Tracks cost created by rushed or bypassed checks.
• Emergency Drift: Measures whether exceptional urgency has become normal operation.
• Auditability: Determines whether urgency decisions remain traceable.
• Local Coherence: Tests whether fast action actually improves affected nodes.

7. Related Gates

Relevant gates include:

• Urgency Gate: Fails when urgency is not tested for validity.
• Need Priority Gate: Fails when pressure replaces affected-state need.
• Phase Gate: Fails when action proceeds without phase fit.
• Capacity Gate: Fails when speed outruns delivery, maintenance, or restoration capacity.
• Consent Gate: Fails when urgency compresses refusal.
• Damping Gate: Fails when acceleration is not paced.
• Auditability Gate: Fails when time pressure suppresses traceability.
• Restoration Gate: Fails when repair is postponed by recurring urgent action.
• Local Coherence Gate: Fails when speed does not improve the receiving state.

The first common gate failure is usually the Urgency Gate.

The system accepts urgency before asking whether urgency is true.

8. Related Operators

Relevant operators include:

• Τ — Trajectory / Time: Primary operator; governs urgency, timing windows, sequence, and phase.
• G — Gain: Amplifies pressure, speed, competition, and crisis response.
• Γ — Selection: Selects priorities under pressure.
• Φ — Flow / Resource Movement: Moves resources or commitments quickly, sometimes incoherently.
• D — Damping: Prevents harmful acceleration when functioning.
• K — Constraint / Load: Rises when rushed action creates burden.
• H — Hidden Debt: Accumulates when checks are bypassed.
• R — Restoration Capacity: Is often deferred or consumed.
• Au — Auditability: Drops when speed suppresses review.
• Ψ — Observation / Interface: Shapes what appears urgent.
• Λ — Compatibility: Tests fit between urgency and action.
• BΣ — Boundary Integrity: Protects consent and scope boundaries under pressure.
• O — Coherence: May appear improved through fast visible motion.

Common operator pattern:

Τ pressure rises
G amplifies urgency
Γ selects speed-first action
D fails to pace
Ψ narrows observation
Λ fit is skipped
BΣ consent and scope boundaries compress
Φ moves quickly
H accumulates through bypassed checks

The core operator inversion is:

urgent → important → coherent

instead of:

urgent + need-valid + phase-fit + capacity-fit + consent-valid → coherent priority

Urgency Substitution turns time pressure into a false truth signal.

9. Related Laws and Invariants

Related Laws

• Urgency Substitution: parent interaction failure where urgency replaces signal truth.
• Phase Failure: urgency often pushes action into wrong phase.
• Late Delivery: urgency may arise after earlier delay and then create rushed misdelivery.
• Premature Delivery: urgency may force early support before readiness.
• Over-Delivery: urgency can intensify delivery beyond absorption.
• Under-Delivery: urgency can send incomplete support.
• Consent Drift: time pressure weakens refusal validity.
• Emergency Normalization: exceptional urgency becomes routine governance.
• Goodhart Collapse: speed becomes target and replaces outcome.
• Hidden Debt Accumulation: rushed action stores future repair cost.
• Delayed Transition Under Clarity: ignored timing need later returns as artificial urgency.
• Expansion Without Capacity: urgency drives growth before capacity.

Related Invariants

• Urgency Must Not Replace Need: pressure is not proof of priority.
• Speed Must Preserve Coherence: fast action must still fit state and capacity.
• Emergency Logic Must Remain Auditable: urgency must not erase accountability.
• Timing Pressure Must Not Override Consent: refusal remains part of coherence.
• Fast Delivery Must Still Match Phase: acceleration does not remove phase requirements.
• Crisis Must Not Become Governance Default: emergency pathways must expire.
• Priority Must Follow Need, Not Pressure: affected-node state outranks loudness.

10. Common False Positives

Not every urgent action is Urgency Substitution.

Common false positives include:

• Real emergency response with valid time-sensitive need.
• Rapid delivery after phase, consent, and capacity checks.
• Time-critical intervention with clear audit trail.
• Deadline-driven work that remains coherent and proportionate.
• Emergency exceptions that expire and receive after-action review.
• Fast support requested by the affected node.
• Accelerated repair that reduces hidden debt.
• Crisis response paired with later burden accounting.
• Rapid deployment with adequate rollback and restoration capacity.
• Short decision windows where key gates are preserved.
• Urgent spending that is accurately targeted and auditable.
• Competitive action that does not suppress coherence checks.

Clarifying rule:

This is not Urgency Substitution unless urgency, deadline pressure, crisis framing, scarcity pressure, or speed demand substitutes for actual need, phase fit, consent, capacity, auditability, or restoration priority.

11. Common False Repairs

Common false repairs include:

• slowing everything down without restoring priority logic
• adding review layers that create future late delivery
• rebranding urgency as agility
• holding postmortems without changing deadline structures
• creating emergency checklists that are always active
• requiring consent forms while time pressure remains coercive
• adding dashboards for urgent work without reducing debt
• treating all urgency as false
• treating all slowness as carefulness
• delaying repair because the urgent cycle continues
• prioritizing visible crises while quiet high-need nodes degrade
• creating artificial deadlines to overcome prior over-constriction
• measuring response time instead of restored coherence
• using emergency success to justify permanent emergency governance
• blaming local nodes for stress caused by rushed decisions

False repair often produces the loop:

urgency causes debt → review slows system → delays create new urgency → urgency returns

Another common loop is:

false urgency exposed → urgency language softened → same pressure path remains

The repair fails because it does not restore the distinction between valid urgency and pressure substitution.

12. Restoration Direction

Restoration requires auditing urgency validity, separating pressure from real need, restoring phase and capacity checks, preserving consent under time pressure, and accounting for hidden debt created by rushed action.

Primary restoration direction:

test urgency,
restore priority discernment,
pace action,
and repair urgency-created debt

A fuller restoration path includes:

1. Name the urgency source. Identify deadline, market window, crisis frame, scarcity pressure, funding cycle, optics, competition, or emergency claim.
2. Name the affected need. Determine whose state actually requires time-sensitive action.
3. Test urgency validity. Separate true timing need from pressure, fear, optics, or artificial scarcity.
4. Map phase fit. Determine whether action fits the receiving state now.
5. Check capacity. Confirm delivery, maintenance, support, and restoration capacity can carry accelerated action.
6. Protect consent. Preserve viable refusal and non-coercive participation under time pressure.
7. Restore damping. Pace action to prevent over-delivery, mis-targeting, or bypassed checks.
8. Preserve auditability. Record why urgency was accepted and which gates were compressed.
9. Limit emergency scope. Bound urgent exceptions by time, domain, and review.
10. Account for skipped checks. Revisit any coherence gates bypassed during urgency.
11. Repair urgency debt. Address harm, rework, trust loss, or burden created by rushed decisions.
12. Recalibrate priority logic. Ensure future priority follows need rather than pressure.
13. Install urgency gates. Require urgency validity review before acceleration.
14. Validate local coherence. Confirm the action improved affected-node state.
15. Prevent emergency normalization. Retire urgency pathways when conditions pass.

A valid restoration path should reduce:

false urgency
consent compression
rushed misdelivery
phase mismatch
capacity overrun
audit loss
emergency drift
repair backlog
H

Urgency Substitution is not repaired by becoming slow.

It is repaired by restoring timing intelligence.

13. Cross-Module Links

• Economy: Core failure of deadline pressure, scarcity framing, market timing, funding cliffs, crisis spending, and speed-first economic action.
• Interactions: Direct domain expression of urgency substituting for signal truth.
• Cybernetics: Urgency can create under-damped escalation, gain saturation, and feedback bypass.
• Scaling: Urgency can drive expansion, deployment, or integration before capacity exists.
• Restoration: Repair is often postponed or rushed when urgent cycles dominate.
• Justice: Urgency can justify coercive settlements, rushed enforcement, or delayed remedy converted into pressure.
• Security: Emergency normalization and crisis access controls can become standing governance.
• AI Governance: AI launches, guardrails, evals, appeals, and deployment decisions can be rushed under competitive or safety urgency.
• Diagnostics: Requires urgency-validity, phase-fit, capacity-fit, consent-validity, damping, and hidden-debt diagnostics.
• Coherence: Coherent urgency preserves state truth under time pressure.

14. Relationship to Parent / Child Modes

Production treatment: Domain Expression

This mode maps upward to:

• FM-ISC-003 — Urgency Substitution
• FM-ECO-007 — Phase Failure
• FM-SEC-010 — Emergency Normalization
• FM-C-007 — Under-Damped Escalation
• FM-S-010 — Hidden Debt Explosion

Sibling or related Economy modes include:

• FM-ECO-002 — Over-Delivery
• FM-ECO-007 — Phase Failure
• FM-ECO-010 — Expansion Without Capacity
• FM-ECO-012 — Late Delivery
• FM-ECO-013 — Conditional Coercive Delivery
• FM-ECO-014 — Economic Over-Constriction
• FM-ECO-021 — “No Alternative” Framing
• FM-ECO-024 — Premature ⊕
• FM-ECO-028 — Repair Starvation
• FM-ECO-029 — Growth Theater

Related cross-family modes include:

• FM-ISC-003 — Urgency Substitution
• FM-ISC-009 — Consent Drift
• FM-C-007 — Under-Damped Escalation
• FM-C-012 — Gain Saturation
• FM-S-010 — Hidden Debt Explosion
• FM-S-015 — Bandwidth Saturation
• FM-SEC-010 — Emergency Normalization
• FM-JC-006 — Emergency Normalization
• FM-AIX-007 — Short-Horizon Survival Attractor
• FM-AIX-013 — False-Positive Safety Distortion
• FM-R-007 — Repair Suppression via Efficiency

Aliases preserved from source material:

• Urgency Substitution
• Economic Urgency Substitution
• Urgency-as-Need
• Speed Substitution
• Crisis-Framing Substitution
• Scarcity Pressure Substitution
• Deadline Capture
• Market-Timing Capture
• False Economic Urgency
• Emergency Logic Substitution

Legacy source preserved:

legacy_ids:
  - "FM-ECOX-012"
deprecated_source_ids:
  - "FM-ECOX-012"
source_aliases:
  - "Economy Extended Entry 012"

15. Minimal Entry Version

Definition: Urgency Substitution occurs when economic urgency, deadline pressure, scarcity pressure, crisis framing, speed demands, market timing, competitive fear, or emergency logic substitutes for actual need, coherence, phase fit, consent, capacity, auditability, or restoration priority.

Signature:

urgency↑
discernment↓
damping↓
phase fit↓
capacity checks↓
consent compression↑
H↑

Restoration direction:

• name the urgency source
• name the affected need
• test urgency validity
• map phase fit
• check capacity
• protect consent
• restore damping
• preserve auditability
• limit emergency scope
• account for skipped checks
• repair urgency debt
• recalibrate priority logic
• install urgency gates
• validate local coherence
• prevent emergency normalization

16. Machine-Readable Summary

failure_mode:
  id: "FM-ECO-016"
  name: "Urgency Substitution"
  family: "Economy"
  production_treatment: "Domain Expression"
  legacy_ids:
    - "FM-ECOX-012"
  parent_modes:
    - "FM-ISC-003 — Urgency Substitution"
    - "FM-ECO-007 — Phase Failure"
    - "FM-SEC-010 — Emergency Normalization"
    - "FM-C-007 — Under-Damped Escalation"
    - "FM-S-010 — Hidden Debt Explosion"
  primary_failure: "Urgency, deadline pressure, crisis framing, scarcity pressure, or speed demand substitutes for actual need, phase fit, consent, capacity, auditability, or restoration priority."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ECO-016"
  deprecated_source_ids:
    - "FM-ECOX-012"
  scope_note: "Conceptual and systems-oriented; does not treat urgency, speed, deadline sensitivity, emergency response, rapid delivery, competitive timing, crisis action, or time-bounded prioritization as inherently failed."
  aliases:
    - "Urgency Substitution"
    - "Economic Urgency Substitution"
    - "Urgency-as-Need"
    - "Speed Substitution"
    - "Crisis-Framing Substitution"
    - "Scarcity Pressure Substitution"
    - "Deadline Capture"
    - "Market-Timing Capture"
    - "False Economic Urgency"
    - "Emergency Logic Substitution"
  signature:
    - "urgency↑"
    - "discernment↓"
    - "damping↓"
    - "phase fit↓"
    - "capacity checks↓"
    - "consent compression↑"
    - "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:
      - "U1 — Power"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U5 — Time"
      - "U6 — Field"
      - "U7 — Memory"
      - "U8 — Environment"
  state_variables:
    - "Τ"
    - "G"
    - "Γ"
    - "Φ"
    - "D"
    - "K"
    - "H"
    - "R"
    - "Au"
    - "Ψ"
    - "Λ"
    - "BΣ"
    - "O"
  first_gate_failure: "Urgency Gate"
  restoration:
    - "Urgency Validity Audit"
    - "Need Priority Recalibration"
    - "Phase Fit Review"
    - "Capacity Check Restoration"
    - "Damping Restoration"
    - "Consent Revalidation"
    - "Emergency Drift Rollback"
    - "Speed / Coherence Rebalancing"
    - "Hidden Urgency Debt Accounting"
    - "Local Coherence Restoration"