1. Short Definition
Local Stability Export occurs when a system maintains apparent stability in one location by transferring incoherence, cost, risk, or repair burden elsewhere.
Local order may be real, but it is not whole-system coherence if it depends on exported burden.
2. Canonical Pattern
O_local stable + H_export↑ ⇒ pseudo-coherence risk↑Expanded:
local stability maintained
by
externalized burden
⇒ O_local appears stable
while O_global declinesPlain form:
Stable for whom, at whose cost, and over what time horizon?
3. Mechanic Description
SCALE-035 describes how pseudo-coherent systems maintain local order.
A subsystem may look stable, efficient, compliant, profitable, peaceful, secure, or successful because it has moved instability elsewhere.
Export channels include:
- weaker nodes
- downstream teams
- future maintainers
- invisible labor
- ecological systems
- users
- patients
- peripheral communities
- lower-status workers
- automated systems
- future budgets
- appeal pathways
- biological recovery systems
- institutional legitimacy reserves
Local stability export is not always obvious.
From inside the stable zone, the system may appear coherent because:
- metrics look good
- visible conflict is low
- operations continue
- leadership appears effective
- compliance improves
- costs are not visible
- repair burden is offloaded
- affected nodes lack visibility or voice
But whole-system coherence declines because hidden debt is still active.
This mechanism explains how pseudo-coherent basins can feel orderly internally while generating external instability.
4. UTS Variable Mapping
| Variable | Role in SCALE-035 |
|---|---|
| O | Local coherence may appear stable while global coherence declines |
| H | Exported hidden debt rises |
| ε | Local error may remain low while downstream error rises |
| ι | Rises when local order is mistaken for whole-system coherence |
| Au | Needed to see exported burden |
| µᵢ | Meaning / legitimacy degrades when export becomes visible |
| BΣ | Boundaries may be used to shift burden outward |
| K | Receiving nodes lose slack as they absorb exported cost |
| R | Restoration burden is transferred away from the origin system |
| Φ | Local success proxy improves through externalization |
5. Diagnostic Questions
- Where is stability being measured?
- Who or what absorbs the cost of that stability?
- Is local error low because burden is exported?
- Are downstream nodes losing slack?
- Is global coherence declining while local metrics improve?
- Are repair burdens moving away from the originating system?
- Can affected nodes report the exported burden?
- Is stability dependent on externalization?
- Is the system confusing local calm with coherence?
- Would the local system remain stable if it had to internalize its costs?
6. Failure Signatures
1. Local Calm, Downstream Burden
ε_local↓ while burden_downstream↑The system appears stable because cost is moved elsewhere.
2. Global Coherence Decline
O_local stable while O_global↓Local order coexists with whole-system degradation.
3. Peripheral Slack Drain
H_export↑ ⇒ K_periphery↓Receiving nodes lose optionality and repair capacity.
4. Hidden Labor Absorption
visible workload stable + invisible labor↑Unseen nodes maintain stability.
5. Stability Dependency on Export
externalization removed ⇒ local stability failsThe local system depends on exported burden.
7. Related Failure Modes
- local stability export
- pseudo-coherence
- hidden debt export
- local-global divergence
- silent extraction
- downstream repair overload
- invisible labor burden
- legitimacy debt
- ecological externality
- burden asymmetry
- exploitation basin
8. Related Diagnostics
| Diagnostic | Use |
|---|---|
| O_local | Local coherence / stability |
| O_global | Whole-system coherence |
| H_export | Exported hidden debt |
| burden_downstream | Load shifted downstream |
| affected_node_cost | Cost to receiving nodes |
| K_periphery | Slack of burden-receiving nodes |
| Au_eff | Ability to observe export |
| R_eff_origin | Repair capacity of origin system |
| R_eff_receiver | Repair capacity of receiving system |
| Φ_local | Local performance proxy |
9. Restoration Implications
If SCALE-035 is active, restoration requires internalizing exported burden and measuring whole-system coherence.
Required actions:
- Identify where stability is being measured.
- Trace exported burden.
- Include affected downstream nodes in diagnostics.
- Compare O_local against O_global.
- Protect receiving nodes from further burden transfer.
- Internalize repair responsibility where appropriate.
- Restore slack to burdened nodes.
- Reduce local metrics that reward export.
- Repair origin-layer causes.
- Validate coherence across scale, not only locally.
Core restoration rule:
Local stability is not coherence if it depends on exported burden.10. Compact Registry Entry
id: SCALE-035
name: "Local Stability Export"
family: "SCALE-F — Hidden Debt Propagation Mechanics"
type: "local-global-debt-export-mechanic"
status: "draft-ready"
short_definition: "A system preserves apparent stability in one location by transferring incoherence, cost, risk, or repair burden elsewhere."
canonical_pattern: "O_local stable + H_export↑ ⇒ pseudo-coherence risk↑"
failure_signature: "local stability maintained by externalized burden ⇒ O_local appears stable while O_global declines"
primary_variables:
- O
- H
- ε
- ι
- Au
- µᵢ
- BΣ
- K
- R
- Φ
primary_diagnostics:
- O_local
- O_global
- H_export
- burden_downstream
- affected_node_cost
- K_periphery
- Au_eff
- R_eff_origin
- R_eff_receiver
- Φ_local
related_failure_modes:
- local_stability_export
- pseudo_coherence
- hidden_debt_export
- local_global_divergence
- silent_extraction
- downstream_repair_overload
- invisible_labor_burden
- legitimacy_debt
- ecological_externality
restoration_implication: "Trace exported burden, compare local and global coherence, protect receiving nodes, internalize repair responsibility, and reduce metrics that reward burden export."11. One-Line Canon
Local stability is not whole-system coherence when it is maintained by exporting burden elsewhere.