0. Plain Statement

Hidden debt migrates across domains and compounds under obfuscation.

Plain-language version:

When hidden debt is suppressed in one place, it often reappears somewhere else: another domain, another layer, another node, the future, the environment, or the periphery. Moving debt is not the same as repairing debt.

1. Formal Definition

The Hidden Debt Migration Law states that suppressed hidden debt can move across domains, layers, nodes, time horizons, and boundary interfaces rather than disappearing.

Hidden debt forms when incoherence is not repaired. If the original system cannot or will not process that debt, the debt may migrate through coupling pathways into adjacent systems. It may appear as institutional burden, biological symptoms, ecological forcing, economic crisis, technical debt, user burden, legitimacy shock, security failure, downstream AI failure, cultural fragmentation, or future repair cost.

Debt migration is often made worse by obfuscation. When causality is hidden, the receiving domain may be blamed for the migrated debt, while the origin domain appears stable or successful.

This law distinguishes three different states:

debt reduced ≠ debt hidden ≠ debt migrated

Only debt reduction is restoration.

2. Canonical Form

H suppressed in domain A ⇒ H migrates to domain B / future / periphery

Expanded canonical form:

suppressed hidden debt moves along coupling, boundary, temporal, and cross-scale pathways until repaired or exposed

Failure expression:

H migration treated as H resolution ⇒ pseudo-coherence

Related variables:

O, H, ε, ι, Au, R, BΣ, K, µᵢ, Φ, τ_m, 𝓓

Where:

3. Core Mechanism

The Hidden Debt Migration Law unfolds when a system suppresses or exports unresolved cost and another domain becomes the carrier.

Debt repair pathway

hidden debt appears
→ origin domain remains auditable
→ source layer is identified
→ repair capacity engages
→ debt is reduced at origin
→ recurrence weakens
→ cross-domain burden decreases

Debt migration pathway

hidden debt appears
→ origin domain suppresses or obscures it
→ debt transfers through coupling or boundary interface
→ receiving domain absorbs cost
→ origin appears stable
→ receiving domain destabilizes
→ global hidden debt compounds

The core mechanism is:

unrepaired debt follows the available path of least resistance

Debt migrates toward weaker nodes, less visible domains, less protected interfaces, future time horizons, or environments with lower immediate accountability.

4. When This Law Applies

This law applies whenever hidden debt appears to disappear from one location while burden rises elsewhere.

Common migration channels include:

• institution → users;
• company → workers;
• economy → ecology;
• governance → future crisis;
• AI platform → user cognition;
• security system → downstream teams;
• technical system → maintenance backlog;
• medical system → patient burden;
• policy system → affected-node navigation cost;
• organization → hidden labor;
• family/community → overloaded node;
• market → supply chain;
• culture → marginalized subfield;
• present system → future system;
• local system → global field.

The law applies strongly when:

local H appears reduced while cross-domain H rises

or when:

a receiving domain is treated as the problem while the origin domain remains unaudited

Typical domains:

5. When This Law Does Not Apply

This law should not be used to reject all cost transfer, delegation, load sharing, or staged repair.

A system can move burden coherently when the transfer is transparent, consented, compensated, reversible, bounded, and tied to repair.

This law does not apply as a critique when:

• the transfer is visible and audited;
• receiving nodes consent and are supported;
• compensation or restoration accompanies the burden;
• the origin domain remains responsible;
• the transfer reduces total hidden debt;
• recurrence weakens;
• boundaries are preserved;
• repair capacity exists in the receiving domain;
• the transfer is temporary and time-validated.

False-positive cases:

Important distinction:

Debt migration is incoherent when it hides, exports, or displaces unresolved cost without repair. Burden sharing is coherent when it remains visible, consented, supported, and restorative.

6. Diagnostic Signature

The basic diagnostic signature is:

H suppressed in domain A ⇒ H migrates to domain B / future / periphery

A stronger warning signature:

H_A appears ↓
Φ_A↑
Au_cross-domain↓
H_B↑
receiving node burden↑
origin accountability↓
⇒ debt migration

Common indicators:

Additional diagnostics:

7. Failure Pattern

If ignored, this law produces pseudo-resolution and downstream collapse.

General failure pathway:

debt appears in domain A
→ domain A suppresses or externalizes debt
→ local stability or success improves
→ debt migrates through hidden coupling
→ domain B absorbs burden
→ B loses slack, boundaries, or repair capacity
→ visible error appears in B
→ origin A remains falsely validated
→ global coherence declines

Common failure modes:

• Hidden Debt Migration — debt moves rather than resolves.
• Hidden Debt Accumulation — migrated debt compounds in receiving domains.
• Debt Relocation — movement of burden is mistaken for repair.
• Pseudo-Coherence — origin domain appears coherent while debt moves elsewhere.
• Local Stability Export — local stability depends on burden transfer.
• Delayed Collapse — receiving domain fails after debt compounds.
• Peripheral Node Collapse — weaker nodes absorb migrated cost.
• Legitimacy Shock — hidden institutional debt returns publicly.
• Ecological Forcing — environmental debt returns as constraint.
• Biological Symptom Migration — unresolved burden appears through another expression.
• Downstream System Contamination — dependent systems inherit upstream debt.
• Basin Entrapment — debt migration stabilizes the original pseudo-coherent basin.

Compact failure signature:

Φ_A↑ + H_B↑ + Au_cross-domain↓ ⇒ debt migration

8. Restoration Implications

Restoration requires tracing debt across domains and repairing both origin and receiving sites.

The first restoration question is not:

Where did the problem appear?

The first restoration question is:

Where did the debt originate, where did it travel, and who or what carried it?

Restoration priorities:

1. Identify the apparent debt reduction site.
2. Identify the receiving debt site.
3. Trace coupling, boundary, temporal, or cross-scale migration pathways.
4. Restore cross-domain auditability.
5. Distinguish origin, carrier, and symptom site.
6. Repair origin-layer incoherence.
7. Repair receiving domains that absorbed the debt.
8. Rebuild slack and restoration capacity in burdened nodes.
9. Change incentives or coupling structures that enabled export.
10. Time-validate that debt no longer migrates or recurs.

Relevant restoration arcs:

Minimal restoration sequence:

identify H migration
→ map origin / carrier / receiver
→ restore cross-domain Au
→ repair origin layer
→ repair receiver burden
→ rebuild R and K
→ change coupling / incentives
→ validate H↓ and migration↓

Temporal validation requirement:

H_origin↓
H_receiver↓
Au_cross-domain↑
BΣ restored
R_receiver↑
K_receiver↑
recurrence↓
migration pathway weakened
O_global stable or rising
no renewed peripheral burden

9. Design Rule

Do not count debt movement as debt repair.

Operational design requirements:

• Track debt across domains, not only inside one subsystem.
• Identify receiving nodes and burden carriers.
• Preserve cross-domain auditability.
• Treat externalities as system effects.
• Separate local improvement from global debt reduction.
• Require repair at the origin layer.
• Restore receiving domains that carried the debt.
• Compensate or support burden-bearing nodes.
• Watch for local stability built on externalized cost.
• Time-validate that debt does not reappear elsewhere.

Avoid:

• declaring success because debt left the dashboard;
• blaming the receiving domain without tracing origin;
• treating user burden as platform improvement;
• treating ecological cost as outside the economy;
• treating hidden labor as efficiency;
• treating patient burden as medical success;
• treating downstream team overload as implementation failure only;
• treating peripheral collapse as unrelated;
• treating future repair burden as savings;
• treating visibility reduction as debt reduction.

10. Cross-Scale Expressions

11. Examples

Example A — Institutional User Burden

Scenario:

An institution simplifies its internal process by shifting navigation, documentation, appeal effort, and proof burden onto users.

Law expression:

H_institution appears↓ while H_user↑ ⇒ debt migration

Interpretation:

The institution did not reduce debt. It moved debt to affected people.

Example B — AI Platform Burden

Scenario:

An AI platform hides uncertainty or reasoning complexity behind smooth output. Users must carry verification, correction, and interpretation burden.

Law expression:

H_AI_interface↓ apparent while H_user_cognition↑ ⇒ debt migration

Interpretation:

The interface appears easier while cognitive debt migrates to the user.

Example C — Economic Externality

Scenario:

A company increases profit by shifting ecological, labor, infrastructure, or future maintenance cost outside its accounting frame.

Law expression:

H_company appears↓ / Φ_profit↑ while H_ecology or H_labor↑

Interpretation:

Profit rises through debt migration.

Example D — Security Hardening

Scenario:

One system strengthens its security posture by forcing risk, friction, and manual review onto downstream users or smaller teams.

Law expression:

O_security_local↑ while H_downstream↑ ⇒ local stability export

Interpretation:

Local security coherence may be purchased through downstream burden.

Example E — Biological Symptom Migration

Scenario:

A symptom is suppressed in one system, but the burden appears later through another pathway, tissue, rhythm, or recurrence pattern.

Law expression:

ε_A↓ while H_B / ε_B↑ ⇒ biological debt migration

Interpretation:

The burden changed expression rather than resolving.

Example F — Software Technical Debt

Scenario:

A product team ships faster by moving complexity into operations, support, documentation debt, or future maintenance.

Law expression:

Φ_delivery↑ while H_ops / H_support↑ ⇒ technical debt migration

Interpretation:

Delivery success is achieved by moving debt downstream.

12. Relationship to Nearby Laws

Aliases folded into this law:

• Hidden Debt Migration Law
• Cross-Domain Debt Migration Law
• Debt Migration Law
• Suppressed Debt Transfer Law
• Debt Relocation Is Not Repair Rule

Deduplication note:

This law should remain the root cross-domain debt migration law. LAW-011 handles debt return, LAW-078 basin export, and LAW-079 local stability export as more specific expressions.

13. Operator Mapping

Coherent operator sequence:

Θ → Γ(debt migration classification) → Σ(origin / carrier / receiver scope) → ⊗(migration path) → Ψ(receiving-domain input) → Π(anti-export constraint) → ℛ(origin + receiver repair) → Τ(validate migration↓)

Inverted operator sequence:

Γ(debt gone from A) → Σ narrowed to A → H_B ignored → Φ_A↑ → H migrates / compounds → ε_B late → O_global↓

14. Machine-Readable Summary

id: "LAW-032"
name: "Hidden Debt Migration Law"
type: "law"
status: "draft"
family:
  - "Scaling and Compression Laws"
summary: "Hidden debt migrates across domains and compounds under obfuscation."
canonical_statement: "Hidden debt migrates across domains and compounds under obfuscation."
canonical_form: "H suppressed in domain A ⇒ H migrates to domain B / future / periphery"
failure_form: "H migration treated as H resolution ⇒ pseudo-coherence"
variables:
  primary:
    - "H"
    - "Au"
    - "BΣ"
    - "R"
    - "O"
  secondary:
    - "ε"
    - "ι"
    - "K"
    - "µᵢ"
    - "Φ"
    - "τ_m"
    - "𝓓"
diagnostics:
  - "Hidden Debt"
  - "Hidden Debt Migration"
  - "Hidden Debt Export"
  - "Cross-Domain Outcome"
  - "Cross-Scale Outcome"
  - "Effective Auditability"
  - "Causality Legibility"
  - "Delayed Field Effect"
  - "Boundary Integrity"
  - "Peripheral Burden"
  - "Legitimacy Shock Risk"
  - "Recurrence"
failure_modes:
  - "Hidden Debt Migration"
  - "Hidden Debt Accumulation"
  - "Debt Relocation"
  - "Pseudo-Coherence"
  - "Local Stability Export"
  - "Delayed Collapse"
  - "Peripheral Node Collapse"
  - "Legitimacy Shock"
  - "Ecological Forcing"
  - "Biological Symptom Migration"
  - "Downstream System Contamination"
  - "Basin Entrapment"
restoration_arcs:
  - "Auditability Restoration"
  - "Origin-Layer Repair"
  - "Boundary Reconstitution"
  - "Controlled Decoupling"
  - "Restoration Capacity Rebuild"
  - "Temporal Validation"
  - "Recurrence Reduction"
  - "Basin Supersession"
  - "Slack Regeneration"
related_laws:
  - "LAW-005"
  - "LAW-010"
  - "LAW-011"
  - "LAW-012"
  - "LAW-013"
  - "LAW-015"
  - "LAW-016"
  - "LAW-017"
  - "LAW-018"
  - "LAW-019"
  - "LAW-031"
  - "LAW-045"
  - "LAW-047"
  - "LAW-064"
  - "LAW-072"
  - "LAW-077"
  - "LAW-078"
  - "LAW-079"
  - "LAW-083"
  - "LAW-106"
related_invariants:
  - "INV-001"
  - "INV-004"
  - "INV-080"
operator_sequence:
  coherent:
    - "Θ"
    - "Γ"
    - "Σ"
    - "⊗"
    - "Ψ"
    - "Π"
    - "ℛ"
    - "Τ"
  inverted:
    - "Γ debt gone from A"
    - "Σ narrowed to A"
    - "H_B ignored"
    - "Φ_A↑"
    - "H migrates / compounds"
    - "ε_B late"
    - "O_global↓"
aliases:
  - "Hidden Debt Migration Law"
  - "Cross-Domain Debt Migration Law"
  - "Debt Migration Law"
  - "Suppressed Debt Transfer Law"
  - "Debt Relocation Is Not Repair Rule"
deduplication_note: "Root cross-domain debt migration law. LAW-011 handles debt return, LAW-078 basin export, and LAW-079 local stability export as more specific expressions."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-032 — Hidden Debt Migration Law

Hidden debt migrates across domains and compounds under obfuscation.

Plain meaning:

When hidden debt is suppressed in one place, it often reappears somewhere else: another domain, layer, node, the future, the environment, or the periphery. Moving debt is not repairing debt.

Canonical form:

H suppressed in domain A ⇒ H migrates to domain B / future / periphery

Failure form:

H migration treated as H resolution ⇒ pseudo-coherence

Primary variables:

H, Au, BΣ, R, O, ε, ι, K, µᵢ, Φ, τ_m, 𝓓

Diagnostic signature:

Debt appears to fall in one domain while burden, recurrence, hidden cost, or visible error rises in another domain, future state, or peripheral node.

Failure risk:

Hidden debt migration, debt relocation, pseudo-coherence, local stability export, peripheral node collapse, legitimacy shock, ecological forcing, biological symptom migration, downstream contamination.

Restoration priority:

Trace debt across origin, carrier, and receiver domains; repair the origin layer; restore receiving domains; rebuild cross-domain auditability; and validate that debt migration decreases over time.