1. Short Definition
A Nested Sub Attractor is a smaller stabilizing pattern inside a larger basin that preserves identity, reward, role, status, belonging, justification, or survival.
2. Canonical Definition
In UTS, a Nested Sub Attractor is a local attractor embedded inside a wider attractor geometry.
It may not define the whole basin, but it helps keep the basin stable.
Examples include:
- a role reward
- a status ladder
- a belonging pattern
- a fear loop
- a compliance habit
- a legal justification
- a metric incentive
- a survival dependency
- a narrative identity
- a recurring workaround
Nested Sub Attractors explain why systems often return to a degraded basin even after the main failure has become visible.
3. Functional Role in UTS
Nested Sub Attractor analysis supports:
- basin mapping
- institutional diagnosis
- identity capture analysis
- governance review
- AI behavior review
- cultural analysis
- restoration design
- controlled decoupling
- supersession planning
It reveals the smaller locks that preserve the larger lock.
Canonical question:
Which smaller rewards or identities keep this basin stable?4. Diagnostic Signatures
Nested Sub Attractor active
local reward persists
identity binding↑
exit cost↑
τ_m↑
basin recurrence↑
H persistsSub-attractor mapped
reinforcement path visible
role / reward / fear / status loop identified
Au↑
transition path clearerSub-attractor dissolved
local reinforcement weakens
exit cost↓
old basin pull↓
K↑
O↑ over time5. Canonical Distinctions
Nested Sub Attractor is not the whole basin
It is a smaller stabilizing loop inside the basin.
Nested Sub Attractor is not always harmful
Some sub-attractors can preserve coherent local function.
Nested Sub Attractor is not just incentive
It may also be identity, memory, narrative, belonging, or fear.
Nested Sub Attractor is not solved by exposure alone
The reinforcement pattern must be changed.
6. U-Layer Mapping
| U-Layer | Nested Sub Attractor Expression |
|---|---|
| U0 | Material habit, dependency, or embodied pattern stabilizes return. |
| U1 | Resource reward or scarcity reinforces the loop. |
| U2 | Boundary, contract, or permission structure preserves it. |
| U3 | Execution routines reproduce it. |
| U4 | Narrative, status, role, or metric justifies it. |
| U5 | Timing and recurrence strengthen the loop. |
| U6 | Field coherence is affected by local reinforcement. |
| U7 | Memory stores the sub-attractor as precedent or identity. |
| U8 | Environmental pressure makes the sub-attractor feel necessary. |
7. Common Failure Patterns
| Failure Pattern | Description |
|---|---|
| Role Capture | A role reward keeps the node inside a degraded basin. |
| Status Loop | Status gain preserves incoherent participation. |
| Survival Dependency | Material need stabilizes a wrong basin. |
| Narrative Lock | Story identity prevents transition. |
| Recurrence Reinforcement | The sub-attractor increases basin memory half-life. |
8. Restoration Implications
Basin-aware restoration must identify and alter nested sub-attractors.
Typical sequence:
Μ map basin
→ identify nested sub-attractors
→ trace reward, identity, and dependency loops
→ restore Au
→ reduce exit cost
→ provide alternative support
→ weaken sub-attractor reinforcement
→ seed higher-order attractor
→ Τ validate recurrence shiftA basin transition becomes more viable when its sub-attractors no longer make the old basin easier to re-enter than the new one.
9. Machine-Readable Summary
glossary_entry:
id: "GL-166"
term: "Nested Sub Attractor"
symbols:
- "Τ"
- "τ_m(t)"
short_definition: "A smaller stabilizing pattern inside a larger basin that preserves identity, reward, role, status, belonging, justification, or survival."
term_family: "Core System Patterns"
term_class:
- "Core System Pattern"
- "Attractor Geometry"
- "Basin Stabilizer"
diagnostic_negative:
- "local reward persists"
- "identity binding↑"
- "exit cost↑"
- "τ_m↑"
- "basin recurrence↑"
- "H persists"
restoration_requirements:
- "sub-attractor mapping"
- "reward loop tracing"
- "identity loop tracing"
- "exit cost reduction"
- "alternative support"
- "higher-order attractor seeding"
- "time validation"