1. Short Definition
Restoration Before Scaling means that repair must precede expansion when hidden debt, boundary damage, auditability loss, or restoration deficits are active.
Scaling an unrepaired system multiplies the unrepaired pattern.
2. Canonical Pattern
H unresolved + Scale↑ ⇒ H amplificationExpanded:
hidden debt / boundary damage / audit loss / restoration deficit
+
scope / load / coupling / velocity / gain↑
⇒ failure pathways↑
⇒ repair burden↑
⇒ coherence risk↑Plain form:
Repair before expansion.
3. Mechanic Description
SCALE-057 is the restoration-side counterpart to earlier pressure-before-repair rules.
It establishes the clean sequencing requirement:
- restore,
- validate,
- then scale.
A system may be tempted to scale because scaling appears to solve pressure:
- more users
- more automation
- more throughput
- more staff
- more enforcement
- more reach
- more authority
- more funding
- more integration
- more speed
But if the original system contains unresolved hidden debt, the added scale spreads the damaged pattern.
This can turn a local problem into a systemic one.
Restoration before scaling applies when a system has:
- unresolved recurrence
- known hidden debt
- weak auditability
- damaged boundaries
- low slack
- insufficient repair capacity
- misaligned incentives
- unresolved legitimacy debt
- recurring misclassification
- pseudo-coherent stability
- unresolved coupling failure
Scaling is not forbidden.
It is sequenced after support capacity is restored.
4. UTS Variable Mapping
| Variable | Role in SCALE-057 |
|---|---|
| O | Must be stabilized before expansion |
| H | Must be reduced or bounded before scale |
| ε | Visible error may be low while hidden debt remains |
| ι | Rises when scaling appears successful despite unrepaired debt |
| Au | Must be restored before scale can be trusted |
| µᵢ | Meaning / legitimacy must be repaired before broader consequence |
| BΣ | Boundary integrity must be restored before expanded coupling |
| K | Slack must be regenerated before increased load |
| R | Restoration capacity must scale before burden scales |
| Φ | Expansion pressure often drives premature scaling |
5. Diagnostic Questions
- What is being scaled?
- What remains unrepaired?
- Is hidden debt reduced or merely contained?
- Are boundaries restored?
- Is auditability sufficient?
- Is restoration capacity higher than before?
- Is slack sufficient for the next scale increase?
- Has recurrence decreased?
- Has ring-down improved?
- Is scaling being used to avoid restoration?
6. Failure Signatures
1. Expansion of Unrepaired Pattern
H unresolved + Scale↑ ⇒ H propagation↑The unrepaired failure spreads through the expanded system.
2. Recurrence After Scale
Scale↑ + τ_m↑ ⇒ restoration incompleteThe same pattern returns after expansion.
3. Boundary Damage Multiplied
BΣ damaged + Coupling↑ ⇒ leakage / capture / recurrence↑Damaged boundaries become more consequential.
4. Auditability Deficit Under Expansion
Scale↑ while Au_eff insufficient ⇒ hidden debt↑The system becomes larger than it can inspect.
5. Repair Capacity Lag
Load↑ faster than R_eff↑ ⇒ restoration starvationBurden grows faster than repair.
7. Related Failure Modes
- restoration-before-scaling violation
- hidden debt propagation
- pseudo-scaling
- recurrence lock
- boundary failure amplification
- auditability collapse
- restoration starvation
- local-global divergence
- silent extraction
- pressure before repair hazard
- standardized incoherence
8. Related Diagnostics
| Diagnostic | Use |
|---|---|
| H | Existing hidden debt |
| τ_m | Recurrence after restoration or scale |
| 𝓓(t) | Ring-down after disturbance |
| BΣ | Boundary repair status |
| Au_eff | Auditability before scale |
| R_eff | Restoration capacity |
| K / σ(t) | Slack before expansion |
| Load | Added burden |
| Gain | Amplification of burden |
| O_trend | Coherence trend before/after scale |
9. Restoration Implications
If SCALE-057 is active, restoration requires pausing expansion until repair is validated.
Required actions:
- Stop or slow further scale pressure.
- Identify unresolved hidden debt.
- Repair origin-layer causes.
- Restore boundary integrity.
- Restore auditability.
- Rebuild slack and restoration capacity.
- Validate ring-down.
- Track recurrence.
- Resume scaling only in bounded increments.
- Re-test coherence after each increment.
Core restoration rule:
Do not scale what has not been repaired.10. Compact Registry Entry
id: SCALE-057
name: "Restoration Before Scaling"
family: "SCALE-K — Transition and Restoration Scaling Mechanics"
type: "restoration-expansion-sequencing-rule"
status: "draft-ready"
short_definition: "Repair must precede expansion when hidden debt, boundary damage, auditability loss, or restoration deficits are active."
canonical_pattern: "H unresolved + Scale↑ ⇒ H amplification"
failure_signature: "hidden debt/boundary damage/audit loss/restoration deficit + scope/load/coupling/velocity/gain↑ ⇒ failure pathways↑ + repair burden↑ + coherence risk↑"
primary_variables:
- O
- H
- ε
- ι
- Au
- µᵢ
- BΣ
- K
- R
- Φ
primary_diagnostics:
- H
- τ_m
- 𝓓(t)
- BΣ
- Au_eff
- R_eff
- K
- σ(t)
- Load
- Gain
- O_trend
related_failure_modes:
- restoration_before_scaling_violation
- hidden_debt_propagation
- pseudo_scaling
- recurrence_lock
- boundary_failure_amplification
- auditability_collapse
- restoration_starvation
- local_global_divergence
- standardized_incoherence
restoration_implication: "Pause expansion, repair origin-layer debt, restore boundaries/auditability/slack/restoration capacity, validate ring-down and recurrence reduction, then scale in bounded increments."11. One-Line Canon
Scaling before restoration turns unrepaired failure into expanded structure.