1. Short Definition
Performance-Coherence Divergence occurs when a system’s visible success proxy improves while its underlying coherence declines.
This is one of the central pathways into pseudo-coherence.
2. Canonical Pattern
Φ↑ while O↓ ⇒ ι↑Expanded:
Performance↑ + Coherence↓ ⇒ Inversion↑ + Hidden Debt↑Plain form:
A system can look more successful while becoming less coherent.
3. Mechanic Description
SCALE-005 describes the core proxy hazard in scaling.
As systems scale, direct understanding becomes harder. They increasingly rely on performance indicators, metrics, dashboards, classifications, outputs, scores, benchmarks, rankings, reports, or visible signs of success.
These proxies can be useful. But they become dangerous when the system starts optimizing the proxy instead of preserving coherence.
Performance-Coherence Divergence appears when:
- output increases while repair capacity declines
- compliance improves while legitimacy falls
- profit rises while circulation weakens
- engagement rises while meaning degrades
- AI benchmark scores rise while auditability falls
- throughput increases while boundary integrity collapses
- visible symptoms decrease while biological coherence worsens
- institutional stability improves while hidden debt is exported
This is not merely measurement error. It is a structural scaling risk.
The larger and faster the system becomes, the more tempting it is to treat Φ as if it were O. UTS separates these: performance is not coherence, and success is not viability.
4. UTS Variable Mapping
| Variable | Role in SCALE-005 |
|---|---|
| O | True coherence; declines beneath visible success |
| H | Hidden debt accumulates when proxy success masks damage |
| ε | Observable error may stay low until late-stage failure |
| ι | Inversion rises when Φ substitutes for O |
| Au | Needed to detect divergence between performance and coherence |
| µᵢ | Meaning integrity often declines under proxy capture |
| BΣ | Boundary damage may be hidden by performance success |
| K | Slack may be consumed to maintain output |
| R | Restoration capacity may decline while metrics improve |
| Φ | Performance / success proxy that appears to improve |
5. Diagnostic Questions
- Which performance proxy is improving?
- Is coherence improving with it, or declining underneath it?
- Is the system optimizing the metric instead of the target?
- Is hidden debt rising while visible success improves?
- Is auditability strong enough to detect divergence?
- Are boundaries, slack, and restoration capacity improving or degrading?
- Is recurrence decreasing, or only visible error?
- Is the success local while burden is exported elsewhere?
- Are people trusting the dashboard more than the system state?
- Does the system still settle after perturbation?
6. Failure Signatures
1. Proxy Substitution
Φ treated as O ⇒ ι↑The system mistakes performance for coherence.
2. Visible Success With Hidden Debt
Φ↑ + H↑ ⇒ pseudo-coherence risk↑The system buys success by deferring cost.
3. Error Suppression
ε↓ while H↑ ⇒ silent extractionVisible error falls while unresolved debt rises.
4. Restoration Decline Under Success
Φ↑ while R↓ ⇒ collapse risk↑The system performs better while losing repair capacity.
5. Slack Consumption
Φ↑ while K↓ ⇒ brittleness↑The system maintains performance by consuming optionality.
7. Related Failure Modes
- pseudo-coherence
- pseudo-scaling
- proxy capture
- Goodhart collapse
- hidden debt accumulation
- silent extraction
- metric substitution
- restoration starvation
- meaning collapse
- compliance theater
- security theater
- local-global divergence
8. Related Diagnostics
| Diagnostic | Use |
|---|---|
| Φ | Performance / success proxy |
| O | True coherence |
| H | Hidden debt |
| ι | Inversion index |
| Au_eff | Ability to detect divergence |
| R_eff | Restoration capacity |
| σ(t) | Slack margin |
| BΣ | Boundary integrity |
| 𝓓(t) | Ring-down |
| τ_m | Recurrence |
9. Restoration Implications
If SCALE-005 is active, restoration requires proxy re-subordination.
Required actions:
- Stop treating Φ as proof of O.
- Identify which coherence variables are declining beneath performance.
- Restore auditability around the proxy.
- Check hidden debt and exported burden.
- Revalidate the metric against whole-system coherence.
- Restore slack and repair capacity.
- Test recurrence and ring-down.
- Redesign the proxy if it selects against coherence.
- Re-anchor optimization to O.
Core restoration rule:
Φ must remain subordinate to O.10. Compact Registry Entry
id: SCALE-005
name: "Performance-Coherence Divergence"
family: "SCALE-A — Core Scaling Definition and Viability"
type: "scaling-failure-rule"
status: "draft-ready"
short_definition: "Performance-Coherence Divergence occurs when visible performance or success proxies improve while underlying coherence declines."
canonical_pattern: "Φ↑ while O↓ ⇒ ι↑"
failure_signature: "Performance↑ + Coherence↓ ⇒ Inversion↑ + Hidden Debt↑"
primary_variables:
- O
- H
- ε
- ι
- Au
- µᵢ
- BΣ
- K
- R
- Φ
primary_diagnostics:
- Φ
- O
- H
- ι
- Au_eff
- R_eff
- σ(t)
- BΣ
- 𝓓(t)
- τ_m
related_failure_modes:
- pseudo_coherence
- pseudo_scaling
- proxy_capture
- goodhart_collapse
- hidden_debt_accumulation
- silent_extraction
- restoration_starvation
- meaning_collapse
restoration_implication: "Re-subordinate Φ to O, restore auditability around the proxy, identify hidden debt, and redesign metrics that select against coherence."11. One-Line Canon
A system is not scaling coherently when its success signal rises while its coherence declines.