1. Short Definition

U7 Recurrence Scaling Rule means that scaling is not validated until recurrence decreases under similar conditions.

If the same pattern returns after scale, the system did not repair the recurrence layer.

2. Canonical Pattern

recurrence↑ ⇒ basin not repaired

Expanded:

scale / repair / reform claims
+
same failure returns under similar forcing
⇒ hidden debt remains
⇒ U7 memory layer unresolved

Plain form:

Repetition reveals what the system still carries.

3. Mechanic Description

SCALE-070 applies scaling directly to U7, the memory and recurrence layer.

U7 tracks what persists across time:

• repeated failures
• recurring symptoms
• repeated conflicts
• recurring classifications
• repeated institutional breakdowns
• repeated AI failure modes
• recurring security incidents
• repeated biological activation
• repeated governance failures
• repeated debt return
• repeated basin re-entry
• recurring legitimacy shocks

A system may claim repair or successful scaling after a local fix.

But U7 asks:

Does the pattern come back?

If recurrence persists, the system may have repaired the visible symptom while leaving the memory, attractor, or hidden debt intact.

U7 recurrence is especially important because scaling often increases pressure on old patterns. A pattern that seems repaired at low load may return under higher scale, higher coupling, higher gain, or higher visibility pressure.

This rule prevents premature declarations of success.

Repair must reduce recurrence, not only reduce immediate error.

4. UTS Variable Mapping

5. Diagnostic Questions

1. Has this pattern returned before?
2. Does it return under similar stress?
3. Did prior repair reduce recurrence or only visible error?
4. Did scaling reactivate an old basin?
5. Is the same hidden debt returning through a new channel?
6. Is the memory layer updating?
7. Are repair claims being validated over time?
8. Is recurrence local or global?
9. Has ring-down improved across cycles?
10. What would have to change for recurrence to weaken?

6. Failure Signatures

1. Repeat Under Similar Forcing

similar forcing ⇒ same pattern returns

The system remains in the old recurrence geometry.

2. Repair Claim With Recurrence

repair_claim↑ while recurrence↑

The system declares repair while the pattern continues.

3. Scale-Reactivated Failure

Scale↑ ⇒ old pattern returns

Scaling exposes unresolved memory or basin structure.

4. Recurrence Channel Shift

H unresolved ⇒ recurrence appears through new domain

Debt returns in altered form.

5. Ring-Down Failure

𝓓(t)↓ across cycles

The system does not settle better over repeated perturbations.

7. Related Failure Modes

• recurrence lock
• U7 memory failure
• pseudo-restoration
• hidden debt return
• basin persistence
• scale-reactivated failure
• symptom suppression
• ring-down failure
• delayed transition cost
• local-global divergence
• restoration starvation

8. Related Diagnostics

9. Restoration Implications

If SCALE-070 is active, restoration must target recurrence geometry.

Required actions:

1. Map recurrence across time.
2. Identify repeated stress conditions.
3. Trace recurrence to hidden debt or basin structure.
4. Distinguish symptom reduction from recurrence reduction.
5. Repair the origin layer.
6. Update memory and learning systems.
7. Reduce scale pressure that reactivates unresolved patterns.
8. Improve ring-down across cycles.
9. Validate restoration under similar forcing.
10. Do not declare scaling success until recurrence weakens.

Core restoration rule:

Scaling is not validated until recurrence decreases.

10. Compact Registry Entry

id: SCALE-070
name: "U7 Recurrence Scaling Rule"
family: "SCALE-L — U-Layer Scaling Mechanics"
type: "memory-recurrence-validation-rule"
status: "draft-ready"
short_definition: "Scaling is not validated until recurrence decreases under similar conditions."
canonical_pattern: "recurrence↑ ⇒ basin not repaired"
failure_signature: "scale/repair/reform claims + same failure returns under similar forcing ⇒ hidden debt remains + U7 memory layer unresolved"
primary_variables:
  - O
  - H
  - ε
  - ι
  - Au
  - µᵢ
  - BΣ
  - K
  - R
  - Φ
primary_diagnostics:
  - τ_m
  - recurrence_rate
  - recurrence_context_similarity
  - H_origin
  - 𝓓(t)
  - R_eff
  - Au_temporal
  - O_trend
  - repair_claims
  - scale_reactivation_index
related_failure_modes:
  - recurrence_lock
  - U7_memory_failure
  - pseudo_restoration
  - hidden_debt_return
  - basin_persistence
  - scale_reactivated_failure
  - symptom_suppression
  - ring_down_failure
  - delayed_transition_cost
restoration_implication: "Map recurrence, trace hidden debt or basin geometry, repair the origin layer, update memory systems, validate under similar forcing, and withhold scaling success claims until recurrence weakens."

11. One-Line Canon

A scaled system is not repaired if the same failure returns when similar pressure returns.