1. Definition

Consent drift occurs when the actual scope, purpose, depth, risk, consequence, or data flow of coupling changes without renewed structural consent.

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:

scope creep
consent stale
BΣ↓
Au↓
contract validity weakens

4. Primary U-Layer Origin

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

• rescope contract
• renew consent
• restore exit
• reveal changed conditions
• repair boundary debt

13. Cross-Module Links

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

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry

Aliases, parent modes, and child modes should be finalized during editorial review.

15. Minimal Entry Version

Definition: Consent drift occurs when the actual scope, purpose, depth, risk, consequence, or data flow of coupling changes without renewed structural consent.

Signature:

scope creep
consent stale
BΣ↓
Au↓
contract validity weakens

Restoration direction: - rescope contract

• renew consent
• restore exit
• reveal changed conditions
• repair boundary debt

16. Machine-Readable Summary

failure_mode:
  id: "FM-ISC-005"
  name: "Consent Drift"
  family: "Interactions Signals Couplings"
  production_treatment: "Standalone Entry"
  primary_failure: "Consent drift occurs when the actual scope, purpose, depth, risk, consequence, or data flow of coupling changes without renewed structural consent."
  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-005 — Consent Drift

Definition:

Consent drift occurs when the actual scope, purpose, depth, risk, consequence, or data flow of coupling changes without renewed structural consent.

Typical signature:

scope creep
consent stale
BΣ↓
Au↓
contract validity weakens

Primary variables:

BΣ, Au, Λ, µᵢ, H

Common origin layers:

U2, U5, U7

Related modules:

ISC · Security · AI · JGL · CMS · Economy

Restoration direction:

• rescope contract
• renew consent
• restore exit
• reveal changed conditions
• repair boundary debt