1. Short Definition

U0 Substrate Load Rule means that a system cannot scale coherently beyond the capacity of its underlying substrate.

Higher-layer growth fails when the base layer cannot carry the load.

2. Canonical Pattern

U0 capacity insufficient ⇒ higher-layer scale fails

Expanded:

substrate load↑
+
U0 capacity insufficient
⇒ execution stress↑
⇒ boundary strain↑
⇒ restoration burden↑
⇒ coherence risk↑

Plain form:

No system scales beyond the base that carries it.

3. Mechanic Description

SCALE-063 begins the U-layer scaling sequence.

U0 is the substrate layer: the physical, energetic, infrastructural, biological, material, or computational base that supports the rest of the system.

A system may attempt to scale at higher layers:

• more execution
• more classification
• more coordination
• more memory
• more governance
• more automation
• more users
• more throughput
• more coupling
• more symbolic or institutional complexity

But if U0 cannot support the load, higher-layer scaling becomes unstable.

Examples:

• AI models scale beyond compute, energy, monitoring, or infrastructure capacity.
• Biological performance demand exceeds substrate recovery or tissue capacity.
• Institutions expand responsibilities beyond physical staffing or operational base.
• Economies scale activity beyond ecological or material substrate.
• Security systems increase surveillance or response load beyond infrastructure.
• Governance systems add policy without the substrate to administer it.
• Digital platforms scale users beyond reliability, moderation, or support capacity.

U0 failure can appear at higher layers first.

A U3 execution problem may actually be a U0 substrate constraint.

A U5 coordination failure may arise from infrastructure limitations.

A U6 coherence problem may arise because the substrate cannot support the field demand.

This rule prevents systems from trying to solve substrate failure with higher-layer messaging, compliance, or control.

4. UTS Variable Mapping

5. Diagnostic Questions

1. What substrate carries the system?
2. Is U0 capacity sufficient for the proposed scale?
3. Is higher-layer failure actually caused by substrate overload?
4. Is the system treating base-layer depletion as an execution problem?
5. Are maintenance and recovery being deferred?
6. Is infrastructure, tissue, energy, compute, staffing, or material base saturated?
7. Is visible performance being maintained by consuming substrate reserves?
8. Can the substrate recover after load?
9. Is substrate auditability sufficient?
10. Should scale pause until U0 is reinforced?

6. Failure Signatures

1. Substrate Saturation

U0 load > U0 capacity

The base layer cannot carry demand.

2. Higher-Layer Misdiagnosis

U0 failure misread as U3 / U4 / U5 failure

The system treats substrate overload as execution, classification, or coordination error.

3. Deferred Maintenance Debt

maintenance deferred + load↑ ⇒ H_U0↑

Base-layer debt accumulates.

4. Performance Through Depletion

Φ↑ while substrate reserves↓

The system performs by consuming its base.

5. Restoration Failure

U0 damaged + R_eff insufficient ⇒ recurrence↑

Recovery cannot occur because the substrate remains damaged.

7. Related Failure Modes

• substrate overload
• deferred maintenance debt
• infrastructure brittleness
• biological depletion
• compute/resource saturation
• higher-layer misdiagnosis
• restoration starvation
• silent extraction
• capacity collapse
• performance-coherence divergence
• late visible failure

8. Related Diagnostics

9. Restoration Implications

If SCALE-063 is active, restoration must reinforce or repair the substrate before higher-layer scaling resumes.

Required actions:

1. Identify the true substrate layer.
2. Measure U0 load against U0 capacity.
3. Pause or reduce higher-layer demand.
4. Repair substrate damage.
5. Reduce deferred maintenance debt.
6. Restore substrate reserves.
7. Increase substrate auditability.
8. Reclassify higher-layer symptoms that originate in U0.
9. Validate substrate ring-down after load.
10. Resume scaling only when substrate capacity exceeds demand with margin.

Core restoration rule:

Repair the base before scaling what rests on it.

10. Compact Registry Entry

id: SCALE-063
name: "U0 Substrate Load Rule"
family: "SCALE-L — U-Layer Scaling Mechanics"
type: "substrate-scaling-constraint"
status: "draft-ready"
short_definition: "A system cannot scale coherently beyond the capacity of its underlying substrate."
canonical_pattern: "U0 capacity insufficient ⇒ higher-layer scale fails"
failure_signature: "substrate load↑ + U0 capacity insufficient ⇒ execution stress↑ + boundary strain↑ + restoration burden↑ + coherence risk↑"
primary_variables:
  - O
  - H
  - ε
  - ι
  - Au
  - µᵢ
  - BΣ
  - K
  - R
  - Φ
primary_diagnostics:
  - U0_capacity
  - U0_load
  - substrate_reserve_depth
  - maintenance_debt
  - R_U0
  - Au_U0
  - Φ_load
  - ε_U0
  - τ_m
  - 𝓓(t)
related_failure_modes:
  - substrate_overload
  - deferred_maintenance_debt
  - infrastructure_brittleness
  - biological_depletion
  - compute_resource_saturation
  - higher_layer_misdiagnosis
  - restoration_starvation
  - silent_extraction
  - capacity_collapse
restoration_implication: "Reduce higher-layer demand, repair substrate damage, restore reserves, increase U0 auditability, and resume scaling only when substrate capacity exceeds demand with margin."

11. One-Line Canon

A system cannot scale coherently beyond the substrate that carries it.