1. Definition

Forced coupling occurs when a system is connected, integrated, observed, represented, constrained, made dependent, or required to participate without valid consent, compatibility, scope clarity, or exit.

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:

⊗ before Λ
⊗ forced
BΣ↓
exit blocked
Au asymmetric
H↑

4. Primary U-Layer Origin

• U2, U3, U5, U6: 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 consent
• test compatibility
• decouple safely
• repair boundary violation
• restore exit path
• validate contract legitimacy

13. Cross-Module Links

• ISC: Source registry related module.
• Security: Source registry related module.
• AI: Source registry related module.
• CMS: Source registry related module.
• JGL: Source registry related module.
• Economy: Source registry related module.
• Principles: Source registry related module.

14. Relationship to Parent / Child Modes

Production treatment: Canon Parent

Aliases preserved from source material:

• Coupling Without Compatibility
• ⊗ Without Λ
• Coercive Contract
• Dependency Lock-In
• Boundary-Violating Help
• Platform Lock-In.

15. Minimal Entry Version

Definition: Forced coupling occurs when a system is connected, integrated, observed, represented, constrained, made dependent, or required to participate without valid consent, compatibility, scope clarity, or exit.

Signature:

⊗ before Λ
⊗ forced
BΣ↓
exit blocked
Au asymmetric
H↑

Restoration direction: - restore consent

• test compatibility
• decouple safely
• repair boundary violation
• restore exit path
• validate contract legitimacy

16. Machine-Readable Summary

failure_mode:
  id: "FM-CORE-008"
  name: "Forced Coupling"
  family: "Core"
  production_treatment: "Canon Parent"
  primary_failure: "Forced coupling occurs when a system is connected, integrated, observed, represented, constrained, made dependent, or required to participate without valid consent, compatibility, scope clarity, or exit."
  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-CORE-008 — Forced Coupling

Definition:

Forced coupling occurs when a system is connected, integrated, observed, represented, constrained, made dependent, or required to participate without valid consent, compatibility, scope clarity, or exit.

Merged aliases:

Coupling Without Compatibility; ⊗ Without Λ; Coercive Contract; Dependency Lock-In; Boundary-Violating Help; Platform Lock-In.

Typical signature:

⊗ before Λ
⊗ forced
BΣ↓
exit blocked
Au asymmetric
H↑

Primary variables:

BΣ, Au, K, H, Λ, ⊗

Common origin layers:

U2, U3, U5, U6

Related modules:

ISC · Security · AI · CMS · JGL · Economy · Principles

Restoration direction:

• restore consent
• test compatibility
• decouple safely
• repair boundary violation
• restore exit path
• validate contract legitimacy