1. Short Definition

Recurrence Pressure occurs when the same failure pattern returns under similar stress, indicating unresolved hidden debt, incomplete repair, or persistent basin geometry.

Recurrence reveals what the system has not actually changed.

2. Canonical Pattern

τ_m↑ + recurrence↑ ⇒ repair incomplete

Expanded:

Same pattern returns under similar forcing
⇒ underlying basin persists
⇒ hidden debt remains
⇒ restoration not complete

Plain form:

If the failure keeps returning, the basin is still active.

3. Mechanic Description

SCALE-031 defines recurrence as a scaling diagnostic.

At scale, systems often mistake temporary suppression for repair. They may reduce visible error, improve compliance, produce new messaging, add rules, change labels, or complete a reform cycle while the underlying pattern remains.

Recurrence tests whether the system actually changed.

A recurrence may appear as:

• repeated incidents
• recurring symptoms
• returning conflicts
• repeated policy failures
• recurring AI behavior
• repeated security events
• repeated institutional breakdown
• repeated biological activation
• recurring economic extraction
• repeated legitimacy shocks
• repeated boundary violations
• repeated repair attempts that do not hold

The recurrence pressure may increase when systems scale because more load, coupling, speed, and visibility pressure reactivate unresolved patterns.

In UTS, recurrence is not merely repetition. It is evidence of memory, basin geometry, hidden debt, or incomplete restoration.

The UTS–Scaling reference emphasizes that coherence must be tested through recurrence reduction, ring-down improvement, restoration behavior, and delayed field effects over time.

4. UTS Variable Mapping

5. Diagnostic Questions

1. Has this pattern happened before?
2. Under what conditions does it return?
3. Did prior repair reduce recurrence or only visible error?
4. Is recurrence happening at the same U-layer?
5. Is the same basin being re-entered under stress?
6. Is hidden debt still active?
7. Are metrics improving while recurrence persists?
8. Is ring-down improving after each cycle?
9. Is memory being updated, or is the system repeating?
10. Has restoration changed the attractor geometry?

6. Failure Signatures

1. Same Pattern, Same Stress

similar forcing ⇒ similar failure

The system returns to the same basin under repeated conditions.

2. Visible Repair, Persistent Recurrence

repair_claim↑ while τ_m↑

The system claims repair while memory of the failure persists.

3. Ring-Down Failure

𝓓(t)↓ + recurrence↑

The system does not settle after disturbance.

4. Suppression Instead of Repair

ε↓ temporarily while recurrence persists

Visible error drops without changing the underlying pattern.

5. Hidden Debt Reactivation

H_unrepaired + stress↑ ⇒ failure returns

Dormant debt reactivates under load.

7. Related Failure Modes

• recurrence lock
• pseudo-restoration
• symptom suppression
• hidden debt reactivation
• basin persistence
• ring-down failure
• restoration starvation
• memory failure
• local-global divergence
• delayed transition cost
• performance-coherence divergence

8. Related Diagnostics

9. Restoration Implications

If SCALE-031 is active, restoration must shift from symptom repair to basin repair.

Required actions:

1. Map recurrence across time.
2. Identify the stress conditions that reactivate the pattern.
3. Localize the recurring failure by U-layer.
4. Compare claimed repair against recurrence data.
5. Restore origin-layer causes.
6. Reduce hidden debt.
7. Improve damping and ring-down.
8. Update memory and learning structures.
9. Alter basin geometry instead of only suppressing symptoms.
10. Validate restoration through recurrence reduction.

Core restoration rule:

Repair is incomplete until recurrence weakens.

10. Compact Registry Entry

id: SCALE-031
name: "Recurrence Pressure"
family: "SCALE-E — Slack, Bandwidth, and Timing Mechanics"
type: "recurrence-memory-scaling-mechanic"
status: "draft-ready"
short_definition: "Recurrence Pressure occurs when the same failure pattern returns under similar stress, indicating unresolved hidden debt, incomplete repair, or persistent basin geometry."
canonical_pattern: "τ_m↑ + recurrence↑ ⇒ repair incomplete"
failure_signature: "Same pattern returns under similar forcing ⇒ underlying basin persists + hidden debt remains + restoration incomplete"
primary_variables:
  - O
  - H
  - ε
  - ι
  - Au
  - µᵢ
  - BΣ
  - K
  - R
  - Φ
primary_diagnostics:
  - τ_m
  - recurrence_rate
  - 𝓓(t)
  - H
  - R_eff
  - Au_eff
  - U_layer_localization
  - stress_condition_map
  - Φ_recovery
  - O_trend
related_failure_modes:
  - recurrence_lock
  - pseudo_restoration
  - symptom_suppression
  - hidden_debt_reactivation
  - basin_persistence
  - ring_down_failure
  - restoration_starvation
  - memory_failure
restoration_implication: "Map recurrence, identify stress triggers, localize the origin layer, repair hidden debt, alter basin geometry, and validate restoration through recurrence reduction."

11. One-Line Canon

A system is not repaired while the same failure keeps returning under the same kind of stress.