A system should not expand, deploy, grow, replicate, automate, govern, monetize, institutionalize, or increase influence while its hidden debt, broken boundaries, weak auditability, or insufficient restoration capacity remain unresolved. Scale does not neutralize unrepaired debt. It multiplies it.

1. Formal Definition

The Restoration Before Scaling Law states that scaling should not proceed until restoration conditions are present.

Scaling increases coupling, load, velocity, reach, visibility, consequence, recurrence density, and field impact. If the system contains unrepaired hidden debt, boundary damage, weak auditability, pseudo-restoration, unresolved recurrence, insufficient restoration capacity, or legitimacy debt, scaling amplifies those conditions.

This applies to:

AI systems;
institutions;
economies;
archetypes;
governance reforms;
security systems;
biological interventions;
cultural movements;
platforms;
protocols;
organizations;
personal or collective influence fields.

Scaling is not only size increase. It includes increased:

users;
reach;
authority;
automation;
dependency;
speed;
coupling;
replication;
access;
leverage;
symbolic power;
institutional adoption;
market penetration;
biological intervention intensity;
governance scope.

Therefore, restoration must precede scaling when hidden debt, boundary damage, recurrence, or insufficient repair capacity remain active.

2. Canonical Form

Core form:

textScroll

Scale↑ before H↓ + R↑ + Au↑ + BΣ↑ ⇒ H amplification

Expanded form:

textScroll

Scale↑ ∧ (H↑/unrepaired ∨ Au↓ ∨ BΣ↓ ∨ R_eff < Load × Gain ∨ recurrence↑) ⇒ O↓ over scale

Restoration-ready scaling form:

textScroll

H↓ + ι↓ + BΣ stable/↑ + Au↑ + R_eff ≥ Load × Gain + recurrence↓ + Τ proof ⇒ scaling admissible

Failure form:

textScroll

unrepaired system × scale ⇒ hidden debt replication

Related variables:

textScroll

O, H, ε, ι, Au, R, R_eff, BΣ, K, σ, µᵢ, Φ, Λ, ⊗, Γ, Π, ℛ, Θ, Σ, Ψ, Τ, FI, Scale, Load, Gain

Where:

TableScroll

Variable	Meaning in this law
`Scale`	Reach, load, users, dependency, replication, speed, authority, access, or influence
`H`	Hidden debt that becomes amplified or replicated by scaling
`R / R_eff`	Restoration capacity required to repair at expanded scale
`Au`	Auditability required to track scaling effects and debt migration
`BΣ`	Boundary integrity required before coupling increases
`O`	Coherence; should remain stable or improve as scale increases
`ι / Ξ`	Inversion rises when scaling is framed as success while debt expands
`recurrence`	Failure pattern repetition increases when unrepaired loops are replicated
`Load`	Burden introduced by increased scale
`Gain`	Amplification from velocity, visibility, leverage, emotion, technology, power, or recurrence
`K / σ`	Slack / sovereignty required for scaling without burden inversion
`FI`	Feedback integrity required to detect debt amplification
`µᵢ`	Meaning / agent integrity stressed when scale pulls the system away from coherence
`Φ`	Visible success proxy; often rises during scaling despite hidden debt growth
`Γ`	Classifies whether the system is restored enough to scale
`Π`	Controls scale gates, deployment limits, throttles, or containment
`ℛ`	Restoration action required before scaling proceeds
`Θ`	Humility / uncertainty prevents premature scaling claims
`Σ`	Scope of scaling, restoration, boundary, and proof conditions
`Ψ`	Field and affected-node feedback reveals scale effects
`Τ`	Time validation required before, during, and after scale increase
`Λ`	Compatibility must be revalidated at expanded scale
`⊗`	Coupling intensity increases with scaling and may need staged expansion

3. Core Mechanism

The law unfolds because scaling multiplies the current state of the system, including hidden defects.

Coherent scaling pathway

textScroll

system seeks scale
→ hidden debt is audited
→ origin-layer repair occurs
→ boundary integrity is restored
→ restoration capacity is increased
→ auditability and feedback are strengthened
→ recurrence decreases
→ scaling proceeds gradually with temporal proof

Debt-amplifying scaling pathway

textScroll

system seeks scale
→ hidden debt remains
→ scaling increases load / gain / coupling
→ debt replicates across larger field
→ auditability falls behind
→ recurrence expands
→ O declines
→ legitimacy shock or collapse occurs

The core mechanism is:

textScroll

scale multiplies both coherence and unrepaired debt

Detailed mechanism:

A system contains unresolved restoration debt.

Debt may exist as boundary damage, weak auditability, invalid consent, depleted capacity, recurrence loops, legitimacy debt, quiet minimization, pseudo-restoration, or incomplete closure.

The system increases scale.

More users, more load, more reach, more influence, more dependency, more automation, more authority, or more replication enters the field.

Load and gain increase.

The unresolved pattern now has more pathways through which to express, repeat, hide, or compound.

Auditability often becomes harder.

As scale rises, local failures may become harder to trace, attribution becomes diffuse, and feedback latency increases.

Hidden debt migrates or multiplies.

Debt may move to weaker nodes, downstream teams, users, environments, future generations, biological substrates, marginalized fields, or unobserved processes.

Visible success may rise while coherence declines.

Growth, adoption, revenue, reach, compliance, or influence can improve while O degrades.

Rebound appears at scale.

The failure returns as legitimacy shock, systemic fragility, security breach, model failure, chronic instability, extraction, collapse, or forced supersession.

4. When This Law Applies

This law applies whenever a system expands after incomplete restoration.

It is especially important when:

scale resumes after pseudo-restoration;
a product is deployed before repair is time-validated;
an AI system scales users before audit and appeal capacity;
an institution grows after unresolved harm;
a security system expands before boundary repair;
an economy seeks growth while circulation debt remains;
a biological intervention intensifies before recovery capacity returns;
a governance reform expands before legitimacy repair;
a movement grows before boundary, meaning, and accountability structures mature;
a platform automates unresolved classifier or policy failures;
a contract model replicates before consent and exit repair;
a system treats adoption, popularity, revenue, or compliance as proof of restoration.

The law applies strongly when:

textScroll

Scale↑ occurs before H↓ + R_eff↑ + Au↑ + BΣ↑

or when:

textScroll

success proxy growth is used to bypass restoration proof

Typical domains:

TableScroll

Domain	Restoration Before Scaling Expression
AI systems	Models, agents, memory, personalization, moderation, and automation should not scale before auditability, appeal, recurrence reduction, and repair capacity scale.
Security	Security architectures should not expand trust, access, or integration before boundary repair and monitoring capacity.
Institutions	Growth, authority, hiring, reform, or public legitimacy should not expand before hidden debt and accountability failures are repaired.
Medicine / biology	Intervention intensity, exposure, stimulation, or performance demand should not scale before restoration capacity and damping improve.
Economy	Expansion should not occur before circulation, contract validity, exit, and debt conditions are repaired.
Governance	Governance scope should not expand before legitimacy, repair, consequence, and prevention capacity exist.
Culture	Movements should not scale symbolic power before accountability, boundaries, and meaning integrity stabilize.
Restoration	Repair must precede expansion, deployment, reintegration at scale, or renewed growth.

5. When This Law Does Not Apply

This law should not be used to block all growth, deployment, or expansion.

Some scaling is necessary for restoration. A repair process may need more staff, more funding, more infrastructure, wider communication, broader support, or greater visibility to reduce debt.

The distinction is whether scaling supports restoration or bypasses it.

Scaling can be coherent when:

it increases restoration capacity;
it improves auditability;
it reduces hidden debt;
it stabilizes boundaries;
it lowers recurrence;
it increases slack;
it expands repair access;
it is gradual, reversible, and monitored;
it does not replicate the unrepaired failure geometry.

False-positive cases:

TableScroll

Case	Why it is not a violation
Scaling a support team before scaling users	Scale increases restoration capacity
Expanding audit coverage before deployment	Scale improves visibility
Gradual deployment under strict recurrence monitoring	Scaling is conditional and time-validated
Increasing funding for harmed-node repair	Scale supports restoration
Extending a biological intervention slowly after tolerance proof	Scaling follows recovery validation

Important distinction:

Scaling restoration capacity is often necessary. Scaling the unrepaired system is the danger.

6. Diagnostic Signature

Canonical diagnostic:

textScroll

Scale↑ before H↓ + R↑ + Au↑ + BΣ↑ ⇒ H amplification

Warning signature:

textScroll

Scale↑
Φ↑
H unresolved
Au insufficient
BΣ fragile
R_eff < Load × Gain
recurrence untested
⇒ debt amplification risk↑

Common indicators:

TableScroll

Diagnostic	Expected movement	Interpretation
`Scale`	↑	Reach, load, dependency, or influence increases
`H`	unresolved / ↑	Hidden debt is being amplified
`Au`	must ↑	Auditability must scale with reach
`BΣ`	stable / ↑	Boundaries must hold under increased coupling
`R_eff`	must ≥ `Load × Gain`	Restoration capacity must scale before or with load
`recurrence`	↓ / stable-low	Failure loops should not replicate under scale
`𝓓`	stable / ↑	Damping should hold as scale increases
`K / σ`	stable / ↑	Slack should not be consumed by growth
`O`	stable / ↑	Coherence should hold under expanded conditions
`ι / Ξ`	↓	Inversion should not rise through success framing
`FI`	intact / ↑	Feedback must remain strong enough to detect scale effects
`µᵢ`	stable / ↑	Meaning integrity should not collapse under growth pressure
`Φ`	not sufficient	Growth metrics cannot prove readiness

Additional diagnostics:

TableScroll

Diagnostic	Use
Restoration Readiness	Tests whether debt, boundary, capacity, and recurrence conditions support scale
Scaling Readiness	Tests whether the system can expand without debt amplification
Hidden Debt	Detects unrepaired conditions before scale
Effective Restoration Capacity	Tests whether repair capacity can scale with load
Effective Auditability	Detects whether visibility keeps pace with scale
Boundary Integrity	Tests whether membranes can hold increased coupling
Recurrence	Reveals whether scaling replicates the failure pattern
Coherence Trajectory	Tests whether `O` holds under expansion
Load	Measures burden added by scale
Gain	Measures amplification through speed, leverage, visibility, or recurrence
Temporal Proof	Validates readiness before larger expansion

7. Failure Pattern

If ignored, this law produces debt amplification through scale.

General failure pathway:

textScroll

unrepaired debt remains
→ scale increases
→ load and gain rise
→ auditability falls behind
→ recurrence replicates
→ debt migrates / multiplies
→ O declines
→ legitimacy shock / collapse / supersession pressure

Common failure modes:

Scaling Hidden Debt — unresolved debt expands with the system.
Unrepaired Expansion — growth occurs before restoration.
Debt Amplification — load and gain multiply the cost of prior failure.
Pseudo-Restoration Scaling — visible repair claims enable expansion while debt remains.
Premature Deployment — deployment occurs before time proof.
Premature Growth — growth metrics override repair readiness.
Legitimacy Decay — authority erodes when scaled debt becomes visible.
Observability Collapse — auditability cannot track scaled effects.
Hidden Debt Migration — debt shifts to weaker or downstream nodes.
Recurrence Amplification — repeated failure patterns spread across scale.
Boundary Failure at Scale — fragile membranes fail under expanded coupling.
Capacity Exhaustion — repair capacity cannot keep up.
Delayed Collapse — failure appears after scale masks causal origin.

Compact failure signature:

textScroll

unrepaired H × Scale↑ ⇒ systemic debt amplification

8. Restoration Implications

Restoration must gate scaling.

The first scaling question is not:

textScroll

Can this system grow?

The first scaling question is:

textScroll

What debt, boundary, audit, recurrence, and capacity conditions will scale with it?

Restoration priorities:

Audit hidden debt before scaling.
Repair origin-layer failures.
Reduce inversion and pseudo-restoration risk.
Restore boundary integrity.
Increase restoration capacity before increasing load.
Scale auditability with reach.
Regenerate slack.
Validate recurrence reduction.
Use staged, reversible scaling.
Time-validate each scaling phase before expanding further.

Relevant restoration arcs:

TableScroll

Restoration Arc	Why it applies
Restoration Before Scaling Gate	Prevents expansion before repair readiness
Hidden Debt Reduction	Reduces debt before it can be multiplied
Origin-Layer Repair	Prevents source failure from replicating
Boundary Reconstitution	Ensures membranes can hold expanded coupling
Restoration Capacity Rebuild	Ensures repair capacity scales with load
Auditability Restoration	Keeps scaled effects visible and traceable
Slack Regeneration	Protects sovereignty and capacity under growth
Controlled Decoupling	Reduces coupling while repair occurs
Temporal Validation	Confirms each scaling stage holds
Recurrence Reduction	Prevents failure pattern replication
Closure Stack Completion	Ensures prior failures are not quietly carried into scale

Minimal restoration sequence:

textScroll

audit H / Au / BΣ / R_eff / recurrence
→ repair origin debt
→ rebuild R_eff and Au
→ validate BΣ and recurrence over Τ
→ scale gradually with rollback
→ monitor O under load

Temporal validation requirement:

textScroll

H↓
ι↓
BΣ stable or rising
Au scales with reach
FI intact
R_eff ≥ Load × Gain
recurrence↓
𝓓↑ or stable
K / σ stable or rising
O stable or rising under expanded load

9. Design Rule

Do not scale an unrepaired system.

Operational design requirements:

Define what counts as scale.
Define restoration readiness before scaling.
Require hidden debt audit before expansion.
Require boundary repair before increased coupling.
Require auditability to scale with reach.
Require restoration capacity to scale with load.
Require recurrence testing before deployment or growth.
Use staged, reversible scaling.
Track affected-node burden after scale.
Do not use growth metrics as repair proof.
Pause scaling when hidden debt rises.
Reopen restoration when recurrence appears.

Avoid:

scaling after symbolic closure;
scaling after pseudo-restoration;
scaling after quiet minimization;
deploying before time proof;
expanding influence before boundary repair;
increasing automation before audit and rollback;
growing users faster than support and repair capacity;
increasing authority faster than legitimacy and consequence;
increasing intervention intensity before tolerance;
expanding contracts before consent and exit repair;
treating popularity, revenue, adoption, or compliance as restoration proof.

10. Cross-Scale Expressions

TableScroll

Scale / Layer	Expression of the Law
U0 — Substrate	Physical, biological, infrastructural, or hardware scaling amplifies substrate defects.
U1 — Energy / capacity	Scaling increases load and consumes slack unless capacity grows first.
U2 — Boundary / interface	Increased coupling stresses membranes, consent, access, permissions, and exits.
U3 — Process / execution	Workflows that barely function locally fail when replicated broadly.
U4 — Classification / claim	Success claims may hide scaled debt if not validated against field effects.
U5 — Time / delay	Scale increases latency, delayed effects, and temporal audit difficulty.
U6 — Field effect	Broader field impact reveals whether coherence holds beyond local conditions.
U7 — Recurrence / memory	Unrepaired recurrence loops replicate across scaled nodes.
U8 — Environment / forcing	Scaling changes environment and may introduce new forcing not present locally.

11. Examples

Example A — AI Deployment Before Restoration

Scenario:

An AI system shows repeated appeal failures and classifier recurrence. The provider improves public messaging and benchmark results, then scales deployment to more users without increasing auditability, appeal capacity, or recurrence repair.

Law expression:

textScroll

Scale_AI↑ before H↓ + Au↑ + R_eff↑ ⇒ AI debt amplification

Interpretation:

Deployment multiplies the unresolved failure pattern. More users means more recurrence, more harmed-node burden, and more legitimacy debt.

Example B — Institutional Growth After Unresolved Harm

Scenario:

An institution expands programs, staff, influence, or public authority after an internal harm process was quietly minimized and boundary repair remains incomplete.

Law expression:

textScroll

institutional Scale↑ after quiet minimization ⇒ L_debt↑

Interpretation:

Growth carries the unresolved debt into a larger field. The institution may look successful while future legitimacy shock accumulates.

Example C — Security Integration Before Boundary Repair

Scenario:

A platform expands integrations after a breach, but access boundaries, credential hygiene, logging, and recurrence pathways remain fragile.

Law expression:

textScroll

integration Scale↑ + BΣ_security fragile ⇒ breach recurrence risk↑

Interpretation:

More integrations multiply the attack surface and spread the unrepaired boundary failure.

Example D — Biological Intervention Scaling

Scenario:

A biological system begins to recover, then rapidly increases exercise, dietary complexity, supplements, stimulation, and workload before damping, tolerance, and restoration capacity are stable.

Law expression:

textScroll

intervention Scale↑ before R_eff_bio↑ + 𝓓↑ ⇒ recurrence↑

Interpretation:

The interventions may be useful, but scaling them before recovery capacity stabilizes can recreate the basin.

Example E — Economic Expansion Before Circulation Repair

Scenario:

A company, market, or economy pushes growth while debt burden, exit costs, labor depletion, resource extraction, and circulation fragility remain unresolved.

Law expression:

textScroll

economic Scale↑ before circulation repair ⇒ extraction amplification

Interpretation:

Growth multiplies the existing circulation defect. Profit may rise while coherence declines.

Example F — Cultural Movement Scaling

Scenario:

A movement grows rapidly through symbolic power, identity charge, and visibility, but lacks boundary clarity, accountability, repair pathways, and recurrence prevention.

Law expression:

textScroll

symbolic Scale↑ before BΣ / Au / ℛ ⇒ archetypal drift risk↑

Interpretation:

The movement’s influence expands faster than its restoration infrastructure. Hidden debt can become basin lock, fragmentation, or legitimacy collapse.

12. Relationship to Nearby Laws

TableScroll

Related Law	Relationship
LAW-006 — Time Validation Law	Scaling should wait for time-validated repair
LAW-007 — Ring-Down Truth Law	Scaling should not proceed if damping remains poor
LAW-008 — Recurrence Validation Law	Recurrence reduction is required before expansion
LAW-010 — Hidden Debt Accumulation Law	Scaling multiplies accumulated debt
LAW-011 — Hidden Debt Return Law	Scaled systems return debt at larger magnitude
LAW-012 — Error Lag Law	Scaled debt may appear after delay
LAW-013 — Auditability-Debt Law	Auditability must scale with system reach
LAW-018 — Scaling as Coherence Under Pressure	LAW-073 is a restoration gate for scaling pressure
LAW-019 — Coupling Outpaces Components Law	Scaling increases coupling before components may be ready
LAW-020 — Bandwidth Threshold Law	Scaling increases signal load and bandwidth demand
LAW-021 — Coherence-Preserving Scaling Law	Scaling is coherent only when restoration conditions preserve `O`
LAW-022 — Integration Capacity Law	Scaling requires integration capacity
LAW-023 — Restoration Capacity Load Law	Repair capacity must scale with load
LAW-030 — Slack Sovereignty Law	Scaling without slack becomes extraction
LAW-031 — Observability Collapse Law	Scale can reduce effective observability
LAW-032 — Hidden Debt Migration Law	Scaled debt may migrate to weaker nodes
LAW-033 — Scale Accelerates Intention Law	Scaling amplifies unresolved intent and hidden structure
LAW-034 — Power–Meaning Collapse Law	Power scaling without restoration can degrade meaning integrity
LAW-047 — Controlled Decoupling Law	Decoupling may be needed before scaling can resume
LAW-050 — Control-Restoration Separation Law	Controlling symptoms is not enough to scale safely
LAW-052 — Stability Proof Law	Scaling requires stability proof under perturbation
LAW-061 — Restoration Sequencing Law	Scaling comes after restoration dependencies
LAW-062 — Restoration Is Not the Inverse of Failure Law	Scaling cannot be justified by simple reversal or rollback
LAW-063 — Origin-Layer Repair Law	Source-layer debt must be repaired before replication
LAW-064 — Restoration Debt Reduction Law	Hidden debt must decrease before scaling
LAW-065 — Pseudo-Restoration Law	Scaling pseudo-restoration amplifies false repair
LAW-066 — Restoration Capacity Sufficiency Law	`R_eff` must exceed `Load × Gain` before scale
LAW-067 — Temporal Proof Law	Repair must hold over time before scale
LAW-068 — Boundary-First Restoration Law	Boundary repair must precede increased coupling
LAW-069 — Closure Stack Law	Closure stack should be complete before scale
LAW-070 — Reintegration Membrane Law	Reintegration should be validated before expanded access
LAW-071 — No Forced Forgiveness Law	Forgiveness cannot be used to authorize scaling
LAW-072 — Quiet Minimization Debt Law	Scaling after minimization issues debt forward at larger scale
LAW-074 — Restoration Before Exploration Law	Exploration is also gated by restoration readiness
LAW-075 — Capacity Before Demand Law	Scaling increases demand and must follow capacity
LAW-076 — Supersession Threshold Law	Systems unable to restore before scaling may require replacement
LAW-109 — High-Φ Legitimacy Scaling Law	Influence scaling requires proportional constraints and repair
LAW-121 — AI as Γ-Amplifier Law	AI scaling amplifies classification and routing errors
LAW-131 — Cognitive Infrastructure Scaling Law	Public-cognition systems require governance proportional to influence
LAW-133 — Error Scale Law	Low error rates can produce large harm at high scale
LAW-145 — Growth Before Expansion Law	Growth capacity should precede expansion
LAW-154 — Biological Coherence-Preserving Scaling Law	Biology-specific expression of scaling only after restoration capacity

Aliases folded into this law:

Restoration Before Scaling Law
Repair Before Expansion Law
No Scaling Before Restoration Law
Scaling Amplifies Unrepaired Debt Law
Debt Before Scale Law
Restore Before Expanding Law
Unrepaired Scaling Debt Law

Deduplication note:

This law should remain the root restoration-gate law for scaling. LAW-018 through LAW-034 define broader scaling mechanics, LAW-064 through LAW-067 define restoration proof, LAW-074 defines the adjacent exploration gate, LAW-075 defines capacity-before-demand logic, and LAW-109 / LAW-131 specialize high-influence governance and cognitive infrastructure scaling.

13. Operator Mapping

TableScroll

Operator	Role in this law
`Γ`	Classifies scaling readiness and distinguishes growth from restoration
`Π`	Applies scale gates, throttles, deployment limits, or containment
`Ξ`	Captures inversion when growth is framed as proof of restoration
`⊗`	Coupling intensity increases with scale and must be staged
`ℛ`	Restoration must occur before unrepaired patterns are replicated
`Τ`	Validates repair before and during scale expansion
`Θ`	Prevents premature scaling certainty
`Σ`	Defines scale scope, repair scope, and expansion limits
`Ψ`	Field and affected-node feedback reveals scaling effects
`Λ`	Compatibility must be revalidated at expanded scale

Coherent operator sequence:

textScroll

Γ(scale readiness) → Θ(uncertainty) → Σ(scale / repair scope) → Au/FI(audit readiness) → ℛ(repair H / BΣ / recurrence) → R_eff↑ → Τ(validate) → Π(stage gates) → ⊗ gradual↑ → Ψ(validate field effects)

Inverted operator sequence:

textScroll

Φ_growth↑ → Γ(success claimed) → Scale↑ → H unrepaired → Au falls behind → recurrence replicates → Ξ / ι↑ → O↓ → legitimacy shock

14. Machine-Readable Summary

yamlScroll

id: "LAW-073"
name: "Restoration Before Scaling Law"
type: "law"
status: "draft"
family:
  - "Restoration Laws"
summary: "Scaling before restoration amplifies hidden debt across the expanded system."
canonical_statement: "Scaling before restoration amplifies hidden debt."
core_form: "Scale↑ before H↓ + R↑ + Au↑ + BΣ↑ ⇒ H amplification"
expanded_form: "Scale↑ ∧ (H↑/unrepaired ∨ Au↓ ∨ BΣ↓ ∨ R_eff < Load × Gain ∨ recurrence↑) ⇒ O↓ over scale"
restoration_ready_scaling_form: "H↓ + ι↓ + BΣ stable/↑ + Au↑ + R_eff ≥ Load × Gain + recurrence↓ + Τ proof ⇒ scaling admissible"
failure_form: "unrepaired system × scale ⇒ hidden debt replication"
variables:
  primary:
    - "Scale"
    - "H"
    - "R"
    - "R_eff"
    - "Au"
    - "BΣ"
    - "O"
    - "ι"
    - "Ξ"
    - "recurrence"
    - "Load"
    - "Gain"
  secondary:
    - "ε"
    - "K"
    - "σ"
    - "FI"
    - "µᵢ"
    - "Φ"
    - "Λ"
    - "⊗"
    - "Γ"
    - "Π"
    - "ℛ"
    - "Θ"
    - "Σ"
    - "Ψ"
    - "Τ"
diagnostics:
  - "Restoration Readiness"
  - "Scaling Readiness"
  - "Hidden Debt"
  - "Effective Restoration Capacity"
  - "Effective Auditability"
  - "Boundary Integrity"
  - "Recurrence"
  - "Ring-Down"
  - "Slack"
  - "Coherence Trajectory"
  - "Load"
  - "Gain"
  - "Pseudo-Restoration Risk"
  - "Temporal Proof"
failure_modes:
  - "Scaling Hidden Debt"
  - "Unrepaired Expansion"
  - "Debt Amplification"
  - "Pseudo-Restoration Scaling"
  - "Premature Deployment"
  - "Premature Growth"
  - "Legitimacy Decay"
  - "Observability Collapse"
  - "Hidden Debt Migration"
  - "Recurrence Amplification"
  - "Boundary Failure at Scale"
  - "Capacity Exhaustion"
  - "Delayed Collapse"
restoration_arcs:
  - "Restoration Before Scaling Gate"
  - "Hidden Debt Reduction"
  - "Origin-Layer Repair"
  - "Boundary Reconstitution"
  - "Restoration Capacity Rebuild"
  - "Auditability Restoration"
  - "Slack Regeneration"
  - "Controlled Decoupling"
  - "Temporal Validation"
  - "Recurrence Reduction"
  - "Closure Stack Completion"
related_laws:
  - "LAW-006"
  - "LAW-007"
  - "LAW-008"
  - "LAW-010"
  - "LAW-011"
  - "LAW-012"
  - "LAW-013"
  - "LAW-018"
  - "LAW-019"
  - "LAW-020"
  - "LAW-021"
  - "LAW-022"
  - "LAW-023"
  - "LAW-030"
  - "LAW-031"
  - "LAW-032"
  - "LAW-033"
  - "LAW-034"
  - "LAW-047"
  - "LAW-050"
  - "LAW-052"
  - "LAW-061"
  - "LAW-062"
  - "LAW-063"
  - "LAW-064"
  - "LAW-065"
  - "LAW-066"
  - "LAW-067"
  - "LAW-068"
  - "LAW-069"
  - "LAW-070"
  - "LAW-071"
  - "LAW-072"
  - "LAW-074"
  - "LAW-075"
  - "LAW-076"
  - "LAW-109"
  - "LAW-121"
  - "LAW-131"
  - "LAW-133"
  - "LAW-141"
  - "LAW-145"
  - "LAW-154"
related_invariants:
  - "INV-001"
  - "INV-004"
  - "INV-006"
  - "INV-079"
  - "INV-080"
operator_sequence:
  coherent:
    - "Γ scale readiness"
    - "Θ uncertainty"
    - "Σ scale / repair scope"
    - "Au/FI audit readiness"
    - "ℛ repair H / BΣ / recurrence"
    - "R_eff↑"
    - "Τ validate"
    - "Π stage gates"
    - "⊗ gradual↑"
    - "Ψ validate field effects"
  inverted:
    - "Φ_growth↑"
    - "Γ success claimed"
    - "Scale↑"
    - "H unrepaired"
    - "Au falls behind"
    - "recurrence replicates"
    - "Ξ / ι↑"
    - "O↓"
    - "legitimacy shock"
aliases:
  - "Restoration Before Scaling Law"
  - "Repair Before Expansion Law"
  - "No Scaling Before Restoration Law"
  - "Scaling Amplifies Unrepaired Debt Law"
  - "Debt Before Scale Law"
  - "Restore Before Expanding Law"
  - "Unrepaired Scaling Debt Law"
deduplication_note: "Root restoration-gate law for scaling. LAW-018 through LAW-034 define broader scaling mechanics, LAW-064 through LAW-067 define restoration proof, LAW-074 defines the adjacent exploration gate, LAW-075 defines capacity-before-demand logic, and LAW-109 / LAW-131 specialize high-influence governance and cognitive infrastructure scaling."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-073 — Restoration Before Scaling Law

Scaling before restoration amplifies hidden debt.

Core form:

textScroll

Scale↑ before H↓ + R↑ + Au↑ + BΣ↑ ⇒ H amplification

Expanded form:

textScroll

Scale↑ ∧ (H↑/unrepaired ∨ Au↓ ∨ BΣ↓ ∨ R_eff < Load × Gain ∨ recurrence↑) ⇒ O↓ over scale

Plain meaning:

A system should not expand, deploy, grow, replicate, automate, govern, monetize, institutionalize, or increase influence while hidden debt, broken boundaries, weak auditability, or insufficient restoration capacity remain unresolved. Scale does not neutralize unrepaired debt. It multiplies it.

Restoration-ready scaling form:

textScroll

H↓ + ι↓ + BΣ stable/↑ + Au↑ + R_eff ≥ Load × Gain + recurrence↓ + Τ proof ⇒ scaling admissible

Failure form:

textScroll

unrepaired system × scale ⇒ hidden debt replication

Primary variables:

Scale, H, R, R_eff, Au, BΣ, O, ι, Ξ, recurrence, Load, Gain, K, σ, FI, µᵢ, Γ, Π, ℛ, Θ, Σ, Ψ, Τ

Diagnostic signature:

Scale increases while hidden debt remains unresolved, auditability falls behind reach, boundaries remain fragile, restoration capacity is below load times gain, recurrence is untested, and growth proxies are treated as proof of readiness.

Failure risk:

Scaling hidden debt, unrepaired expansion, debt amplification, pseudo-restoration scaling, premature deployment, premature growth, legitimacy decay, observability collapse, hidden debt migration, recurrence amplification, boundary failure at scale, capacity exhaustion, delayed collapse.

Restoration priority:

Audit hidden debt, repair origin-layer failures, restore boundaries and auditability, rebuild restoration capacity, validate recurrence reduction over time, then scale gradually with rollback and field feedback.

LAW-072 — Quiet Minimization Debt Law

Registry

LAW-074 — Restoration Before Exploration Law