1. Short Definition
Hidden Debt Migration occurs when unresolved incoherence is displaced from one part of a system into another domain, layer, node, future period, or weaker field.
Debt migration is not debt resolution.
2. Canonical Pattern
H suppressed in domain A ⇒ H migrates to domain B / future / peripheryExpanded:
suppressed incoherence
+
no origin-layer repair
⇒ debt displacement
⇒ burden appears elsewhere
⇒ system-wide coherence risk↑Plain form:
Hidden debt moves when it is not repaired.
3. Mechanic Description
SCALE-033 describes the transfer behavior of hidden debt.
When a system suppresses visible error, delays repair, hides damage, exports cost, or protects a local success metric, the underlying incoherence does not disappear. It often migrates.
Migration pathways include:
- from present into future
- from center to periphery
- from strong nodes to weak nodes
- from visible systems to invisible labor
- from public metrics to private burden
- from institutional decisions to downstream repair
- from technical systems to human operators
- from economic gain to ecological damage
- from governance failure to legitimacy debt
- from biological symptom suppression to later recurrence
- from AI system opacity to user confusion or appeal burden
Debt migration is especially dangerous because the originating system may look cleaner after export.
The debt appears elsewhere, often in a form that is harder to trace back to the source.
This creates local success while weakening cross-scale coherence.
4. UTS Variable Mapping
| Variable | Role in SCALE-033 |
|---|---|
| O | Declines globally when debt migrates instead of resolving |
| H | Moves across domains, nodes, layers, or time |
| ε | May decrease locally while rising elsewhere later |
| ι | Rises when local improvement hides displaced debt |
| Au | Must trace debt movement across domains |
| µᵢ | Meaning / legitimacy degrades when displaced burden becomes visible |
| BΣ | Boundaries may be used to export or hide debt |
| K | Receiving nodes lose slack as they absorb migrated burden |
| R | Restoration burden shifts to another layer or population |
| Φ | Local success proxy may improve through debt displacement |
5. Diagnostic Questions
- What debt is being suppressed rather than repaired?
- Where did the burden move?
- Which node, domain, layer, or future period absorbs the cost?
- Did visible error decrease locally while hidden burden increased elsewhere?
- Is the receiving node less powerful, less visible, or less able to refuse?
- Can auditability trace the migration pathway?
- Is local performance being purchased through downstream burden?
- Is the system calling migration “resolution”?
- Is recurrence appearing in a different form or domain?
- Would origin-layer repair reduce cross-domain burden?
6. Failure Signatures
1. Local Error Reduction With External Burden
ε_local↓ while H_elsewhere↑The system looks improved locally while burden rises elsewhere.
2. Debt Export to Periphery
H_center↓ apparent + H_periphery↑Central stability is maintained by peripheral burden.
3. Future Burden Shift
repair deferred ⇒ H_future↑Current calm is purchased through future repair cost.
4. Domain Translation
H_domain_A suppressed ⇒ symptoms appear in domain_BDebt reappears through a different channel.
5. Traceability Loss
H migrates + Au↓ ⇒ source attribution failureThe debt becomes harder to connect to its origin.
7. Related Failure Modes
- hidden debt migration
- hidden debt propagation
- local-global divergence
- silent extraction
- burden export
- legitimacy debt
- ecological externality
- downstream repair overload
- auditability collapse
- recurrence displacement
- pseudo-resolution
8. Related Diagnostics
| Diagnostic | Use |
|---|---|
| H_local | Hidden debt in originating system |
| H_downstream | Hidden debt in receiving system |
| H_future | Deferred repair burden |
| affected_node_cost | Cost imposed on receiving nodes |
| Au_eff | Traceability of debt movement |
| BΣ | Boundary role in export or containment |
| K / σ(t) | Slack of receiving nodes |
| R_eff | Repair capacity where debt lands |
| τ_m | Recurrence after migration |
| O_global | Whole-system coherence after displacement |
9. Restoration Implications
If SCALE-033 is active, restoration requires debt tracing and origin-layer repair.
Required actions:
- Identify the originating hidden debt.
- Trace where the burden migrated.
- Distinguish local improvement from whole-system repair.
- Protect receiving nodes from further exported burden.
- Restore auditability across domains.
- Repair the origin layer, not only the receiving symptom.
- Rebalance repair responsibility.
- Reduce boundary mechanisms that enable debt export.
- Track recurrence across domains.
- Validate whole-system debt reduction.
Core restoration rule:
Debt migration is not repair.10. Compact Registry Entry
id: SCALE-033
name: "Hidden Debt Migration"
family: "SCALE-F — Hidden Debt Propagation Mechanics"
type: "hidden-debt-transfer-mechanic"
status: "draft-ready"
short_definition: "Unresolved hidden debt moves across domains, layers, nodes, time horizons, or populations when suppressed rather than repaired."
canonical_pattern: "H suppressed in domain A ⇒ H migrates to domain B / future / periphery"
failure_signature: "Suppressed incoherence + no origin-layer repair ⇒ debt displacement + burden appears elsewhere + system-wide coherence risk↑"
primary_variables:
- O
- H
- ε
- ι
- Au
- µᵢ
- BΣ
- K
- R
- Φ
primary_diagnostics:
- H_local
- H_downstream
- H_future
- affected_node_cost
- Au_eff
- BΣ
- K
- σ(t)
- R_eff
- τ_m
- O_global
related_failure_modes:
- hidden_debt_migration
- hidden_debt_propagation
- local_global_divergence
- silent_extraction
- burden_export
- legitimacy_debt
- downstream_repair_overload
- auditability_collapse
- recurrence_displacement
restoration_implication: "Trace where hidden debt migrated, protect receiving nodes, restore auditability across domains, repair the origin layer, and validate whole-system debt reduction."11. One-Line Canon
Debt that is moved but not repaired remains active in the system.