1. Short Definition
Hidden Debt Propagation occurs when unresolved hidden debt is carried into a larger, faster, more coupled, or more powerful system, giving the debt more pathways to spread.
Scaling before repair spreads the debt.
2. Canonical Pattern
Scale↑ while H unresolved ⇒ H propagation↑Expanded:
Unresolved hidden debt
+
scope↑ / coupling↑ / velocity↑ / gain↑
⇒ debt pathways↑
⇒ repair burden↑
⇒ coherence risk↑Plain form:
Hidden debt does not disappear when scaled; it travels farther.
3. Mechanic Description
SCALE-032 begins the hidden debt propagation family.
Hidden debt is deferred incoherence: unresolved cost, suppressed error, exported burden, delayed repair, unacknowledged damage, invisible dependency, or accumulated future failure pressure.
When systems scale without reducing hidden debt, that debt becomes embedded into the larger structure.
This can happen through:
- expanding broken processes
- deploying unaudited AI systems
- growing institutions with unresolved legitimacy debt
- scaling economic systems with extraction built in
- increasing biological demand before recovery
- automating flawed classifications
- expanding security systems with trust failures
- increasing coupling before boundary repair
- standardizing procedures that contain hidden incoherence
The debt then spreads through new nodes, interfaces, contracts, dependencies, memory layers, and downstream consequences.
At small scale, hidden debt may remain local.
At larger scale, it becomes systemic.
The UTS–Scaling reference frames hidden debt as deferred incoherence that can be pushed into the future, weaker actors, environments, unmeasured zones, or maintenance backlogs, but eventually reasserts.
4. UTS Variable Mapping
| Variable | Role in SCALE-032 |
|---|---|
| O | Declines as hidden debt spreads through scaled structure |
| H | Core variable; unresolved debt propagates under scale |
| ε | Appears late when propagated debt becomes visible failure |
| ι | Rises when scaled success hides debt expansion |
| Au | Must trace where debt is moving |
| µᵢ | Meaning / legitimacy degrades as debt becomes known or felt |
| BΣ | Boundaries may transmit debt into new domains |
| K | Slack is consumed by future repair burden |
| R | Restoration burden increases as debt spreads |
| Φ | Scaling may improve performance while propagating debt |
5. Diagnostic Questions
- What hidden debt exists before scaling?
- Is the system scaling before reducing that debt?
- Where will unresolved debt propagate if scope increases?
- Which nodes will absorb the debt?
- Is debt being exported to weaker or less visible domains?
- Is performance improving while hidden repair burden grows?
- Can auditability trace the debt pathway?
- Is the debt becoming embedded into standard procedure?
- Is recurrence increasing after scale increases?
- Would repair now be cheaper than repair after scaling?
6. Failure Signatures
1. Debt Spreads With Scope
H unresolved + scope↑ ⇒ H_distribution↑Hidden debt reaches more nodes.
2. Debt Amplified by Coupling
H unresolved + coupling↑ ⇒ propagation pathways↑Debt travels through dependencies.
3. Debt Accelerated by Gain
H unresolved + Gain↑ ⇒ impact_magnitude↑The same debt becomes more consequential.
4. Late Error Emergence
H propagated ⇒ ε spike lateVisible failure appears after debt spreads.
5. Standardized Incoherence
broken process + scale↑ ⇒ incoherence normalizedThe system turns hidden debt into standard operating structure.
7. Related Failure Modes
- hidden debt propagation
- pseudo-scaling
- standardized incoherence
- restoration starvation
- local-global divergence
- silent extraction
- recurrence lock
- auditability collapse
- legitimacy debt
- delayed transition cost
- performance-coherence divergence
8. Related Diagnostics
| Diagnostic | Use |
|---|---|
| H | Existing hidden debt |
| H_distribution | Spread of debt across nodes/domains |
| scope | Scale of affected system |
| ⊗ density | Coupling pathways for debt propagation |
| Gain | Amplification of debt impact |
| Au_eff | Debt traceability |
| R_eff | Repair capacity |
| τ_m | Recurrence after scaling |
| ε | Visible late failure |
| affected_node_cost | Burden placed on downstream nodes |
9. Restoration Implications
If SCALE-032 is active, restoration must stop debt propagation before expanding scale.
Required actions:
- Identify hidden debt before scaling.
- Map propagation pathways.
- Reduce debt at the origin layer.
- Pause expansion if debt is likely to spread.
- Repair broken processes before standardizing them.
- Reduce coupling pathways that carry debt.
- Restore auditability around debt movement.
- Protect downstream and weaker nodes.
- Increase restoration capacity before resuming scale.
- Validate recurrence reduction after repair.
Core restoration rule:
Do not scale hidden debt.10. Compact Registry Entry
id: SCALE-032
name: "Hidden Debt Propagation"
family: "SCALE-F — Hidden Debt Propagation Mechanics"
type: "hidden-debt-scaling-mechanic"
status: "draft-ready"
short_definition: "Unresolved hidden debt spreads, amplifies, or becomes harder to repair when carried into a larger, faster, more coupled, or more powerful system."
canonical_pattern: "Scale↑ while H unresolved ⇒ H propagation↑"
failure_signature: "Unresolved hidden debt + scope↑ / coupling↑ / velocity↑ / gain↑ ⇒ debt pathways↑ + repair burden↑ + coherence risk↑"
primary_variables:
- O
- H
- ε
- ι
- Au
- µᵢ
- BΣ
- K
- R
- Φ
primary_diagnostics:
- H
- H_distribution
- scope
- ⊗ density
- Gain
- Au_eff
- R_eff
- τ_m
- ε
- affected_node_cost
related_failure_modes:
- hidden_debt_propagation
- pseudo_scaling
- standardized_incoherence
- restoration_starvation
- local_global_divergence
- silent_extraction
- recurrence_lock
- auditability_collapse
- legitimacy_debt
restoration_implication: "Identify hidden debt before scaling, repair origin-layer causes, map propagation pathways, protect downstream nodes, and resume scaling only after recurrence reduction."11. One-Line Canon
Scaling before hidden debt is repaired turns local debt into system debt.