1. Short Definition

A system remains viable under pressure only when effective restoration capacity exceeds load multiplied by gain.

Canonical form:

R_eff > Load × Gain ⇒ O tends to increase
R_eff < Load × Gain ⇒ collapse amplifies

This is one of the most useful operational scaling thresholds.

2. Plain-Language Definition

Load is the burden placed on the system.

Gain is how strongly that burden is amplified.

Restoration capacity is the system’s ability to repair, recover, settle, and reduce hidden debt.

If the system’s repair capacity is greater than the amplified burden, it can adapt.

If the amplified burden is greater than repair capacity, the system begins accumulating debt, distortion, recurrence, and instability.

3. Canonical Pattern

R_eff > Load × Gain

Coherent side:

R_eff > Load × Gain ⇒ O stable/↑, H bounded/↓, 𝓓↑

Incoherent side:

R_eff < Load × Gain ⇒ H↑, ι↑, 𝓓↓, recurrence↑, O↓

4. UTS Variable Mapping

5. Mechanic Description

SCALE-003 isolates one of the central scaling thresholds.

Many systems can handle high load if gain is low.

Many systems can handle high gain if load is low.

But high load multiplied by high gain can overwhelm even strong systems.

Examples:

• A small error in a low-gain system stays local.
• A small error in a high-gain AI system can propagate widely.
• A moderate biological stressor with low amplification may resolve.
• The same stressor under immune overreaction can become systemic.
• A governance dispute with low symbolic gain may be repaired.
• The same dispute under high attention, identity binding, and institutional pressure may destabilize the whole field.

The constraint is multiplicative because gain amplifies load.

So the system does not only ask:

How much burden exists?

It asks:

How amplified is the burden?

6. Load Types

Load may include:

• operational load
• cognitive load
• emotional / symbolic load
• biological load
• financial load
• governance load
• legal load
• technical load
• security load
• attention load
• environmental load
• coordination load
• memory load
• repair backlog

In scaling analysis, load should be localized by U-layer.

Examples:

7. Gain Types

Gain is the amplification factor applied to load.

Common gain sources:

• automation
• leverage
• institutional authority
• financial leverage
• emotional charge
• identity binding
• symbolic intensity
• legal force
• algorithmic reach
• virality
• surveillance
• centralization
• urgency framing
• network effects
• high-speed feedback
• recursive loops
• adversarial pressure

Gain is not inherently bad.

But gain must be matched by restoration and damping.

8. Effective Restoration Capacity

Effective restoration capacity is not theoretical repair capacity.

It is repair capacity available under actual conditions.

R_eff = usable restoration capacity under current load, timing, access, and constraint conditions

R_eff may be reduced by:

• low slack
• poor auditability
• missing authority
• inaccessible repair paths
• damaged boundaries
• delayed feedback
• legitimacy loss
• resource scarcity
• hidden debt backlog
• fragmented responsibility
• unclear ownership
• trust collapse
• meaning collapse

So the system may claim high R while having low R_eff.

9. Diagnostic Questions

Ask:

1. What is the current load?
2. What is amplifying that load?
3. Which gain sources are active?
4. Is gain necessary, excessive, or misapplied?
5. What is the usable restoration capacity?
6. Is restoration capacity theoretical or actually accessible?
7. Is slack sufficient to buffer the load?
8. Are boundaries regulating load entry?
9. Is hidden debt increasing?
10. Is the system settling after disturbance?

10. Failure Signatures

1. Amplified Burden Exceeds Repair

Load × Gain > R_eff

The system cannot repair at the rate pressure is being applied.

2. Control Escalation After Repair Failure

R_eff < Load × Gain ⇒ control↑ ⇒ compression↑ ⇒ R_eff↓

The system tries to solve repair failure by adding more control, which further reduces recovery capacity.

3. Damping Collapse

Load × Gain > R_eff ⇒ 𝓓↓

The system stops settling cleanly.

4. Recurrence Increase

τ_m↑ + recurrence↑

The same failure pattern keeps returning.

5. Hidden Debt Accumulation

H↑ while ε remains bounded

The system appears stable while repair debt accumulates.

11. Related Failure Modes

• restoration starvation
• capacity collapse
• gain runaway
• latency-gain oscillation
• compression depth collapse
• hidden debt accumulation
• silent extraction
• pseudo-restoration
• control-density spiral
• recurrence lock
• brittle compliance

12. Related Diagnostics

13. Restoration Implications

When SCALE-003 fails, the system has four primary options:

1. Reduce Load

Load↓

Examples:

• pause expansion
• lower throughput
• reduce intake
• shed nonessential burden
• simplify demands
• reduce active cases
• narrow scope

2. Reduce Gain

Gain↓

Examples:

• damp urgency
• reduce amplification
• decentralize force
• slow propagation
• lower emotional charge
• remove identity binding
• reduce automation reach
• reduce leverage

3. Increase Restoration Capacity

R_eff↑

Examples:

• add repair resources
• improve access to repair
• restore auditability
• clarify ownership
• increase staffing
• rebuild trust
• improve feedback
• repair boundaries

4. Increase Slack

K↑ / σ↑

Examples:

• add time buffers
• create recovery windows
• reduce forced choice
• improve optionality
• create pause capacity
• protect repair bandwidth

Best restoration often does all four.

14. Compact Registry Entry

id: SCALE-003
name: "Load × Gain Constraint"
family: "SCALE-A — Core Scaling Definition and Viability"
type: "threshold-rule"
status: "draft-ready"
short_definition: "A system remains coherent under pressure only when effective restoration capacity exceeds load multiplied by gain."
canonical_pattern: "R_eff > Load × Gain ⇒ O stable/↑; R_eff < Load × Gain ⇒ collapse amplifies"
failure_signature: "Load × Gain > R_eff ⇒ H↑ + ι↑ + 𝓓↓ + recurrence↑ + O↓"
primary_variables:
  - O
  - H
  - ε
  - ι
  - Au
  - µᵢ
  - BΣ
  - K
  - R
  - Φ
primary_diagnostics:
  - Load
  - Gain
  - R_eff
  - 𝓓(t)
  - σ(t)
  - τ_resp
  - τ_m
  - Cv(t)
related_failure_modes:
  - restoration_starvation
  - capacity_collapse
  - gain_runaway
  - latency_gain_oscillation
  - compression_depth_collapse
  - hidden_debt_accumulation
  - recurrence_lock
restoration_implication: "Reduce load, reduce gain, increase restoration capacity, and regenerate slack before continuing scale."

15. One-Line Canon

A system can carry amplified burden only when effective restoration capacity exceeds load multiplied by gain.