1. Definition
Exit denial occurs when a system punishes, blocks, hides, delays, prices out, or structurally prevents decoupling.
This definition describes the structural pattern, not the moral quality of the actors involved.
2. Core Pattern
TBD. Expand the initiating pressure, misclassification or bypass, variable degradation, debt accumulation, and stabilization pattern during editorial review.
3. Failure Signature
Typical signature:
exit penalty↑
⊗ locked
BΣ↓
dependency↑
H↑4. Primary U-Layer Origin
- U2, U6, U7: Source registry origin layer.
5. Typical Development Sequence
TBD. Add the development sequence during editorial review.
6. Diagnostic Markers
TBD. Add diagnostic markers only when supported by source material or later canon updates.
7. Related Gates
TBD. Add gate links during editorial review.
8. Related Operators
TBD. Add operator links during editorial review.
9. Related Laws and Invariants
TBD. Add law and invariant links during editorial review.
10. Common False Positives
TBD. Add false positives during editorial review.
11. Common False Repairs
TBD. Add false repairs during editorial review.
12. Restoration Direction
- restore exit path
- decouple safely
- repair coercive dependency
- audit contract legitimacy
- strengthen post-exit immunity
13. Cross-Module Links
- ISC: Source registry related module.
- Security: Source registry related module.
- CMS: Source registry related module.
- AI: Source registry related module.
- JGL: Source registry related module.
- Economy: Source registry related module.
14. Relationship to Parent / Child Modes
Production treatment: Standalone Entry
Aliases preserved from source material:
- Dependency Lock-In
- Locked-In Renegotiation Failure
- Exit Snap-Back.
15. Minimal Entry Version
Definition: Exit denial occurs when a system punishes, blocks, hides, delays, prices out, or structurally prevents decoupling.
Signature:
exit penalty↑
⊗ locked
BΣ↓
dependency↑
H↑Restoration direction: - restore exit path
- decouple safely
- repair coercive dependency
- audit contract legitimacy
- strengthen post-exit immunity
16. Machine-Readable Summary
failure_mode:
id: "FM-ISC-006"
name: "Exit Denial"
family: "Interactions Signals Couplings"
production_treatment: "Standalone Entry"
primary_failure: "Exit denial occurs when a system punishes, blocks, hides, delays, prices out, or structurally prevents decoupling."
source: "FM-REGISTRY-PLAN.md"17. Quality Control Checklist
TBD. Complete the template quality-control checklist before marking this entry ready.
18. Source Status
This scaffold was generated from FM-REGISTRY-PLAN.md. Matching excerpts from content/archive/failure-modes/registry/index.md were included when available. Sections marked TBD should be expanded only from source material, related canon pages, or later editorial review.
19. Source Excerpt
FM-ISC-006 — Exit Denial
Definition:
Exit denial occurs when a system punishes, blocks, hides, delays, prices out, or structurally prevents decoupling.
Merged aliases:
Dependency Lock-In; Locked-In Renegotiation Failure; Exit Snap-Back.
Typical signature:
exit penalty↑
⊗ locked
BΣ↓
dependency↑
H↑Primary variables:
BΣ, K, H, µᵢ, Λ
Common origin layers:
U2, U6, U7
Related modules:
ISC · Security · CMS · AI · JGL · Economy
Restoration direction:
- restore exit path
- decouple safely
- repair coercive dependency
- audit contract legitimacy
- strengthen post-exit immunity