1. Short Definition

Capacity Collapse Under Compression occurs when amplified load exceeds effective restoration capacity while slack is too low to absorb the mismatch.

At this threshold, adding more control, demand, speed, or pressure worsens outcomes.

2. Canonical Pattern

Load × Gain > R_eff ∧ K≈0 ⇒ control worsens collapse

Expanded:

Amplified burden > usable repair capacity
+
slack near zero
⇒ restoration failure
⇒ compression cascade
⇒ coherence decline

Plain form:

When a system has no slack and cannot repair the load it carries, pushing harder accelerates collapse.

3. Mechanic Description

SCALE-023 names the compression threshold where ordinary performance demands become destructive.

A system can often absorb temporary overload if it has slack.

A system can sometimes absorb high load if gain is low.

A system can sometimes handle high gain if load is low.

But when:

• load is high,
• gain is high,
• restoration capacity is insufficient,
• and slack is near zero,

the system loses room to recover.

At that point, more demand does not produce better performance. More control does not produce restoration. More urgency does not produce coherence. More enforcement does not solve capacity failure.

It worsens compression.

This applies across many domains:

• biology: increased demand before recovery capacity returns
• institutions: more caseload without repair capacity
• AI: higher deployment pressure before auditability and correction scale
• economy: more growth pressure under circulation breakdown
• security: more surveillance without restoration
• governance: more enforcement under legitimacy collapse
• operations: higher throughput under exhausted teams

SCALE-023 is the operational point where the right move is not “try harder.”

The right move is to reduce load, reduce gain, restore slack, and rebuild capacity.

4. UTS Variable Mapping

5. Diagnostic Questions

1. Is amplified load greater than usable restoration capacity?
2. Is slack near zero?
3. Are demands increasing after repair capacity has failed?
4. Is control being added instead of load reduction?
5. Is the system still expected to perform normally while compressed?
6. Are boundaries failing under overload?
7. Is auditability declining because capacity is exhausted?
8. Are recurrence and hidden debt increasing?
9. Is urgency being used to justify more pressure?
10. Would reducing load improve coherence more than adding control?

6. Failure Signatures

1. Restoration Threshold Failure

Load × Gain > R_eff

The system cannot repair at the rate burden is applied.

2. Zero-Slack Condition

K≈0 or σ≈0

The system has no buffer for adaptation or recovery.

3. Control Worsens Collapse

control↑ under K≈0 ⇒ compression↑ ⇒ O↓

Added control increases pressure.

4. Boundary Failure Under Load

Load↑ + K≈0 ⇒ BΣ failure

Boundaries harden, leak, or become selectively invalid.

5. Late Error Spike

H↑ + K≈0 ⇒ ε spike

Hidden debt becomes visible once buffers fail.

7. Related Failure Modes

• capacity collapse
• restoration starvation
• compression cascade
• control-density spiral
• burnout-equivalent structural exhaustion
• boundary failure
• auditability collapse
• late visible error
• emergency normalization
• pseudo-performance
• recurrence lock

8. Related Diagnostics

9. Restoration Implications

If SCALE-023 is active, restoration must prioritize load reduction and slack regeneration before further performance demand.

Required actions:

1. Stop adding pressure as the default response.
2. Reduce load.
3. Reduce gain and amplification.
4. Restore slack.
5. Stabilize boundaries.
6. Rebuild restoration capacity.
7. Restore auditability after overload begins to settle.
8. Avoid adding complexity during collapse.
9. Validate ring-down before resuming normal demand.
10. Resume scaling only after R_eff exceeds Load × Gain with slack restored.

Core restoration rule:

When slack is gone and restoration is exceeded, pressure reduction is repair.

10. Compact Registry Entry

id: SCALE-023
name: "Capacity Collapse Under Compression"
family: "SCALE-D — Compression and Depth Collapse Mechanics"
type: "compression-threshold-rule"
status: "draft-ready"
short_definition: "Capacity Collapse occurs when amplified load exceeds effective restoration capacity while slack is too low to absorb the mismatch."
canonical_pattern: "Load × Gain > R_eff ∧ K≈0 ⇒ control worsens collapse"
failure_signature: "Amplified burden > usable repair capacity + slack near zero ⇒ restoration failure + compression cascade + coherence decline"
primary_variables:
  - O
  - H
  - ε
  - ι
  - Au
  - µᵢ
  - BΣ
  - K
  - R
  - Φ
primary_diagnostics:
  - Load
  - Gain
  - R_eff
  - K
  - σ(t)
  - Cv(t)
  - BΣ
  - Au_eff
  - H
  - ε
  - 𝓓(t)
related_failure_modes:
  - capacity_collapse
  - restoration_starvation
  - compression_cascade
  - control_density_spiral
  - structural_exhaustion
  - boundary_failure
  - auditability_collapse
  - late_visible_error
  - emergency_normalization
  - recurrence_lock
restoration_implication: "Reduce load and gain, restore slack, stabilize boundaries, rebuild restoration capacity, and delay further scaling until R_eff exceeds Load × Gain."

11. One-Line Canon

When amplified load exceeds restoration and slack is gone, pushing harder becomes part of the collapse.