schema_version: "1.0"

id: "FM-R-005"

title: "FM-R-005 — Stabilization Freeze"

slug: "fm-r-005-stabilization-freeze"

type: "failure_mode"

status: "draft"

version: "0.1.0"

last_updated: "2026-06-19"

summary: "Stabilization Freeze occurs when a system reaches a calmer, less volatile, less visibly harmful, or more administratively manageable state after disruption and then treats that stabilized state as sufficient repair, preventing deeper restoration, adaptation, burden reduction, justice, or transition."

canonical_url: "/archive/failure-modes/registry/false-repair/fm-r-005-stabilization-freeze"

citation_id: "FM-R-005-v0-1-0"

canon:

tier: "registry"

state: "draft"

source: "UTS — Failure Modes Registry"

source_id: "FM-R-005"

classification:

family: "failure-modes"

module: "false-repair"

module_group: "restoration"

density: "advanced-reference"

audience:

• "UTS readers"
• "restoration researchers"
• "justice researchers"
• "cybernetics researchers"
• "organizational systems researchers"
• "AI governance researchers"
• "security researchers"
• "coherence researchers"
• "machine readers"

tags:

• "failure-modes"
• "false-repair"
• "stabilization-freeze"
• "fm-r-005-stabilization-freeze"
• "stabilization"
• "false-calm"
• "pseudo-restoration"
• "repair-freeze"
• "restoration-starvation"
• "hidden-debt"
• "coherence"

aliases:

• "Stabilization Freeze"
• "Stability Freeze"
• "False Stability Repair"
• "Stabilization as Closure"
• "Calm as Repair"
• "Frozen Stabilization"
• "Repair Freeze"
• "Post-Crisis Freeze"
• "Stabilized But Unrepaired"
• "False Calm Restoration"

related:

laws:

• "Pseudo-Restoration"
• "False Calm"
• "Suppressed Oscillation / False Calm"
• "Tyrant Stability Trap"
• "Pseudo-Coherence"
• "Hidden Debt Accumulation"
• "Restoration Starvation"
• "Reintegration Without Closure"
• "Delayed Transition Under Clarity"
• "Stasis / Blockage"
• "Over-Damped Brittleness"
• "Repair Suppression via Efficiency"

invariants:

• "Stabilization Is Not Restoration"
• "Calm Must Remain Auditable"
• "Repair Must Continue After Crisis Quieting"
• "Reduced Volatility Must Not Hide Burden"
• "Stability Must Include Restoration Capacity"
• "Post-Crisis States Must Remain Transitional"
• "Closure Requires Affected-State Repair"

operators:

• "D — Damping"
• "R — Restoration Capacity"
• "H — Hidden Debt"
• "O — Coherence"
• "K — Constraint / Load"
• "Au — Auditability"
• "Τ — Trajectory / Time"
• "Ψ — Observation / Interface"
• "Φ — Flow / Resource Movement"
• "BΣ — Boundary Integrity"
• "Γ — Selection"
• "Λ — Compatibility"
• "G — Gain"

gates:

• "Stabilization / Restoration Gate"
• "Affected-State Gate"
• "Hidden Debt Gate"
• "Transition Gate"
• "Restoration Gate"
• "Auditability Gate"
• "False Calm Gate"
• "Closure Gate"
• "Local Coherence Gate"

diagnostics:

• "Stabilization / Restoration Delta"
• "Affected-State Change"
• "Hidden Debt"
• "False Calm"
• "Residual Burden"
• "Restoration Capacity"
• "Transition Readiness"
• "Repair Continuity"
• "Auditability"
• "Local Coherence"

failure_modes:

• "FM-R-001 — Cosmetic Restoration"
• "FM-R-002 — Process Inflation"
• "FM-R-003 — Insight Without Load Reduction"
• "FM-R-004 — Repair Burden Externalization"
• "FM-R-006 — Repair as Compliance"
• "FM-R-007 — Repair Suppression via Efficiency"
• "FM-R-010 — Infinite Repair Loop"
• "FM-C-006 — Suppressed Oscillation / False Calm"
• "FM-C-008 — Over-Damped Brittleness"
• "FM-S-011 — Tyrant Stability Trap"
• "FM-ECO-032 — Pseudo-Coherent Economic Stability"
• "FM-RX-008 — Reintegration Without Time Validation"

restoration_arcs:

• "Stabilization / Restoration Audit"
• "False Calm Exposure"
• "Residual Burden Mapping"
• "Post-Stabilization Repair Continuation"
• "Hidden Debt Accounting"
• "Transition Path Reopening"
• "Affected-State Recheck"
• "Restoration Capacity Reallocation"
• "Closure Revalidation"
• "Local Coherence Restoration"

modules:

• "False Repair"
• "Restoration"
• "Cybernetics"
• "Justice"
• "Scaling"
• "Economy"
• "Security"
• "AI Governance"
• "Diagnostics"
• "Coherence"

navigation:

order: 1405

parent: "failure-modes"

visible: true

provenance:

created_from: "failure-mode-registry-production"

source_thread: "UTS Failure Modes Registry production"

source_file: "content/archive/failure-modes/registry/false-repair/fm-r-005-stabilization-freeze.md"

notes: "Expanded from False Repair family index entry and aligned to normalized metadata structure. Standalone false repair entry focused on stabilization, calm, reduced volatility, manageable state, post-crisis order, or frozen normalcy being mistaken for completed restoration while deeper burden remains unrepaired."

entry:

failure_mode_id: "FM-R-005"

failure_family: "False Repair"

production_treatment: "Standalone Entry"

parent_modes:

• "FM-C-006 — Suppressed Oscillation / False Calm"
• "FM-S-011 — Tyrant Stability Trap"
• "FM-RX-001 — Pseudo-Restoration"
• "FM-CORE-001 — Pseudo-Coherence"
• "FM-CORE-002 — Hidden Debt Accumulation"

first_gate_failure: "Stabilization / Restoration Gate"

primary_hidden_debt: "Hidden debt accumulates when the system stops repair after volatility decreases, leaving residual burdens, harms, constraints, dependencies, or affected-node damage stabilized rather than restored."

primary_inversion: "Stability becomes restoration; the system treats calm, reduced conflict, lower volatility, operational manageability, or crisis containment as proof that repair is complete."

primary_boundary_pattern: "The boundary between stabilization and restoration collapses; a temporary containment state is converted into a permanent repaired state."

primary_signature: "Crisis or visible disturbance decreases; system calm improves; repair pressure drops; affected-state burden remains; transition freezes; hidden debt accumulates under stabilized normalcy."

FM-R-005 — Stabilization Freeze

Status: Draft

Archive Type: Failure Mode

System: Universal Theory Stack

Parent: Failure Modes

Canon Tier: Registry

Registry: Failure Modes Registry

Entry ID: FM-R-005

Family: False Repair

Production Treatment: Standalone Entry

Parent Modes: FM-C-006 — Suppressed Oscillation / False Calm; FM-S-011 — Tyrant Stability Trap; FM-RX-001 — Pseudo-Restoration; FM-CORE-001 — Pseudo-Coherence; FM-CORE-002 — Hidden Debt Accumulation

0. False Repair Scope Note

This entry is conceptual and systems-oriented.

It does not treat stabilization, crisis containment, calming, de-escalation, temporary rest, reduced volatility, triage, pause, holding patterns, emergency order, or short-term control as inherently failed.

Stabilization can be necessary.

Some systems must first stop the bleeding before deeper repair can occur.

Stabilization can preserve coherence when it:

• prevents further harm
• protects affected nodes
• creates repair conditions
• preserves auditability
• remains explicitly temporary
• does not erase hidden debt
• does not request premature closure
• keeps restoration capacity active
• names residual burden
• preserves transition paths
• validates affected-state change
• leads into deeper repair

The failure begins when stabilization becomes the endpoint.

The issue is not calm.

The issue is calm being mistaken for restoration.

Stabilization Freeze occurs when the system stops moving toward repair because the visible crisis has quieted.

1. Definition

Stabilization Freeze occurs when a system reaches a calmer, less volatile, less visibly harmful, or more administratively manageable state after disruption and then treats that stabilized state as sufficient repair, preventing deeper restoration, adaptation, burden reduction, justice, or transition.

The stabilized state may appear as:

• reduced conflict
• reduced complaints
• lower volatility
• operational continuity
• temporary ceasefire
• quieted crisis
• stable dashboard
• lower incident rate
• paused escalation
• controlled narrative
• reduced churn
• lower visible distress
• administrative manageability
• restored routine
• surface calm
• crisis containment
• compliance equilibrium
• normalized workaround
• managed backlog
• stabilized dependency
• frozen settlement
• temporary patch
• lower public pressure

The core failure is:

volatility↓
visible crisis↓
repair pressure↓
residual burden remains
H↑

Stabilization Freeze is not successful stabilization.

It is stabilization that blocks restoration.

2. Core Pattern

The core pattern is:

1. A crisis, harm, instability, breach, burden, or conflict becomes visible.
2. The system acts to reduce immediate volatility.
3. Visible disturbance decreases.
4. Stakeholders feel relief.
5. The stabilized state is treated as proof that repair has occurred.
6. Deeper restoration, accountability, transition, or burden reduction is postponed.
7. Affected nodes remain in a constrained or damaged state.
8. The system resists reopening the issue because reopening feels destabilizing.
9. Hidden debt accumulates under calm.
10. Restoration requires distinguishing crisis containment from repair completion.

This failure often appears as:

things are stable now

while the hidden truth may be:

the burden is stable, not repaired

or:

we should not reopen this

while the overlooked condition is:

reopening may be required because the system never completed restoration

The restorative question is:

what remains unrepaired beneath the calm?

Stabilization Freeze turns containment into closure.

3. Failure Signature

Typical signature:

visible volatility↓
incident visibility↓
repair urgency↓
residual burden↑
transition motion↓
false calm↑
H↑

Extended signature:

conflict quiets while power asymmetry remains
incident rate drops while root cause persists
complaints fall because complaint paths are costly
support backlog stabilizes but does not clear
worker distress becomes normalized
security alerts quiet after suppression, not repair
AI harm reports decrease after reporting friction increases
settlement stabilizes optics while affected nodes remain unrepaired

Common forms include:

an organization stabilizes a crisis through silence agreements but does not repair harm
a platform reduces visible abuse reports by making reporting harder
a security system quiets alerts by raising thresholds while vulnerabilities remain
a team stops conflict by avoiding the unresolved issue
a public agency stabilizes case volume by closing intake
a company reduces churn through lock-in instead of value repair
an AI system appears safer after refusing more cases while user needs remain unmet
a justice process settles visible conflict while material remedy remains absent

The defining condition is not that the system becomes calmer.

The defining condition is that calm prevents restoration from continuing.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: stability is cheaper or safer than full repair.
• U2 — Configuration / Boundaries: crisis containment boundaries become permanent.
• U3 — Execution / Runtime: operations resume before repair is complete.
• U4 — Information / Truth: reduced visible disturbance substitutes for repair truth.
• U5 — Coordination / Time: temporary state freezes instead of transitioning.
• U6 — Coherence Field: calm creates relief and legitimacy.
• U7 — Memory / Recurrence: stabilization becomes the standard endpoint after crisis.
• U8 — Environment / Field: external pressure rewards order more than restoration.

Common manifestation layers:

• U2 — Boundaries: temporary containment hardens.
• U3 — Execution: routine resumes.
• U4 — Truth: calm becomes proof.
• U5 — Time: transition stalls.
• U6 — Field: relief suppresses further repair claims.
• U7 — Memory: freeze pattern repeats.

Stabilization Freeze is primarily a U5 transition and U4 truth-substitution failure.

The system mistakes a temporary holding state for a completed restoration state.

5. Typical Development Sequence

A common development sequence is:

1. A disruption or harm becomes visible.
2. Immediate stabilization is necessary.
3. The system reduces visible volatility.
4. Pressure drops.
5. Repair resources are redirected away from deeper work.
6. Affected nodes remain burdened but less visible.
7. The system restarts normal operations.
8. Further repair requests are framed as reopening old wounds, destabilizing the system, or being unreasonable.
9. The stabilized state becomes new normal.
10. Hidden debt remains unresolved.
11. Later instability reappears from the same buried source.

The loop often looks like:

crisis → stabilization → relief → repair deferred → residual burden → future crisis

Another common loop is:

conflict quiets → issue declared resolved → affected burden persists → conflict returns as surprise

Stabilization Freeze becomes self-reinforcing when each reopened burden is treated as a threat to stability rather than evidence of incomplete repair.

6. Diagnostic Markers

Diagnostic markers include:

• Crisis metrics improve but affected nodes still report burden.
• The system resists deeper repair because things are now calm.
• Temporary policies become permanent.
• Repair resources are withdrawn after visible volatility decreases.
• Root causes remain unchanged.
• Complaints or signals drop after access, reporting, or standing is reduced.
• Affected nodes adapt to the burden rather than recover from it.
• The system prioritizes not disturbing the stabilized state.
• Transition milestones disappear after crisis containment.
• Hidden debt remains stable or increases.
• The phrase “let’s not reopen this” appears before repair validation.
• Restoration improves when stabilization is treated as a phase rather than an endpoint.

Useful diagnostics:

• Stabilization / Restoration Delta: Compares calm with actual repair.
• Affected-State Change: Tests whether the burdened node improved.
• Hidden Debt: Tracks unresolved burden beneath calm.
• False Calm: Detects suppressed signals or quieted symptoms.
• Residual Burden: Measures what remains after stabilization.
• Restoration Capacity: Tests whether repair resources remain active.
• Transition Readiness: Determines whether the system can move beyond containment.
• Repair Continuity: Measures whether repair continues after crisis quiets.
• Auditability: Determines whether unresolved items remain visible.
• Local Coherence: Tests whether calm improves real affected states.

7. Related Gates

Relevant gates include:

• Stabilization / Restoration Gate: Fails when containment is counted as repair.
• Affected-State Gate: Fails when the affected node remains unrepaired.
• Hidden Debt Gate: Fails when residual burden is excluded from closure.
• Transition Gate: Fails when temporary stabilization cannot move to restoration.
• Restoration Gate: Fails when repair capacity is withdrawn after calm.
• Auditability Gate: Fails when unresolved burden becomes hard to trace.
• False Calm Gate: Fails when quiet signals are mistaken for resolved conditions.
• Closure Gate: Fails when closure occurs before restoration validation.
• Local Coherence Gate: Fails when calm does not improve local coherence.

The first common gate failure is usually the Stabilization / Restoration Gate.

The system treats reduced volatility as completed repair.

8. Related Operators

Relevant operators include:

• D — Damping: Primary operator; stabilization can damp volatility but may over-damp repair signals.
• R — Restoration Capacity: Must continue after stabilization.
• H — Hidden Debt: Accumulates when residual burden remains.
• O — Coherence: May appear high through calm.
• K — Constraint / Load: Remains on affected nodes if the system is only stabilized.
• Au — Auditability: Reveals unresolved burden after stabilization.
• Τ — Trajectory / Time: Tracks whether stabilization transitions into repair or freezes.
• Ψ — Observation / Interface: Determines whether quiet is visible as health.
• Φ — Flow / Resource Movement: Must keep resources moving toward repair.
• BΣ — Boundary Integrity: Prevents affected nodes from being locked into burden.
• Γ — Selection: Selects calm, repair, transition, or closure.
• Λ — Compatibility: Tests whether stabilized state fits long-term coherence.
• G — Gain: Incentivizes quick calming and optics preservation.

Common operator pattern:

crisis appears
D increases to stabilize
visible volatility drops
O appears improved
Γ selects closure or routine
Φ repair resources slow
K remains in affected nodes
Au weakens around residual burden
H accumulates
Τ transition freezes

The core operator inversion is:

calm → restored

instead of:

calm + affected-state repair + hidden-debt reduction + restoration continuity → restored

Stabilization Freeze turns damping into closure.

9. Related Laws and Invariants

Related Laws

• Pseudo-Restoration: restoration appearance replaces real repair.
• False Calm: quiet signals mask unresolved instability.
• Suppressed Oscillation / False Calm: oscillation is suppressed rather than resolved.
• Tyrant Stability Trap: stability protects an incoherent basin.
• Pseudo-Coherence: calm surface hides hidden debt.
• Hidden Debt Accumulation: residual burden persists beneath stability.
• Restoration Starvation: repair capacity is withdrawn or underfunded.
• Reintegration Without Closure: systems return before repair is validated.
• Delayed Transition Under Clarity: known next repair phase does not occur.
• Stasis / Blockage: stabilized state becomes stuck.
• Over-Damped Brittleness: excessive damping prevents adaptation.
• Repair Suppression via Efficiency: repair is avoided to preserve operational continuity.

Related Invariants

• Stabilization Is Not Restoration: containment is only a phase.
• Calm Must Remain Auditable: reduced disturbance must not hide residual burden.
• Repair Must Continue After Crisis Quieting: restoration cannot stop at de-escalation.
• Reduced Volatility Must Not Hide Burden: quiet does not equal relief.
• Stability Must Include Restoration Capacity: a stable state without repair is incomplete.
• Post-Crisis States Must Remain Transitional: stabilization should lead somewhere.
• Closure Requires Affected-State Repair: closure cannot rest on calm alone.

10. Common False Positives

Not every stabilized state is Stabilization Freeze.

Common false positives include:

• Crisis containment followed by active restoration.
• Temporary pause that protects affected nodes.
• De-escalation that preserves auditability and repair plans.
• Reduced volatility because root cause was actually repaired.
• Stabilized operations with funded hidden-debt reduction.
• Affected nodes requesting temporary calm before deeper repair.
• Holding pattern with clear review date and transition path.
• Emergency containment that does not claim closure.
• Lower incident rate paired with affected-state validation.
• Stability that remains open to disconfirmation.
• System calm that includes repair resources and standing.
• A phased restoration plan where stabilization is explicitly phase one.

Clarifying rule:

This is not Stabilization Freeze unless a calmer, less volatile, more manageable, or less visibly harmful state is treated as sufficient repair while deeper restoration, burden reduction, transition, or affected-state repair remains incomplete.

11. Common False Repairs

Common false repairs include:

• preserving calm at all costs
• discouraging affected nodes from raising unresolved issues
• treating renewed repair requests as destabilizing
• extending temporary containment indefinitely
• creating stability dashboards instead of restoration plans
• reducing complaint visibility
• rewarding teams for lowering incidents without checking root cause
• calling adaptation recovery
• freezing policy after crisis because change feels risky
• reclassifying residual burden as normal operations
• maintaining silence agreements as repair
• reopening only symbolic dialogue while material state remains frozen
• using settlement to lock the stabilized state
• treating lack of visible conflict as consent
• suppressing feedback to protect stability

False repair often produces the loop:

stabilization challenged → stability protected harder → unresolved burden becomes less visible

Another common loop is:

residual burden resurfaces → framed as threat to calm → burden suppressed again

The repair fails because it defends the stabilized state rather than restoring the damaged one.

12. Restoration Direction

Restoration requires distinguishing stabilization from restoration, auditing residual burden, preserving repair capacity after calm returns, reopening transition pathways, and validating affected-state change before closure.

Primary restoration direction:

treat stabilization as a phase,
audit residual burden,
continue repair,
and validate restoration before closure

A fuller restoration path includes:

1. Name the stabilized state. Identify what became calmer, quieter, safer-looking, or more manageable.
2. Name the original burden. Identify the harm, instability, debt, conflict, breach, or constraint that required repair.
3. Distinguish containment from repair. Determine what was stabilized versus what was restored.
4. Map residual burden. Identify what remains unrepaired.
5. Test affected-state change. Determine whether affected nodes actually improved.
6. Audit hidden debt. Identify debt hidden by the calmer state.
7. Preserve repair resources. Keep restoration capacity active after visible crisis quiets.
8. Reopen transition path. Move from containment into repair, reform, or reintegration.
9. Restore signal pathways. Allow unresolved burden to surface without being treated as destabilizing.
10. Validate closure criteria. Define what must be repaired before closure.
11. Reduce false calm. Distinguish real peace from suppressed signal.
12. Repair root causes. Address the source, not only the visible disturbance.
13. Validate over time. Confirm the stabilized state holds because burden is reduced.
14. Prevent recurrence. Block stabilization from satisfying restoration gates.

A valid restoration path should reduce:

false calm
residual burden
stabilized debt
transition blockage
premature closure
affected-node pressure
repair withdrawal
H

Stabilization Freeze is not repaired by destabilizing the system unnecessarily.

It is repaired by allowing calm to become the ground from which real repair continues.

13. Cross-Module Links

• False Repair: Core failure where stabilization replaces restoration.
• Restoration: Stabilization must remain a phase of restoration, not its substitute.
• Cybernetics: Stabilization can become over-damping or false calm when signals are suppressed.
• Justice: Settlement or de-escalation cannot replace remedy.
• Scaling: Large systems may freeze after crisis containment to avoid transition cost.
• Economy: Economic pseudo-stability often rests on stabilization freeze.
• Security: Alerts may quiet while vulnerabilities remain.
• AI Governance: Refusal-heavy safety posture, reduced reports, or policy freezes can look stable while user harm, appeal, or correction remains unrepaired.
• Diagnostics: Requires stabilization/restoration delta, residual burden, false calm, and repair continuity diagnostics.
• Coherence: Coherence requires stabilization to support transition into restoration.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry

This mode maps upward to:

• FM-C-006 — Suppressed Oscillation / False Calm
• FM-S-011 — Tyrant Stability Trap
• FM-RX-001 — Pseudo-Restoration
• FM-CORE-001 — Pseudo-Coherence
• FM-CORE-002 — Hidden Debt Accumulation

Sibling or related False Repair modes include:

• FM-R-001 — Cosmetic Restoration
• FM-R-002 — Process Inflation
• FM-R-003 — Insight Without Load Reduction
• FM-R-004 — Repair Burden Externalization
• FM-R-006 — Repair as Compliance
• FM-R-007 — Repair Suppression via Efficiency
• FM-R-008 — Audit Evasion in Repair
• FM-R-009 — Therapeutic Capture
• FM-R-010 — Infinite Repair Loop

Related cross-family modes include:

• FM-C-006 — Suppressed Oscillation / False Calm
• FM-C-008 — Over-Damped Brittleness
• FM-C-009 — Unproven Stability
• FM-S-011 — Tyrant Stability Trap
• FM-CORE-001 — Pseudo-Coherence
• FM-CORE-002 — Hidden Debt Accumulation
• FM-ECO-032 — Pseudo-Coherent Economic Stability
• FM-RX-008 — Reintegration Without Time Validation
• FM-RX-010 — Basin-Protective Repair
• FM-JC-012 — Silence Misread as Stability
• FM-AIX-003 — Defensive Compliance Attractor
• FM-SEC-010 — Emergency Normalization

Aliases preserved from source material:

• Stabilization Freeze
• Stability Freeze
• False Stability Repair
• Stabilization as Closure
• Calm as Repair
• Frozen Stabilization
• Repair Freeze
• Post-Crisis Freeze
• Stabilized But Unrepaired
• False Calm Restoration

15. Minimal Entry Version

Definition: Stabilization Freeze occurs when a system reaches a calmer, less volatile, less visibly harmful, or more administratively manageable state after disruption and then treats that stabilized state as sufficient repair, preventing deeper restoration, adaptation, burden reduction, justice, or transition.

Signature:

visible volatility↓
incident visibility↓
repair urgency↓
residual burden↑
transition motion↓
false calm↑
H↑

Restoration direction:

• name the stabilized state
• name the original burden
• distinguish containment from repair
• map residual burden
• test affected-state change
• audit hidden debt
• preserve repair resources
• reopen transition path
• restore signal pathways
• validate closure criteria
• reduce false calm
• repair root causes
• validate over time
• prevent recurrence

16. Machine-Readable Summary

failure_mode:
  id: "FM-R-005"
  name: "Stabilization Freeze"
  family: "False Repair"
  production_treatment: "Standalone Entry"
  parent_modes:
    - "FM-C-006 — Suppressed Oscillation / False Calm"
    - "FM-S-011 — Tyrant Stability Trap"
    - "FM-RX-001 — Pseudo-Restoration"
    - "FM-CORE-001 — Pseudo-Coherence"
    - "FM-CORE-002 — Hidden Debt Accumulation"
  primary_failure: "A calmer, less volatile, more manageable, or less visibly harmful state is treated as sufficient repair while deeper restoration, burden reduction, transition, or affected-state repair remains incomplete."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-R-005"
  scope_note: "Conceptual and systems-oriented; does not treat stabilization, crisis containment, calming, de-escalation, temporary rest, reduced volatility, triage, pause, holding patterns, emergency order, or short-term control as inherently failed."
  aliases:
    - "Stabilization Freeze"
    - "Stability Freeze"
    - "False Stability Repair"
    - "Stabilization as Closure"
    - "Calm as Repair"
    - "Frozen Stabilization"
    - "Repair Freeze"
    - "Post-Crisis Freeze"
    - "Stabilized But Unrepaired"
    - "False Calm Restoration"
  signature:
    - "visible volatility↓"
    - "incident visibility↓"
    - "repair urgency↓"
    - "residual burden↑"
    - "transition motion↓"
    - "false calm↑"
    - "H↑"
  primary_layers:
    origin:
      - "U1 — Power / Budgets"
      - "U2 — Configuration / Boundaries"
      - "U3 — Execution / Runtime"
      - "U4 — Information / Truth"
      - "U5 — Coordination / Time"
      - "U6 — Coherence Field"
      - "U7 — Memory / Recurrence"
      - "U8 — Environment / Field"
    manifestation:
      - "U2 — Boundaries"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U5 — Time"
      - "U6 — Field"
      - "U7 — Memory"
  state_variables:
    - "D"
    - "R"
    - "H"
    - "O"
    - "K"
    - "Au"
    - "Τ"
    - "Ψ"
    - "Φ"
    - "BΣ"
    - "Γ"
    - "Λ"
    - "G"
  first_gate_failure: "Stabilization / Restoration Gate"
  restoration:
    - "Stabilization / Restoration Audit"
    - "False Calm Exposure"
    - "Residual Burden Mapping"
    - "Post-Stabilization Repair Continuation"
    - "Hidden Debt Accounting"
    - "Transition Path Reopening"
    - "Affected-State Recheck"
    - "Restoration Capacity Reallocation"
    - "Closure Revalidation"
    - "Local Coherence Restoration"