1. Definition

Boundary collapse occurs when identity, consent, scope, exit, representation, permission, or interface clarity breaks down.

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:

BΣ↓
Perm unstable
scope ambiguity↑
exit penalty↑
over-coupling↑
identity confusion↑

4. Primary U-Layer Origin

• U2, U3, 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

• reconstitute boundaries
• restore consent validity
• scope coupling
• make exit possible
• reduce over-fusion
• repair boundary debt

13. Cross-Module Links

• ISC: Source registry related module.
• CMS: Source registry related module.
• Security: Source registry related module.
• AI: Source registry related module.
• JGL: Source registry related module.
• Cybernetics: Source registry related module.
• Principles: Source registry related module.
• Archetypes: Source registry related module.
• Biology: Source registry related module.

14. Relationship to Parent / Child Modes

Production treatment: Canon Parent

Aliases preserved from source material:

• Boundary Leakiness
• Boundary-Collapse Love
• Fusion Collapse
• AI Boundary Failure
• Manufactured Consent
• Boundary-Violating Help.

15. Minimal Entry Version

Definition: Boundary collapse occurs when identity, consent, scope, exit, representation, permission, or interface clarity breaks down.

Signature:

BΣ↓
Perm unstable
scope ambiguity↑
exit penalty↑
over-coupling↑
identity confusion↑

Restoration direction: - reconstitute boundaries

• restore consent validity
• scope coupling
• make exit possible
• reduce over-fusion
• repair boundary debt

16. Machine-Readable Summary

failure_mode:
  id: "FM-CORE-005"
  name: "Boundary Collapse"
  family: "Core"
  production_treatment: "Canon Parent"
  primary_failure: "Boundary collapse occurs when identity, consent, scope, exit, representation, permission, or interface clarity breaks down."
  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-005 — Boundary Collapse

Definition:

Boundary collapse occurs when identity, consent, scope, exit, representation, permission, or interface clarity breaks down.

Merged aliases:

Boundary Leakiness; Boundary-Collapse Love; Fusion Collapse; AI Boundary Failure; Manufactured Consent; Boundary-Violating Help.

Typical signature:

BΣ↓
Perm unstable
scope ambiguity↑
exit penalty↑
over-coupling↑
identity confusion↑

Primary variables:

BΣ, Perm, K, H, µᵢ, Λ

Common origin layers:

U2, U3, U6, U7

Related modules:

ISC · CMS · Security · AI · JGL · Cybernetics · Principles · Archetypes · Biology

Restoration direction:

• reconstitute boundaries
• restore consent validity
• scope coupling
• make exit possible
• reduce over-fusion
• repair boundary debt