1. Short Definition

Scaling Failure Signature is the diagnostic pattern indicating that a system is increasing output, reach, power, or performance while losing coherence-supporting capacity.

The system looks more successful while becoming less viable.

2. Canonical Pattern

Φ↑
O↓
H↑
ι↑
Au↓
µᵢ↓
BΣ↓
K↓
R insufficient
𝓓↓
τ_m↑
ε appears late

Expanded:

performance / power / reach↑
while
coherence support capacity↓
⇒ pseudo-scaling
⇒ hidden debt↑
⇒ late visible failure risk↑

Plain form:

The system is doing more while becoming less able to remain coherent.

3. Mechanic Description

SCALE-073 gives the negative diagnostic profile for scaling.

It is the pattern to look for when growth, performance, or expansion may be hiding degradation.

A system may appear to scale because:

• output increases
• revenue increases
• user count rises
• model performance improves
• compliance metrics improve
• incidents appear lower
• throughput rises
• stability appears stronger
• authority expands
• reach increases
• speed improves

But beneath that surface, the system may be losing:

• auditability
• slack
• boundary integrity
• meaning integrity
• restoration capacity
• recurrence control
• ring-down
• cross-scale coherence
• trust
• legitimacy
• adaptive variety

This is the profile of pseudo-scaling.

The most dangerous version occurs when visible error remains low while hidden debt rises. That creates a false sense of stability until late-stage visible failure appears.

SCALE-073 is used as a red-flag pattern when a system is scaling in appearance but degrading in structure.

4. UTS Variable Mapping

5. Diagnostic Questions

1. Is performance rising while coherence falls?
2. Is hidden debt increasing?
3. Is auditability declining?
4. Is slack being consumed?
5. Are boundaries weakening or becoming brittle?
6. Is meaning being replaced by throughput or control?
7. Is restoration capacity lagging behind load?
8. Is ring-down worsening?
9. Is recurrence increasing?
10. Is visible error low only because the system is suppressing or exporting failure?

6. Failure Signatures

1. Performance-Coherence Split

Φ↑ while O↓

The system looks more successful while becoming less coherent.

2. Hidden Debt Rise

Scale↑ + H↑

Expansion increases deferred burden.

3. Auditability Decline

complexity↑ while Au_eff↓

The system becomes harder to inspect.

4. Slack Collapse

K↓ / σ↓ while demand↑

The system loses choice and repair margin.

5. Late Visible Failure

H↑ + ε low ⇒ ε spike late

Visible failure appears after hidden debt accumulates.

7. Related Failure Modes

• pseudo-scaling
• performance-coherence divergence
• hidden debt propagation
• silent extraction
• auditability collapse
• compression depth collapse
• meaning collapse
• restoration starvation
• overcoupling
• boundary brittleness
• late visible failure

8. Related Diagnostics

9. Restoration Implications

If SCALE-073 is active, restoration requires pausing or bounding scale until support capacities recover.

Required actions:

1. Stop treating Φ growth as proof of scaling success.
2. Identify which support capacities are declining.
3. Reduce load, gain, or coupling where necessary.
4. Restore auditability.
5. Rebuild slack.
6. Repair boundaries.
7. Increase restoration capacity.
8. Reconnect performance to meaning and coherence.
9. Track hidden debt and recurrence.
10. Resume scaling only after failure signature reverses.

Core restoration rule:

Reverse the failure signature before resuming scale.

10. Compact Registry Entry

id: SCALE-073
name: "Scaling Failure Signature"
family: "SCALE-M — Scaling Diagnostics and Tests"
type: "scaling-failure-diagnostic-profile"
status: "draft-ready"
short_definition: "Scaling Failure Signature indicates that a system is increasing output, reach, power, or performance while losing coherence-supporting capacity."
canonical_pattern: "Φ↑; O↓; H↑; ι↑; Au↓; µᵢ↓; BΣ↓; K↓; R insufficient; 𝓓↓; τ_m↑; ε appears late"
failure_signature: "performance/power/reach↑ while coherence support capacity↓ ⇒ pseudo-scaling + hidden debt↑ + late visible failure risk↑"
primary_variables:
  - O
  - H
  - ε
  - ι
  - Au
  - µᵢ
  - BΣ
  - K
  - R
  - Φ
primary_diagnostics:
  - Φ_trend
  - O_trend
  - H_trend
  - ι
  - Au_eff
  - µᵢ
  - BΣ
  - K
  - σ(t)
  - R_eff
  - 𝓓(t)
  - τ_m
  - ε_late
related_failure_modes:
  - pseudo_scaling
  - performance_coherence_divergence
  - hidden_debt_propagation
  - silent_extraction
  - auditability_collapse
  - compression_depth_collapse
  - meaning_collapse
  - restoration_starvation
  - overcoupling
  - boundary_brittleness
restoration_implication: "Pause or bound scale, reduce load/gain/coupling, restore auditability, slack, boundaries, meaning, and restoration capacity, and resume scaling only after the failure signature reverses."

11. One-Line Canon

Scaling is failing when the system becomes more powerful while becoming less coherent, less auditable, less repairable, and less able to settle.