0. Interaction Scope Note

This entry is conceptual and systems-oriented.

It does not treat structured repair, accountability pathways, therapy, mediation, appeals, grievance systems, remediation programs, governance processes, safety protocols, support plans, or long-duration restoration as inherently failed.

Some restoration requires sustained pathway commitment.

Some repair cannot be completed instantly.

A restoration pathway can preserve coherence when it is:

• outcome-bound
• burden-reducing
• agency-preserving
• consent-valid
• exit-aware
• revisable
• auditable
• compatible with the harm type
• responsive to affected-state change
• not dependent on endless participation
• not coercively singular
• not protecting the repair institution over the affected node
• able to transfer the node toward restored autonomy

The failure begins when the repair path becomes a trap.

The issue is not structured restoration.

The issue is a restoration pathway becoming more binding than restorative.

Restoration Lock-In occurs when the approved path to repair becomes the new constraint.

1. Definition

Restoration Lock-In occurs when a repair, healing, support, remediation, governance, appeal, accountability, or restoration pathway becomes the only permitted path forward, trapping affected nodes inside a fixed repair architecture even when that pathway no longer reduces burden, restores agency, fits the harm, or permits exit.

The locked pathway may involve:

• mediation process
• grievance procedure
• appeal pathway
• support plan
• therapy or wellness pathway
• restorative justice circle
• compliance remediation
• accountability program
• safety protocol
• AI appeal or redress flow
• moderation review
• institutional investigation
• compensation process
• repair committee
• governance pathway
• incident response process
• customer support escalation
• workplace improvement plan
• legal settlement process
• community reconciliation process
• medical or care plan
• spiritual or moral repair frame
• relationship repair routine
• organizational culture process

The core failure is:

repair path established
→ participation becomes required
→ exit / alternatives narrow
→ burden remains or rises
→ H↑

Restoration Lock-In is not a failed attempt at repair.

It is a repair attempt that becomes the structure preventing better repair.

2. Core Pattern

The core pattern is:

1. A harm, burden, breach, failure, conflict, or incoherence appears.
2. A restoration pathway is created or assigned.
3. The pathway initially offers legitimacy, structure, safety, visibility, or relief.
4. Over time, the pathway becomes mandatory, exclusive, or difficult to leave.
5. The affected node must keep participating to preserve standing.
6. Alternative repair paths are treated as invalid, disruptive, premature, or noncompliant.
7. The pathway’s continuation becomes more important than affected-state change.
8. The burden remains, shifts, or grows.
9. Hidden debt accumulates under restoration language.
10. Restoration requires restoring exit, alternative paths, and outcome-bound repair.

This failure often appears as:

they are in the repair process

while the hidden truth may be:

the repair process may be what is now holding them in burden

or:

they need to stay with the process

while the overlooked condition is:

the process must prove it is still reducing burden

The restorative question is:

is the pathway restoring autonomy, or creating dependency on the pathway?

Restoration Lock-In turns repair into a basin.

3. Failure Signature

Typical signature:

repair pathway↑
exit availability↓
alternative repair↓
participation load↑
affected-state change↓
H↑

Extended signature:

appeal process must be used but cannot correct outcome
therapy path continues while source burden remains
mediation required before remedy
support plan becomes condition for standing
accountability process replaces compensation
safety protocol blocks affected-node agency
AI redress flow loops without repair
restoration circle becomes obligation to remain engaged

Common forms include:

a harmed employee must stay in a grievance process that never changes the harmful conditions
a user must repeatedly appeal automated decisions through a process that cannot alter the model or policy
a community must participate in listening sessions to remain eligible for repair
a relationship requires endless repair conversations while the original boundary remains unrepaired
an institution requires mediation before acknowledging material remedy
a support plan teaches adaptation while source conditions stay unchanged
a compliance program locks cases into documented remediation without affected-state validation
a platform routes all redress into a support funnel that cannot restore lost access

The defining condition is not that a repair path exists.

The defining condition is that the repair path becomes non-exitable or non-revisable despite failing to restore.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: repair institutions benefit from keeping cases inside controlled pathways.
• U2 — Configuration / Boundaries: pathways lack exit, escalation, alternative, or failure criteria.
• U3 — Execution / Runtime: repair operations continue by procedure even after outcome failure.
• U4 — Information / Truth: participation in the path substitutes for restoration truth.
• U5 — Coordination / Time: prolonged pathway participation normalizes non-resolution.
• U6 — Coherence Field: restoration language creates legitimacy aura.
• U7 — Memory / Recurrence: prior process participation becomes proof of proper repair.
• U8 — Environment / Field: institutional, legal, therapeutic, platform, or governance systems reward process continuity.

Common manifestation layers:

• U2 — Boundaries: exit and alternative paths narrow.
• U3 — Execution: pathway continues.
• U4 — Truth: “in process” becomes repair status.
• U5 — Time: non-resolution becomes normal.
• U6 — Field: repair aura suppresses challenge.
• U7 — Memory: pathway history becomes standing requirement.

Restoration Lock-In is primarily a R restoration-capacity / BΣ boundary failure.

The repair pathway loses its function as a path and becomes a binding structure.

5. Typical Development Sequence

A common development sequence is:

1. A valid repair need appears.
2. The system creates or assigns a repair pathway.
3. Initial participation produces hope, order, or legitimacy.
4. The pathway does not reduce the core burden.
5. Affected node seeks alternative, escalation, exit, or direct remedy.
6. The system treats leaving the pathway as noncompliance or lack of readiness.
7. The affected node remains dependent on the pathway for standing, access, or recognition.
8. Repair capacity remains confined to the same architecture.
9. The pathway becomes self-protective.
10. Hidden debt accumulates through participation load and non-repair.

The loop often looks like:

harm → repair pathway → participation → non-resolution → more pathway participation

Another common loop is:

pathway fails → affected node asks for alternative → alternative denied because pathway is still active

Restoration Lock-In becomes self-reinforcing when the pathway’s failure creates the justification for staying inside the pathway longer.

6. Diagnostic Markers

Diagnostic markers include:

• Affected nodes must remain in the official process to retain standing.
• The pathway has no clear failure condition.
• Exit is framed as noncooperation.
• Alternatives are blocked because “a process already exists.”
• Participation load rises while burden reduction stalls.
• Repair metrics track engagement, attendance, or completion instead of affected-state change.
• The pathway protects the institution from direct remedy.
• Closure depends on process completion rather than restoration.
• Affected nodes become dependent on the process for recognition.
• The repair path cannot repair the source condition.
• The system treats process continuity as care, justice, or accountability.
• Restoration improves when exit, escalation, or alternative repair becomes available.

Useful diagnostics:

• Restoration Path Fit: Tests whether pathway matches harm type.
• Exit Availability: Determines whether affected nodes can leave without losing standing.
• Affected-State Change: Tests whether burdened nodes improve.
• Burden Reduction: Measures actual load reduction.
• Repair Participation Load: Tracks burden of staying in the pathway.
• Agency Preservation: Tests whether the pathway restores or reduces agency.
• Pathway Dependency: Measures dependence on process for recognition or access.
• Hidden Debt: Tracks burden accumulated through non-restorative participation.
• Auditability: Determines whether pathway outcomes can be inspected.
• Local Coherence: Tests whether the pathway improves actual conditions.

7. Related Gates

Relevant gates include:

• Restoration Path Gate: Fails when pathway continuation replaces outcome validation.
• Exit Gate: Fails when affected nodes cannot leave failed repair without penalty.
• Affected-State Gate: Fails when the pathway does not improve the burdened node.
• Burden Reduction Gate: Fails when participation does not reduce load.
• Compatibility Gate: Fails when pathway does not fit harm type.
• Auditability Gate: Fails when pathway effects cannot be inspected.
• Agency Gate: Fails when repair reduces autonomy rather than restoring it.
• Closure Gate: Fails when closure follows pathway completion rather than repair.
• Local Coherence Gate: Fails when the pathway degrades local viability.

The first common gate failure is usually the Restoration Path Gate.

The system treats the existence of a repair pathway as sufficient restoration legitimacy.

8. Related Operators

Relevant operators include:

• R — Restoration Capacity: Primary operator; should reduce burden but becomes trapped in pathway form.
• BΣ — Boundary Integrity: Preserves exit, scope, and agency boundaries.
• K — Constraint / Load: Rises when participation becomes burdensome.
• Au — Auditability: Tracks whether the path produces restoration.
• H — Hidden Debt: Accumulates through non-repair and participation load.
• Γ — Selection: Selects official pathway over direct remedy or alternative repair.
• Λ — Compatibility: Tests whether pathway fits harm type.
• Ψ — Observation / Interface: Shows the node as “in repair” or “noncompliant.”
• Φ — Flow / Resource Movement: Routes resources into process rather than burden reduction.
• Τ — Trajectory / Time: Tracks pathway duration, stagnation, and lock-in.
• D — Damping: Should prevent escalation but can over-damp exit.
• O — Coherence: May appear high because a process exists.
• G — Gain: Incentivizes process maintenance or institutional control.

Common operator pattern:

repair need appears
Γ selects official pathway
Ψ marks node as in process
Φ routes attention to pathway
R does not reach burden
BΣ exit boundary weakens
K participation load rises
O appears improved through structure
H accumulates

The core operator inversion is:

in repair process → being restored

instead of:

in repair process + burden reduction + agency restoration + affected-state change → being restored

Restoration Lock-In turns participation into proof.

9. Related Laws and Invariants

Related Laws

• Restoration Must Remain Revisable: repair paths must change when they fail.
• Repair Pathways Must Preserve Exit: affected nodes need alternatives when the path fails.
• Restoration Must Not Become Capture: repair cannot become dependency.
• Repair Must Reduce Burden: participation is not enough.
• Restoration Requires Affected-State Validation: pathway success is bounded by actual improvement.
• Process Must Serve Repair: structure is subordinate to restoration.
• Infinite Repair Loop: repeated pathway participation can become recursive non-repair.
• Therapeutic Capture: support path may replace source repair.
• Repair Burden Externalization: affected nodes may carry the repair pathway.
• Pseudo-Restoration: repair appearance substitutes for restoration.
• Hidden Debt Accumulation: non-repair stores future burden.
• Dependency Lock-In: pathway can create dependency or non-exitability.

Related Invariants

• Restoration Pathways Must Remain Outcome-Bound: process must answer to repair.
• Affected Nodes Must Retain Exit from Failed Repair: failed paths require alternatives.
• Repair Architecture Must Remain Auditable: pathway effects must be visible.
• Restoration Must Not Require Permanent Participation: repair should restore autonomy.
• Repair Must Preserve Agency: affected nodes should not be captured by the pathway.
• Restoration Path Must Match Harm Type: pathway compatibility matters.
• Lock-In Requires Revalidation and Remedy: if lock-in appears, repair must be rechecked.

10. Common False Positives

Not every long repair process is Restoration Lock-In.

Common false positives include:

• Long-duration repair that demonstrably reduces burden.
• Required process with clear escalation and exit paths.
• Therapy or support requested by affected nodes and paired with source repair.
• Appeal pathway that can actually reverse outcomes.
• Mediation after standing and remedy are preserved.
• Justice process with material repair and affected-state validation.
• Governance pathway with time limits, alternatives, and audits.
• Safety protocol that protects without trapping.
• Restoration process that becomes less burdensome over time.
• Repair pathway that changes when evidence shows mismatch.
• Phased restoration with clear termination criteria.
• Continued participation that remains voluntary and beneficial.

Clarifying rule:

This is not Restoration Lock-In unless the approved repair, support, appeal, accountability, or restoration pathway becomes compulsory, exclusive, non-exitable, or non-revisable while failing to reduce burden, restore agency, or improve the affected state.

11. Common False Repairs

Common false repairs include:

• adding another step to the same pathway
• requiring deeper participation
• extending the process timeline
• reframing exit as avoidance
• adding support to tolerate the pathway
• measuring engagement instead of restoration
• creating an appeal inside the same non-repairing architecture
• offering alternative language but not alternative repair
• assigning a new facilitator without changing authority
• asking affected nodes to trust the process longer
• reducing friction while preserving lock-in
• adding documentation of progress
• treating pathway fatigue as resistance
• making the pathway more compassionate without making it effective
• closing the case when participation ends

False repair often produces the loop:

restoration lock-in exposed → pathway improved → affected node remains trapped

Another common loop is:

pathway fails to restore → more pathway participation required → pathway burden grows

The repair fails because it improves the pathway while preserving lock-in.

12. Restoration Direction

Restoration requires auditing the pathway, restoring exit and alternatives, validating affected-state change, reducing participation burden, and ensuring the repair architecture remains outcome-bound rather than self-protective.

Primary restoration direction:

audit the pathway,
restore exit,
reopen alternatives,
and validate affected-state repair

A fuller restoration path includes:

1. Name the restoration pathway. Identify the process, support plan, appeal, mediation, governance, or repair architecture.
2. Name the original burden. Identify what the pathway was supposed to repair.
3. Test affected-state change. Determine whether the affected node is actually improving.
4. Measure participation load. Identify time, attention, emotional, administrative, financial, or standing burden.
5. Audit pathway fit. Determine whether the path matches harm type.
6. Identify lock-in mechanisms. Locate penalties for exit, lost standing, dependency, closed alternatives, or process monopoly.
7. Restore exit. Let affected nodes leave failed pathways without losing standing or remedy.
8. Reopen alternative repair paths. Provide direct remedy, escalation, compensation, decoupling, or source repair.
9. Reduce pathway burden. Remove unnecessary participation and proof load.
10. Reattach accountability. Ensure repair responsibility does not sit only with the affected node’s participation.
11. Create failure criteria. Define when the pathway must change or end.
12. Preserve auditability. Track burden reduction, not only process completion.
13. Repair lock-in debt. Address harm created by prolonged non-restorative participation.
14. Validate local coherence. Confirm the node regains agency, relief, and viable standing.

A valid restoration path should reduce:

pathway dependency
participation burden
non-exitable repair
failed-process legitimacy
agency loss
unrepaired burden
restoration debt
H

Restoration Lock-In is not repaired by making the repair path more beautiful.

It is repaired by making restoration possible outside the path.

13. Cross-Module Links

• Interactions / Signals / Couplings: Core ISC failure where a repair pathway becomes a binding coupling.
• Restoration: Restoration must reduce burden and restore autonomy, not create dependency.
• Justice: Grievance, appeal, mediation, testimony, accountability, and remedy pathways can become traps if non-exitable.
• Interfaces: Support flows, appeal portals, progress trackers, and repair dashboards can enforce pathway lock-in.
• AI Governance: Users can be trapped in AI appeal, redress, moderation, correction, or safety-support flows that cannot actually repair model/system harm.
• Organizations: HR processes, culture repair, mediation, and improvement plans can become compulsory non-repair.
• Cybernetics: Repair loops become closed basins when feedback does not change pathway structure.
• Diagnostics: Requires restoration-path-fit, exit-availability, affected-state, pathway-dependency, and hidden-debt diagnostics.
• Coherence: Coherent repair must restore agency and reduce burden, not stabilize dependency on repair infrastructure.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry

This mode maps upward to:

• FM-R-010 — Infinite Repair Loop
• FM-R-004 — Repair Burden Externalization
• FM-R-009 — Therapeutic Capture
• FM-ECO-026 — Dependency Lock-In
• FM-CORE-002 — Hidden Debt Accumulation

Sibling or related ISC modes include:

• FM-ISC-005 — Coupling Without Compatibility
• FM-ISC-006 — Asymmetric Bandwidth Coupling
• FM-ISC-007 — Premature Irreversible Coupling
• FM-ISC-008 — Coupling Under False Coherence
• FM-ISC-009 — Consent Drift
• FM-ISC-010 — Scope Creep
• FM-ISC-011 — Invisible Intrusion
• FM-ISC-013 — Empowerment Without Boundaries
• FM-ISC-014 — Reflection Without Integration
• FM-ISC-021 — Gate Bypass Normalization

Related cross-family modes include:

• FM-R-002 — Process Inflation
• FM-R-004 — Repair Burden Externalization
• FM-R-009 — Therapeutic Capture
• FM-R-010 — Infinite Repair Loop
• FM-ECO-026 — Dependency Lock-In
• FM-JC-004 — Under-Resourced Justice
• FM-JC-005 — Amnesty Without Repair
• FM-CORE-001 — Pseudo-Coherence
• FM-CORE-002 — Hidden Debt Accumulation
• FM-CORE-006 — U4 Truth Substitution
• FM-AIX-008 — Emotional Containment Without Repair
• FM-AIX-015 — User Agency Compression

Aliases preserved from source material:

• Restoration Lock-In
• Repair Lock-In
• Locked Restoration Pathway
• Restoration Path Capture
• Repair Path Capture
• Restoration Dependency Lock
• False Repair Lock-In
• Remediation Lock-In
• Accountability Path Lock-In
• Single-Path Restoration Trap

15. Minimal Entry Version

Definition: Restoration Lock-In occurs when a repair, healing, support, remediation, governance, appeal, accountability, or restoration pathway becomes the only permitted path forward, trapping affected nodes inside a fixed repair architecture even when that pathway no longer reduces burden, restores agency, fits the harm, or permits exit.

Signature:

repair pathway↑
exit availability↓
alternative repair↓
participation load↑
affected-state change↓
H↑

Restoration direction:

• name the restoration pathway
• name the original burden
• test affected-state change
• measure participation load
• audit pathway fit
• identify lock-in mechanisms
• restore exit
• reopen alternative repair paths
• reduce pathway burden
• reattach accountability
• create failure criteria
• preserve auditability
• repair lock-in debt
• validate local coherence

16. Machine-Readable Summary

failure_mode:
  id: "FM-ISC-012"
  name: "Restoration Lock-In"
  family: "Interactions / Signals / Couplings"
  production_treatment: "Standalone Entry"
  parent_modes:
    - "FM-R-010 — Infinite Repair Loop"
    - "FM-R-004 — Repair Burden Externalization"
    - "FM-R-009 — Therapeutic Capture"
    - "FM-ECO-026 — Dependency Lock-In"
    - "FM-CORE-002 — Hidden Debt Accumulation"
  primary_failure: "The approved repair, support, appeal, accountability, or restoration pathway becomes compulsory, exclusive, non-exitable, or non-revisable while failing to reduce burden, restore agency, or improve the affected state."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ISC-012"
  scope_note: "Conceptual and systems-oriented; does not treat structured repair, accountability pathways, therapy, mediation, appeals, grievance systems, remediation programs, governance processes, safety protocols, support plans, or long-duration restoration as inherently failed."
  aliases:
    - "Restoration Lock-In"
    - "Repair Lock-In"
    - "Locked Restoration Pathway"
    - "Restoration Path Capture"
    - "Repair Path Capture"
    - "Restoration Dependency Lock"
    - "False Repair Lock-In"
    - "Remediation Lock-In"
    - "Accountability Path Lock-In"
    - "Single-Path Restoration Trap"
  signature:
    - "repair pathway↑"
    - "exit availability↓"
    - "alternative repair↓"
    - "participation load↑"
    - "affected-state change↓"
    - "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:
    - "R"
    - "BΣ"
    - "K"
    - "Au"
    - "H"
    - "Γ"
    - "Λ"
    - "Ψ"
    - "Φ"
    - "Τ"
    - "D"
    - "O"
    - "G"
  first_gate_failure: "Restoration Path Gate"
  restoration:
    - "Restoration Path Audit"
    - "Exit Path Restoration"
    - "Affected-State Recheck"
    - "Repair Burden Reduction"
    - "Agency Restoration"
    - "Pathway Compatibility Review"
    - "Alternative Repair Path Reopening"
    - "Lock-In Debt Accounting"
    - "Closure Revalidation"
    - "Local Coherence Restoration"