schema_version: "1.0"

id: "FM-ECO-012"

title: "FM-ECO-012 — Late Delivery"

slug: "fm-eco-012-late-delivery"

type: "failure_mode"

status: "draft"

version: "0.1.0"

last_updated: "2026-06-19"

summary: "Late Delivery occurs when needed resource, support, payment, repair, authority, information, care, capacity, attention, intervention, or relief arrives after the valid window of use has narrowed, closed, or become more costly, causing otherwise useful delivery to lose value, compound hidden debt, or fail to restore the affected node."

canonical_url: "/archive/failure-modes/registry/economy/fm-eco-012-late-delivery"

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

canon:

tier: "registry"

state: "draft"

source: "UTS — Failure Modes Registry"

source_id: "FM-ECO-012"

legacy_ids:

• "FM-ECOX-004"

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"
• "late-delivery"
• "fm-eco-012-late-delivery"
• "fm-ecox-004-late-delivery"
• "timing"
• "delay"
• "delivery-window"
• "repair-window"
• "phase-failure"
• "hidden-debt"
• "coherence"

aliases:

• "Late Delivery"
• "Delayed Delivery"
• "Delayed Support"
• "Late Support"
• "Late Repair"
• "After-Window Delivery"
• "Post-Window Support"
• "Delayed Relief"
• "Missed Delivery Window"
• "Too-Late Delivery"

related:

laws:

• "Phase Failure"
• "Under-Delivery"
• "Latency Blindness"
• "Hidden Debt Accumulation"
• "Restoration Starvation"
• "Delayed Transition Under Clarity"
• "Unproven Stability"
• "Capacity Collapse / Control Impossibility"
• "Exported Economic Incoherence"
• "Victim Burden Inversion"

invariants:

• "Timing Is Part of Delivery"
• "Repair Must Arrive in the Correct Window"
• "Late Flow Cannot Undo All Accrued Debt"
• "Delivery Must Match Phase"
• "Delay Must Be Accounted as Debt"
• "Support Must Preserve Viability Before Collapse"
• "Windows Must Remain Auditable"

operators:

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

gates:

• "Timing Gate"
• "Delivery Window Gate"
• "Phase Gate"
• "Restoration Gate"
• "Viability Gate"
• "Debt Accounting Gate"
• "Readiness Gate"
• "Auditability Gate"
• "Local Coherence Gate"

diagnostics:

• "Timing Fit"
• "Delivery Window"
• "Repair Window"
• "Latency"
• "Hidden Debt"
• "Viability Loss"
• "Restoration Capacity"
• "Need / Supply Fit"
• "Auditability"
• "Local Coherence"

failure_modes:

• "FM-ECO-001 — Under-Delivery"
• "FM-ECO-007 — Phase Failure"
• "FM-ECO-010 — Expansion Without Capacity"
• "FM-ECO-011 — Exported Economic Incoherence"
• "FM-C-005 — Latency Blindness"
• "FM-S-006 — Restoration Starvation"
• "FM-S-010 — Hidden Debt Explosion"
• "FM-C-013 — Capacity Collapse / Control Impossibility"
• "FM-R-003 — Insight Without Load Reduction"
• "FM-RX-008 — Reintegration Without Time Validation"
• "FM-RX-009 — Repair Through Suppressed Auditability"
• "FM-JC-004 — Under-Resourced Justice"

restoration_arcs:

• "Delivery Window Audit"
• "Late Debt Accounting"
• "Timing Recalibration"
• "Repair Window Restoration"
• "Emergency Viability Support"
• "Backlog Reduction"
• "Delayed Burden Compensation"
• "Phase Fit Repair"
• "Restoration Capacity Scaling"
• "Local Coherence Restoration"

modules:

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

navigation:

order: 1312

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-012-late-delivery.md"

legacy_source_file: "content/archive/failure-modes/registry/economy/fm-ecox-004-late-delivery.md"

notes: "Unified from former FM-ECOX-004 into continuous Economy namespace. Standalone economy entry focused on support, repair, payment, resource, information, capacity, authority, or relief arriving after the valid delivery or repair window, producing reduced usable value and accumulated hidden debt."

entry:

failure_mode_id: "FM-ECO-012"

failure_family: "Economy"

production_treatment: "Standalone Entry"

legacy_ids:

• "FM-ECOX-004"

parent_modes:

• "FM-ECO-001 — Under-Delivery"
• "FM-ECO-007 — Phase Failure"
• "FM-C-005 — Latency Blindness"
• "FM-S-006 — Restoration Starvation"
• "FM-CORE-002 — Hidden Debt Accumulation"

first_gate_failure: "Timing Gate"

primary_hidden_debt: "Hidden debt accumulates when needed delivery arrives after affected nodes have already absorbed preventable cost, lost viability, adapted around absence, exited, degraded, or crossed a repair threshold."

primary_inversion: "Delivery becomes evidence of support even though the delay changed the receiving state, increased repair cost, or made the original support insufficient."

primary_boundary_pattern: "The boundary between delivered and delivered-in-time collapses; the system counts eventual delivery as if timing did not alter value, burden, legitimacy, or repair requirements."

primary_signature: "Need emerges; delivery is delayed; affected nodes absorb cost; repair window narrows or closes; eventual delivery arrives with reduced value; hidden debt remains unless delay burden is explicitly repaired."

FM-ECO-012 — Late Delivery

Status: Draft

Archive Type: Failure Mode

System: Universal Theory Stack

Parent: Failure Modes

Canon Tier: Registry

Registry: Failure Modes Registry

Entry ID: FM-ECO-012

Legacy ID: FM-ECOX-004

Family: Economy

Production Treatment: Standalone Entry

Parent Modes: FM-ECO-001 — Under-Delivery; FM-ECO-007 — Phase Failure; FM-C-005 — Latency Blindness; FM-S-006 — Restoration Starvation; FM-CORE-002 — Hidden Debt Accumulation

0. Economic Scope Note

This entry is conceptual and systems-oriented.

It does not treat delay, waiting, pacing, staging, review, preparation, sequencing, caution, buffering, or gradual delivery as inherently failed.

Some delivery must wait.

Some systems require preparation before support can be used.

Some resources should not be released until:

• readiness exists
• safety conditions are met
• local absorption capacity is present
• the right phase has arrived
• delivery would not overload the receiver
• the receiving node has consented
• the sequence has reached the proper step
• premature delivery would create greater burden

The failure begins when delay exceeds the valid window.

The issue is not delay.

The issue is delivery after the receiving state has already been damaged by absence.

Late Delivery occurs when a needed flow arrives after the delay itself has changed the system.

1. Definition

Late Delivery occurs when needed resource, support, payment, repair, authority, information, care, capacity, attention, intervention, or relief arrives after the valid window of use has narrowed, closed, or become more costly, causing otherwise useful delivery to lose value, compound hidden debt, or fail to restore the affected node.

The late delivery may involve:

• money
• food
• housing
• tools
• staffing
• payment
• maintenance
• medical support
• operational support
• governance action
• legal remedy
• justice repair
• apology
• recognition
• decision authority
• training
• information
• documentation
• access
• safety intervention
• restoration capacity
• compute capacity
• customer support
• emotional or relational repair
• infrastructure repair

The core failure is:

need arises
delivery delayed
receiving state degrades
delivery arrives after value window
H remains / increases

Late Delivery is not merely slow delivery.

It is delivery whose delay alters the burden landscape.

2. Core Pattern

The core pattern is:

1. A need appears.
2. A resource, action, or repair could reduce burden if delivered inside the valid window.
3. Delivery is delayed by bureaucracy, capacity shortage, denial, budget timing, gatekeeping, indecision, misread urgency, coordination failure, or strategic withholding.
4. The affected node carries the burden during the delay.
5. The receiving state changes.
6. Costs compound.
7. Workarounds, harm, adaptation, distrust, or exit occur.
8. Delivery eventually arrives.
9. The system counts the delivery as support.
10. The affected node remains burdened because the delay created additional debt.
11. Restoration requires accounting for the late interval, not merely delivering the original resource.

This failure often appears as:

we delivered it eventually

while the hidden truth is:

but the delay created its own debt

or:

the requested support was provided

while the overlooked condition is:

after the support could no longer do what it originally would have done

The restorative question is:

what changed while delivery was absent?

Late Delivery turns time into unacknowledged cost.

3. Failure Signature

Typical signature:

need present
delivery delayed
latency↑
viability↓
repair cost↑
original delivery value↓
H↑

Extended signature:

payment arrives after eviction pressure
repair arrives after infrastructure failure
recognition arrives after trust collapse
support arrives after burnout
authority arrives after illegitimacy hardens
information arrives after wrong action is taken
maintenance arrives after damage spreads
justice arrives after affected nodes exit
governance arrives after incentives lock in

Common forms include:

aid arrives after local capacity has collapsed
wages arrive after debt has compounded
maintenance arrives after replacement becomes necessary
support tickets resolve after users leave
policy action arrives after the exploit becomes normalized
appeal processes complete after opportunity is lost
safety intervention arrives after harm has propagated
repair funding arrives after trust has broken
data access arrives after the decision window closes
training arrives after the tool has already caused overload

The defining condition is not that delivery happened late relative to preference.

The defining condition is that late arrival reduced, inverted, or failed the intended effect.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: funding cycles, hierarchy, approval rights, scarcity control, or resource power delay delivery.
• U2 — Configuration / Boundaries: routing, permissions, eligibility boundaries, or responsibility boundaries slow support.
• U3 — Execution / Runtime: operations, staffing, logistics, queues, or implementation capacity delay delivery.
• U4 — Information / Truth: urgency is misread, need is undercounted, or delivery occurrence substitutes for timing truth.
• U5 — Coordination / Time: primary origin layer; latency, sequence, and delivery-window logic fail.
• U6 — Coherence Field: eventual delivery creates the appearance that the system responded.
• U7 — Memory / Recurrence: chronic late delivery becomes normalized.
• U8 — Environment / Field: external shocks, market timing, or institutional rhythms override local timing need.

Common manifestation layers:

• U3 — Execution: delivery arrives late in runtime.
• U4 — Truth: late delivery is counted as successful delivery.
• U5 — Time: valid window narrows or closes.
• U6 — Field: response aura hides accumulated delay debt.
• U7 — Memory: lateness becomes normal expectation.
• U8 — Environment: field conditions worsen during delay.

Late Delivery is primarily a U5 timing-window failure.

The system treats delivery as a binary event instead of a time-sensitive relation.

5. Typical Development Sequence

A common development sequence is:

1. A need becomes active.
2. The affected node signals need or the system detects it.
3. The system recognizes the need incompletely, slowly, or conditionally.
4. Delivery enters a queue, approval process, funding cycle, review layer, or logistics chain.
5. The affected node absorbs load while waiting.
6. Hidden debt begins accumulating.
7. The original support requirement grows.
8. The valid delivery window narrows.
9. The system finally delivers the original resource.
10. The affected node is now in a different state.
11. Delivery helps less, arrives with new burden, or fails entirely.
12. The system counts delivery as closure.
13. The late interval remains unrepaired.

The loop often looks like:

need → delay → burden growth → original support insufficient → more need

Another common loop is:

late support criticized → process review added → delivery slows further

Late Delivery becomes self-reinforcing when delay is treated as an administrative issue rather than a source of debt.

6. Diagnostic Markers

Diagnostic markers include:

• Affected nodes say support would have helped earlier but no longer fits.
• Delivery occurs after the decision, crisis, repair, or viability window.
• Original support amount is no longer sufficient.
• The system records closure while the affected node remains burdened.
• Delay causes new costs not included in the original delivery.
• Support arrives after workarounds have become necessary.
• Late repair is treated as equivalent to timely repair.
• Delivery backlogs become normal.
• Need is repeatedly revalidated while the burden grows.
• The system asks whether delivery happened but not whether it arrived in time.
• Eligibility or review cycles consume the valid window.
• Trust declines even though support eventually arrives.
• Affected nodes exit before delivery.
• The delay produces secondary failure modes.
• Restoration improves when delay debt is explicitly compensated.

Useful diagnostics:

• Timing Fit: Tests whether delivery arrived inside the valid window.
• Delivery Window: Identifies when the resource could have preserved value.
• Repair Window: Identifies when restoration could still reduce harm.
• Latency: Measures delay between need, recognition, decision, and delivery.
• Hidden Debt: Tracks cost accumulated during absence.
• Viability Loss: Measures degradation while waiting.
• Restoration Capacity: Tests whether repair can still activate.
• Need / Supply Fit: Rechecks whether original support still matches changed state.
• Auditability: Determines whether delay causes are traceable.
• Local Coherence: Tests whether late delivery actually improves state.

7. Related Gates

Relevant gates include:

• Timing Gate: Fails when delivery timing is not validated.
• Delivery Window Gate: Fails when support arrives after the useful window.
• Phase Gate: Fails when the receiving state has changed during delay.
• Restoration Gate: Fails when repair arrives after repair cost has compounded.
• Viability Gate: Fails when the affected node loses capacity while waiting.
• Debt Accounting Gate: Fails when the delay interval is not counted.
• Readiness Gate: Fails when late delivery no longer matches current readiness or need.
• Auditability Gate: Fails when the cause and cost of delay cannot be traced.
• Local Coherence Gate: Fails when eventual delivery does not restore the affected state.

The first common gate failure is usually the Timing Gate.

The system asks whether delivery occurred before asking whether delivery arrived in time.

8. Related Operators

Relevant operators include:

• Τ — Trajectory / Time: Primary operator; governs latency, windows, phase, sequence, and compounding.
• Φ — Flow / Resource Movement: Determines when the needed resource moves.
• R — Restoration Capacity: Decays or becomes more expensive as delay extends.
• H — Hidden Debt: Accumulates during non-delivery.
• K — Constraint / Load: Rises while the affected node carries unmet need.
• Au — Auditability: Reveals delay causes and delay cost.
• Ψ — Observation / Interface: Determines whether urgency and changed state are seen.
• Λ — Compatibility: Tests whether the late resource still fits the current state.
• Γ — Selection: Selects whether to deliver now, later, or not at all.
• O — Coherence: May appear restored through eventual delivery.
• D — Damping: Paces delivery but can become delay if misapplied.
• G — Gain: Can amplify queues, urgency misread, or process pressure.
• BΣ — Boundary Integrity: Determines whether responsibility for delay remains attached.

Common operator pattern:

need appears
Ψ detects late or partially
Γ delays selection
Φ does not arrive
K rises
H accumulates
Τ window narrows
R weakens or becomes more expensive
Φ eventually arrives
Λ fit is reduced
O is claimed prematurely

The core operator inversion is:

eventual delivery → support fulfilled

instead of:

timely delivery + delay-debt repair → support fulfilled

Late Delivery turns delivery into an incomplete restoration signal.

9. Related Laws and Invariants

Related Laws

• Phase Failure: late delivery is a timing-specific form of wrong-phase delivery.
• Under-Delivery: late delivery may become effectively insufficient delivery.
• Latency Blindness: the system misses how delay changes outcome.
• Hidden Debt Accumulation: costs compound while support is absent.
• Restoration Starvation: repair capacity is unavailable during the needed window.
• Delayed Transition Under Clarity: even known timing needs are not acted on.
• Unproven Stability: the system assumes the receiving state will remain stable while waiting.
• Capacity Collapse / Control Impossibility: delays can push systems beyond control thresholds.
• Exported Economic Incoherence: delay burden is often shifted onto affected nodes.
• Victim Burden Inversion: harmed nodes may carry the cost created by late response.

Related Invariants

• Timing Is Part of Delivery: support is incomplete if it misses the valid window.
• Repair Must Arrive in the Correct Window: restoration has timing requirements.
• Late Flow Cannot Undo All Accrued Debt: delay creates additional cost.
• Delivery Must Match Phase: late delivery must be recalibrated to the changed state.
• Delay Must Be Accounted as Debt: the waiting interval must be measured.
• Support Must Preserve Viability Before Collapse: delivery should arrive before preventable degradation.
• Windows Must Remain Auditable: timing decisions and delays must be traceable.

10. Common False Positives

Not every delayed delivery is Late Delivery.

Common false positives include:

• Delivery delayed to avoid premature overload.
• Support intentionally staged to match readiness.
• A pause requested by the affected node.
• Review time needed to prevent harmful action.
• Delay that remains inside the valid delivery window.
• Slow delivery where the receiving state remains stable.
• Waiting that increases compatibility or safety.
• Emergency triage that prioritizes more time-critical nodes.
• Delayed delivery paired with full delay-debt compensation.
• Delivery after preparation that improves absorption.
• Phased release that preserves coherence.
• Deferred action where non-action is part of valid sequencing.

Clarifying rule:

This is not Late Delivery unless support, resource, payment, repair, authority, information, attention, or relief arrives after the valid window has narrowed, closed, or become more costly in a way that reduces usable value, compounds hidden debt, or fails to restore the affected node.

11. Common False Repairs

Common false repairs include:

• delivering the original resource without adjusting for accumulated debt
• treating eventual delivery as closure
• apologizing for delay without repairing delay cost
• increasing process documentation instead of reducing latency
• adding review layers that make future delays worse
• blaming the affected node for not being restored by late support
• offering support after exit and counting it as care
• delivering symbolic recognition after material repair windows close
• clearing backlogs without accounting for damage caused by waiting
• prioritizing visible late cases while hidden late cases continue
• creating emergency exceptions without fixing ordinary delay pathways
• calling delays unavoidable when delay causes were never audited
• restarting eligibility review after the node’s state has worsened
• using late delivery to deny further responsibility
• demanding gratitude for support that arrived after the burden compounded

False repair often produces the loop:

late delivery criticized → delivery completed → delay debt ignored → affected node remains burdened

Another common loop is:

delay causes harm → system adds safeguards → safeguards slow future delivery → more harm

The repair fails because it treats delivery as sufficient while leaving the late interval unpaid.

12. Restoration Direction

Restoration requires identifying the valid delivery window, measuring delay, accounting for changed state and accumulated debt, delivering updated support, and repairing the cost created by lateness.

Primary restoration direction:

audit the delay,
repair the delay debt,
update delivery to the changed state,
and restore timing fit

A fuller restoration path includes:

1. Name the original need. Identify what support, repair, resource, payment, authority, information, or relief was required.
2. Name the valid window. Determine when delivery would have preserved viability or reduced burden.
3. Measure the delay. Track time between need, recognition, decision, delivery, and use.
4. Identify causes of delay. Locate process, budget, capacity, denial, gatekeeping, logistics, or coordination failure.
5. Map state change during delay. Identify what degraded, adapted, exited, or compounded.
6. Account for delay debt. Measure costs created because support was absent.
7. Reassess current need. Determine whether the original delivery still fits.
8. Update the delivery. Add resources, repair, compensation, explanation, or authority needed for the changed state.
9. Repair secondary harms. Address losses, workarounds, distrust, and capacity depletion caused by lateness.
10. Restore timing feedback. Give affected nodes a path to signal urgency and changed phase.
11. Reduce future latency. Remove avoidable delay points.
12. Install timing gates. Require delivery-window checks before closure.
13. Validate local coherence. Confirm delivery reduces the current burden, not only the original request.
14. Preserve audit trail. Keep visible who delayed what, why, and at what cost.

A valid restoration path should reduce:

latency
delay debt
missed windows
repair cost
viability loss
trust loss
backlog burden
phase mismatch
H

Late Delivery is not repaired by arriving.

It is repaired by accounting for what lateness changed.

13. Cross-Module Links

• Economy: Core failure of delivery timing, payment timing, resource timing, and repair-window economics.
• Restoration: Repair loses effectiveness when it arrives after the valid window and must include delay-debt accounting.
• Justice: Justice delayed may fail as repair when affected nodes have already absorbed irreversible cost.
• Cybernetics: Latency blindness and slow feedback loops convert solvable problems into compounded failures.
• Scaling: Large systems often normalize queues and backlogs that create hidden delay debt.
• Diagnostics: Requires timing-fit, repair-window, latency, hidden-debt, and local-coherence diagnostics.
• Security: Late patches, late disclosures, late incident response, and late access repair can create avoidable harm.
• AI Governance: Late evals, late appeals, late redress, late memory correction, or late policy intervention can fail after model behavior or user dependency has already hardened.
• Interfaces: User support, warnings, explanations, and escalation paths must arrive during actionable windows.
• Coherence: Delivery coherence requires timing, not merely occurrence.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry

This mode maps upward to:

• FM-ECO-001 — Under-Delivery
• FM-ECO-007 — Phase Failure
• FM-C-005 — Latency Blindness
• FM-S-006 — Restoration Starvation
• FM-CORE-002 — Hidden Debt Accumulation

Sibling or related Economy modes include:

• FM-ECO-001 — Under-Delivery
• FM-ECO-003 — Mis-Targeting
• FM-ECO-004 — Stasis / Blockage
• FM-ECO-006 — Shunting / Bypass
• FM-ECO-007 — Phase Failure
• FM-ECO-010 — Expansion Without Capacity
• FM-ECO-011 — Exported Economic Incoherence
• FM-ECO-013 — Conditional Coercive Delivery
• FM-ECO-015 — Clearance Failure
• FM-ECO-028 — Repair Starvation

Related cross-family modes include:

• FM-C-005 — Latency Blindness
• FM-C-013 — Capacity Collapse / Control Impossibility
• FM-S-006 — Restoration Starvation
• FM-S-010 — Hidden Debt Explosion
• FM-R-003 — Insight Without Load Reduction
• FM-R-008 — Audit Evasion in Repair
• FM-RX-008 — Reintegration Without Time Validation
• FM-RX-009 — Repair Through Suppressed Auditability
• FM-JC-004 — Under-Resourced Justice
• FM-JC-011 — Locked-In Renegotiation Failure
• FM-BIOX-020 — Timing Failure

Aliases preserved from source material:

• Late Delivery
• Delayed Delivery
• Delayed Support
• Late Support
• Late Repair
• After-Window Delivery
• Post-Window Support
• Delayed Relief
• Missed Delivery Window
• Too-Late Delivery

Legacy source preserved:

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

15. Minimal Entry Version

Definition: Late Delivery occurs when needed resource, support, payment, repair, authority, information, care, capacity, attention, intervention, or relief arrives after the valid window of use has narrowed, closed, or become more costly, causing otherwise useful delivery to lose value, compound hidden debt, or fail to restore the affected node.

Signature:

need present
delivery delayed
latency↑
viability↓
repair cost↑
original delivery value↓
H↑

Restoration direction:

• name the original need
• name the valid window
• measure the delay
• identify causes of delay
• map state change during delay
• account for delay debt
• reassess current need
• update the delivery
• repair secondary harms
• restore timing feedback
• reduce future latency
• install timing gates
• validate local coherence
• preserve audit trail

16. Machine-Readable Summary

failure_mode:
  id: "FM-ECO-012"
  name: "Late Delivery"
  family: "Economy"
  production_treatment: "Standalone Entry"
  legacy_ids:
    - "FM-ECOX-004"
  parent_modes:
    - "FM-ECO-001 — Under-Delivery"
    - "FM-ECO-007 — Phase Failure"
    - "FM-C-005 — Latency Blindness"
    - "FM-S-006 — Restoration Starvation"
    - "FM-CORE-002 — Hidden Debt Accumulation"
  primary_failure: "Needed delivery arrives after the valid window has narrowed, closed, or become more costly in a way that reduces usable value, compounds hidden debt, or fails to restore the affected node."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ECO-012"
  deprecated_source_ids:
    - "FM-ECOX-004"
  scope_note: "Conceptual and systems-oriented; does not treat delay, waiting, pacing, staging, review, preparation, sequencing, caution, buffering, or gradual delivery as inherently failed."
  aliases:
    - "Late Delivery"
    - "Delayed Delivery"
    - "Delayed Support"
    - "Late Support"
    - "Late Repair"
    - "After-Window Delivery"
    - "Post-Window Support"
    - "Delayed Relief"
    - "Missed Delivery Window"
    - "Too-Late Delivery"
  signature:
    - "need present"
    - "delivery delayed"
    - "latency↑"
    - "viability↓"
    - "repair cost↑"
    - "original delivery value↓"
    - "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:
      - "U3 — Execution"
      - "U4 — Truth"
      - "U5 — Time"
      - "U6 — Field"
      - "U7 — Memory"
      - "U8 — Environment"
  state_variables:
    - "Τ"
    - "Φ"
    - "R"
    - "H"
    - "K"
    - "Au"
    - "Ψ"
    - "Λ"
    - "Γ"
    - "O"
    - "D"
    - "G"
    - "BΣ"
  first_gate_failure: "Timing Gate"
  restoration:
    - "Delivery Window Audit"
    - "Late Debt Accounting"
    - "Timing Recalibration"
    - "Repair Window Restoration"
    - "Emergency Viability Support"
    - "Backlog Reduction"
    - "Delayed Burden Compensation"
    - "Phase Fit Repair"
    - "Restoration Capacity Scaling"
    - "Local Coherence Restoration"