1. Short Definition

Restoration Scaling Test evaluates whether a system’s effective repair capacity is sufficient for the burden created by scale.

A system is not scaling coherently if the damage, load, or hidden debt it creates grows faster than its ability to restore.

2. Canonical Pattern

R_eff > Load × Gain

Expanded:

scale pressure↑
+
effective restoration capacity scales faster than amplified burden
⇒ repair remains viable
⇒ hidden debt remains bounded
⇒ coherence can stabilize

Failure pattern:

R_eff < Load × Gain ⇒ restoration starvation + H↑ + O↓

Plain form:

Scaling is only viable when repair capacity grows with burden.

3. Mechanic Description

SCALE-078 operationalizes the restoration side of scaling.

As systems scale, restoration demand rises because there are more:

• users
• cases
• failures
• edge conditions
• conflicts
• boundary crossings
• classifications
• decisions
• appeals
• downstream effects
• hidden debt pathways
• affected nodes
• recurrence risks

A system may expand execution, power, automation, enforcement, or reach while failing to expand restoration.

This creates restoration starvation.

Restoration capacity includes the ability to:

• detect harm
• receive feedback
• trace causality
• repair damage
• reduce hidden debt
• restore boundaries
• correct classifications
• compensate affected nodes
• reduce recurrence
• improve ring-down
• update memory
• prevent repeated failure

The test asks whether R_eff — usable restoration capacity under actual conditions — exceeds the burden produced by load and gain.

The important term is effective restoration capacity.

A system may claim restoration exists, but if repair is inaccessible, delayed, underfunded, symbolic, non-auditable, or too weak for the burden, then R_eff is low.

4. UTS Variable Mapping

5. Diagnostic Questions

1. What restoration burden does scale create?
2. Does restoration capacity increase with load?
3. Does restoration capacity increase with gain?
4. Is repair accessible to affected nodes?
5. Is restoration material, structural, and time-validated, or only symbolic?
6. Is hidden debt decreasing after repair?
7. Are recurrence patterns weakening?
8. Does ring-down improve after perturbation?
9. Are boundaries repaired after failure?
10. Is R_eff greater than Load × Gain under actual conditions?

6. Failure Signatures

1. Restoration Starvation

R_eff < Load × Gain

The system cannot repair at the rate burden is created.

2. Symbolic Restoration

repair_claim↑ while H not reduced

Restoration language appears without debt reduction.

3. Recurrence After Repair

R_claimed↑ while τ_m↑

The system claims repair while patterns repeat.

4. Appeal / Repair Access Failure

affected_node_cost↑ + repair_access↓

Affected nodes cannot access restoration.

5. Boundary Repair Failure

BΣ damaged + recoupling↑ ⇒ recurrence↑

The system reconnects before boundary repair holds.

7. Related Failure Modes

• restoration starvation
• pseudo-restoration
• symbolic repair
• recurrence lock
• appeal collapse
• hidden debt accumulation
• boundary failure recurrence
• capacity collapse
• silent extraction
• legitimacy decay
• pressure before repair hazard

8. Related Diagnostics

9. Restoration Implications

If SCALE-078 fails, scaling must pause or become bounded until restoration capacity catches up.

Required actions:

1. Measure actual restoration burden.
2. Distinguish claimed R from effective R.
3. Reduce load or gain where repair is overwhelmed.
4. Increase repair access.
5. Increase restoration staffing, funding, tooling, or authority.
6. Restore auditability of repair pathways.
7. Repair boundaries before recoupling.
8. Track hidden debt reduction, not only repair activity.
9. Validate recurrence reduction.
10. Resume scaling only when R_eff exceeds Load × Gain with margin.

Core restoration rule:

Do not scale faster than the system can repair.

10. Compact Registry Entry

id: SCALE-078
name: "Restoration Scaling Test"
family: "SCALE-M — Scaling Diagnostics and Tests"
type: "restoration-capacity-diagnostic-test"
status: "draft-ready"
short_definition: "Restoration Scaling Test evaluates whether effective repair capacity is sufficient for the burden created by scale."
canonical_pattern: "R_eff > Load × Gain"
failure_signature: "R_eff < Load × Gain ⇒ restoration starvation + H↑ + O↓"
primary_variables:
  - O
  - H
  - ε
  - ι
  - Au
  - µᵢ
  - BΣ
  - K
  - R
  - Φ
primary_diagnostics:
  - R_eff
  - Load
  - Gain
  - H_repaired
  - H_remaining
  - repair_access_ratio
  - affected_node_cost
  - τ_m
  - 𝓓(t)
  - BΣ_repair_status
  - Au_repair
related_failure_modes:
  - restoration_starvation
  - pseudo_restoration
  - symbolic_repair
  - recurrence_lock
  - appeal_collapse
  - hidden_debt_accumulation
  - boundary_failure_recurrence
  - capacity_collapse
  - silent_extraction
restoration_implication: "Pause or bound scaling, distinguish claimed from effective restoration, reduce load/gain, increase repair access and capacity, and resume scaling only after recurrence and hidden debt decline."

11. One-Line Canon

A system is not scaling coherently if its repair capacity grows slower than the burden it creates.