1. Short Definition
Silent Extraction occurs when a system loses coherence, slack, repair capacity, or future viability while visible error remains low.
The system appears calm because depletion is not yet visible.
2. Canonical Pattern
dO/dt < 0 ∧ ε≈0 ⇒ silent extraction riskExpanded:
coherence↓ + slack↓ + repair capacity↓
while
visible error remains low
⇒ hidden debt↑ + late failure risk↑Plain form:
Calm can hide depletion.
3. Mechanic Description
SCALE-036 names a subtle but high-risk scaling condition.
A system can look stable because it is drawing down reserves that are not visible in normal performance metrics.
These reserves may include:
- slack
- trust
- goodwill
- repair capacity
- biological recovery
- institutional legitimacy
- worker capacity
- social patience
- environmental resilience
- infrastructure margin
- audit capacity
- future optionality
- boundary integrity
- hidden maintenance capacity
Silent extraction is dangerous because the system may appear healthy while it is becoming less viable.
The extraction remains “silent” when ordinary metrics do not track what is being depleted.
For example:
- a team hits targets by consuming recovery capacity
- an economy grows by degrading future resilience
- an AI system performs well while auditability declines
- a biological system functions while recovery slack disappears
- an institution maintains order by spending legitimacy reserves
- a security system reduces incidents while trust and repair capacity collapse
Silent extraction often precedes sudden visible failure.
The failure appears sudden only because the depletion was not tracked.
4. UTS Variable Mapping
| Variable | Role in SCALE-036 |
|---|---|
| O | Declines beneath surface stability |
| H | Accumulates as depletion becomes future repair burden |
| ε | Remains low or delayed despite coherence loss |
| ι | Rises when calm or performance is mistaken for coherence |
| Au | Falls or remains insufficient to detect depletion |
| µᵢ | Meaning / legitimacy may hollow beneath continued function |
| BΣ | Boundary integrity may erode quietly |
| K | Slack / sovereignty margin is often the first reserve consumed |
| R | Restoration capacity is depleted or deferred |
| Φ | Performance proxy may remain stable or rise during extraction |
5. Diagnostic Questions
- What reserves are being consumed?
- Are visible errors low because the system is healthy or because depletion is hidden?
- Is slack declining while performance remains stable?
- Is restoration capacity being spent faster than rebuilt?
- Is trust, legitimacy, or goodwill being consumed?
- Are affected nodes absorbing cost invisibly?
- Are maintenance and repair being deferred?
- Is auditability sufficient to detect depletion?
- Are metrics tracking reserve loss or only output?
- What would fail first if hidden reserves ran out?
6. Failure Signatures
1. Low Visible Error With Coherence Decline
ε≈0 while O↓The system appears stable while coherence degrades.
2. Slack Drawdown
Φ stable while K↓ / σ↓Performance is maintained by consuming optionality.
3. Repair Capacity Depletion
R_eff↓ while output remains stableThe system continues functioning while losing recovery capacity.
4. Hidden Burden Absorption
visible workload stable + invisible burden↑Unseen nodes absorb system cost.
5. Late Failure Spike
silent depletion + buffer exhaustion ⇒ ε spikeVisible error appears after reserves are exhausted.
7. Related Failure Modes
- silent extraction
- hidden debt accumulation
- restoration starvation
- local stability export
- invisible labor burden
- legitimacy depletion
- zero-slack collapse
- pseudo-coherence
- performance-coherence divergence
- late visible failure
- capacity collapse
8. Related Diagnostics
| Diagnostic | Use |
|---|---|
| O_trend | Coherence decline under low error |
| ε | Visible error surface |
| K / σ(t) | Slack reserves |
| R_eff | Repair capacity |
| H | Hidden debt accumulation |
| Au_eff | Ability to detect depletion |
| reserve_depth | Remaining hidden reserves |
| affected_node_cost | Invisible burden absorbed by nodes |
| 𝓓(t) | Ring-down after disturbance |
| τ_m | Recurrence after apparent stability |
9. Restoration Implications
If SCALE-036 is active, restoration requires reserve accounting and depletion reversal.
Required actions:
- Identify which reserves are being consumed.
- Stop relying on visible error as the only health signal.
- Restore auditability around hidden reserves.
- Reduce load or gain where reserves are being depleted.
- Rebuild slack.
- Rebuild restoration capacity.
- Surface invisible burden.
- Protect affected nodes from continued extraction.
- Track reserve recovery over time.
- Validate that calm reflects coherence, not depletion.
Core restoration rule:
Measure depletion before trusting calm.10. Compact Registry Entry
id: SCALE-036
name: "Silent Extraction"
family: "SCALE-F — Hidden Debt Propagation Mechanics"
type: "hidden-depletion-mechanic"
status: "draft-ready"
short_definition: "Silent Extraction occurs when coherence, slack, repair capacity, or future viability decline while visible error remains low."
canonical_pattern: "dO/dt < 0 ∧ ε≈0 ⇒ silent extraction risk"
failure_signature: "coherence↓ + slack↓ + repair capacity↓ while visible error remains low ⇒ hidden debt↑ + late failure risk↑"
primary_variables:
- O
- H
- ε
- ι
- Au
- µᵢ
- BΣ
- K
- R
- Φ
primary_diagnostics:
- O_trend
- ε
- K
- σ(t)
- R_eff
- H
- Au_eff
- reserve_depth
- affected_node_cost
- 𝓓(t)
- τ_m
related_failure_modes:
- silent_extraction
- hidden_debt_accumulation
- restoration_starvation
- local_stability_export
- invisible_labor_burden
- legitimacy_depletion
- zero_slack_collapse
- pseudo_coherence
- performance_coherence_divergence
restoration_implication: "Identify hidden reserve depletion, reduce load and gain, restore auditability, rebuild slack and restoration capacity, and validate that calm reflects coherence rather than depletion."11. One-Line Canon
A system can look calm because it is coherent, or because it is quietly spending its future.