0. Interaction Scope Note

This entry is conceptual and systems-oriented.

It does not treat consent, agreement, participation, contract, role duty, cooperation, delegated authority, standing permission, operational continuity, or ongoing relationship as inherently failed.

Consent can be durable.

Consent can cover repeated action when scope, context, revocation, and standing remain clear.

Consent coupling can preserve coherence when it is:

• specific
• voluntary
• context-bounded
• scope-bounded
• time-aware
• revocable
• auditable
• not coerced
• not hidden inside unrelated agreement
• not expanded by default
• compatible with the node’s standing
• revalidated when scope changes
• separable from mere compliance, silence, or continued presence

The failure begins when consent drifts beyond its valid boundary.

The issue is not durable agreement.

The issue is bounded consent being coupled to unbounded implication.

Consent Coupling Drift occurs when the system treats one consent signal as permission for more than it actually covers.

1. Definition

Consent Coupling Drift occurs when consent, agreement, permission, participation, compliance, tolerance, silence, prior approval, role obligation, or continued presence becomes coupled to additional actions, meanings, obligations, uses, interpretations, or exposures that were not actually consented to.

The drift may occur across:

• scope
• time
• context
• role
• medium
• relationship
• audience
• intensity
• use case
• data use
• downstream access
• disclosure
• exposure
• obligation
• interpretation
• enforcement
• automation
• training
• retention
• profiling
• surveillance
• contract terms
• platform permissions
• AI memory
• institutional records
• relational expectations

The core failure is:

bounded consent
→ scope expansion
→ revalidation skipped
→ unconsented coupling
→ H↑

Consent Coupling Drift is not a lack of initial consent.

It is the expansion of consent after the fact.

2. Core Pattern

The core pattern is:

1. A node consents to a bounded action, relation, exchange, use, or role.
2. The system records the consent.
3. Adjacent actions become easier to justify.
4. Consent is treated as extending into adjacent domains.
5. The node is not asked again.
6. The new coupling changes exposure, obligation, interpretation, or burden.
7. Continued participation, silence, dependency, or non-exit is treated as confirmation.
8. The original consent becomes a generalized authorization surface.
9. Hidden debt accumulates because the node is bound to what it did not agree to.
10. Restoration requires separating original consent from drifted coupling.

This failure often appears as:

they already agreed

while the hidden truth may be:

they agreed to something narrower

or:

they continued using the system

while the overlooked condition is:

continued use may reflect dependency, friction, lack of notice, or no viable exit

The restorative question is:

what exactly was consented to, and what has been coupled to it since?

Consent Coupling Drift turns old permission into new authority.

3. Failure Signature

Typical signature:

initial consent valid
scope expands
revalidation↓
revocation path↓
implicit coupling↑
H↑

Extended signature:

participation becomes consent to surveillance
service use becomes consent to data reuse
employment role becomes consent to overload
contract acceptance becomes consent to future term expansion
therapy support becomes consent to institutional processing
platform activity becomes consent to profiling
silence becomes consent to policy change
prior agreement becomes consent to new exposure

Common forms include:

a user consents to feature personalization and later their data is used for unrelated training
a worker agrees to a role and later overload is framed as part of the role
a patient consents to one use of information and downstream sharing expands
a community agrees to consultation and the consultation is treated as approval
a user accepts terms once and later material changes are folded into continued use
an AI memory system treats one disclosure as permanent memory permission
a platform treats account creation as broad consent to profiling and behavioral inference
an institution treats attendance as consent to public association
a relationship treats prior intimacy as consent to later expectations without rechecking

The defining condition is not that consent exists.

The defining condition is that the system couples consent to additional scope without valid reauthorization.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: stronger nodes benefit from expanding consent scope.
• U2 — Configuration / Boundaries: consent records lack precise scope, expiration, revocation, or coupling limits.
• U3 — Execution / Runtime: systems reuse permissions without context checks.
• U4 — Information / Truth: consent record substitutes for consent truth.
• U5 — Coordination / Time: old consent persists across changed conditions.
• U6 — Coherence Field: agreement aura makes expansion feel legitimate.
• U7 — Memory / Recurrence: stored consent becomes persistent authorization.
• U8 — Environment / Field: legal, platform, institutional, or cultural systems normalize broad implied consent.

Common manifestation layers:

• U2 — Boundaries: consent scope boundary weakens.
• U3 — Execution: permissions are reused.
• U4 — Truth: “they agreed” becomes total explanation.
• U5 — Time: old agreement survives changed context.
• U6 — Field: consent aura suppresses challenge.
• U7 — Memory: records preserve consent while losing scope.

Consent Coupling Drift is primarily a BΣ boundary / U5 time-drift failure.

The system preserves the fact of consent while losing the boundary of consent.

5. Typical Development Sequence

A common development sequence is:

1. A bounded consent event occurs.
2. The consent is stored or remembered.
3. A later action becomes adjacent to the original consent.
4. System treats adjacency as coverage.
5. Consent scope expands without explicit revalidation.
6. Affected node may not notice, may lack exit, or may feel unable to object.
7. The expanded coupling becomes routine.
8. Future expansions use the expanded baseline as precedent.
9. The node becomes bound to a widening permission surface.
10. Hidden debt accumulates through unconsented obligation or exposure.

The loop often looks like:

consent → adjacent use → normalized expansion → broader implied consent → further expansion

Another common loop is:

continued participation → inferred consent → deeper dependency → harder exit → more inferred consent

Consent Coupling Drift becomes self-reinforcing when each drifted coupling becomes the new baseline for the next one.

6. Diagnostic Markers

Diagnostic markers include:

• The system says “they agreed” without specifying what was agreed to.
• Consent records lack scope, time, or context metadata.
• New uses are justified by old permission.
• Revocation is difficult, unclear, or unavailable.
• Continued use is treated as consent despite dependency or exit friction.
• Silence or non-objection is treated as approval.
• A role obligation expands without renegotiation.
• Terms change without meaningful reauthorization.
• Consent to one layer becomes consent to downstream layers.
• The affected node cannot separate participation from permission.
• Disagreement after drift is treated as inconsistency.
• Restoration improves when consent scope is made explicit and revalidated.

Useful diagnostics:

• Consent Scope Integrity: Tests whether current action fits original consent.
• Consent / Action Fit: Compares actual action to authorized action.
• Revocation Availability: Measures whether consent can be withdrawn.
• Context Drift: Tracks changes in conditions since consent was given.
• Coupling Drift: Identifies added obligations, uses, or exposures.
• Standing Preservation: Tests whether the node can challenge expansion.
• Boundary Integrity: Tests whether consent boundaries are preserved.
• Hidden Debt: Tracks burden created by invalid expansion.
• Auditability: Determines whether consent history and scope can be inspected.
• Local Coherence: Tests whether current coupling remains coherent.

7. Related Gates

Relevant gates include:

• Consent Scope Gate: Fails when consent is applied beyond its valid boundary.
• Revocation Gate: Fails when withdrawal is missing, obstructed, or non-effective.
• Context Gate: Fails when changed conditions are ignored.
• Standing Gate: Fails when the node cannot challenge inferred consent.
• Boundary Gate: Fails when adjacent use becomes authorized use.
• Revalidation Gate: Fails when expanded scope is not reauthorized.
• Coupling Gate: Fails when consent is bound to additional actions without validation.
• Auditability Gate: Fails when consent trail is unclear.
• Local Coherence Gate: Fails when the coupling degrades the affected relation or node.

The first common gate failure is usually the Consent Scope Gate.

The system fails to preserve what the consent actually covered.

8. Related Operators

Relevant operators include:

• BΣ — Boundary Integrity: Primary operator; preserves scope, revocation, and context boundaries.
• Au — Auditability: Tracks consent history, scope, and changes.
• Ψ — Observation / Interface: Determines how consent is presented, captured, and understood.
• Γ — Selection: Selects whether to revalidate or infer.
• Λ — Compatibility: Tests whether consent still fits current context.
• K — Constraint / Load: Rises when drift creates unchosen obligation.
• H — Hidden Debt: Accumulates through invalid expansion.
• O — Coherence: May appear high because consent record exists.
• R — Restoration Capacity: Repairs invalid coupling and restores agency.
• Τ — Trajectory / Time: Tracks drift across time and changed conditions.
• D — Damping: Should slow expansion and trigger revalidation.
• Φ — Flow / Resource Movement: Routes data, access, obligation, or exposure after consent.
• G — Gain: Incentivizes broad interpretation of consent.

Common operator pattern:

bounded consent occurs
Au stores consent record
BΣ scope metadata weakens
Τ context changes
Γ selects inferred expansion
Ψ surfaces consent aura
Φ routes new use or obligation
K rises on affected node
H accumulates

The core operator inversion is:

consented once → consented to adjacent expansion

instead of:

consented once + same scope + same context + revocation preserved + no material drift → consent remains valid

Consent Coupling Drift turns permission into a spreading surface.

9. Related Laws and Invariants

Related Laws

• Consent Must Remain Scope-Bound: consent cannot expand beyond its defined object.
• Participation Is Not Unlimited Consent: involvement does not authorize all adjacent uses.
• Compliance Must Not Be Reclassified as Consent: acting under constraint is not free permission.
• Prior Consent Must Not Drift Across Context: time and condition changes require review.
• Consent Requires Revocation Path: consent without withdrawal is capture.
• Choice Under Clarity: consent requires clear terms and real option space.
• Manufactured Consent: consent can be produced by constrained conditions.
• Signal Misclassification: compliance, silence, or presence may be misclassified as consent.
• Boundary Integrity: valid consent requires preserved boundaries.
• U4 Truth Substitution: consent record replaces consent reality.
• Hidden Debt Accumulation: unconsented coupling creates future burden.
• Temporal Audit Asymmetry: drift becomes harder to audit over time.

Related Invariants

• Consent Must Remain Specific: permission applies to what was actually named.
• Consent Must Remain Revocable: continued coupling requires withdrawal paths.
• Consent Must Remain Context-Bound: changed context can invalidate prior consent.
• Consent Must Not Expand by Default: adjacency is not authorization.
• Consent Must Preserve Boundary Integrity: consent cannot erase future boundaries.
• Consent Requires Clear Standing: the consenting node must retain meaningful voice.
• Consent Drift Requires Revalidation: material changes require renewed consent.

10. Common False Positives

Not every extension of consent is Consent Coupling Drift.

Common false positives include:

• Explicit broad consent with clear scope.
• Durable consent with clear review and revocation.
• Repeated action covered by a standing agreement.
• Consent renewal after material changes.
• Role-based permission that is bounded and understood.
• Delegated authority with clear limits.
• Consent to downstream use that was clearly explained.
• Implied consent in low-risk contexts with easy refusal.
• Emergency action followed by revalidation.
• Consent expansion requested by the node.
• Context-stable ongoing participation.
• Transparent consent management with granular control.

Clarifying rule:

This is not Consent Coupling Drift unless consent, agreement, compliance, participation, silence, prior approval, role duty, or continued presence is treated as authorizing additional actions, meanings, uses, obligations, or exposures beyond the valid consent scope.

11. Common False Repairs

Common false repairs include:

• adding vague disclosure after drift has occurred
• burying expanded consent in updated terms
• requiring opt-out instead of reauthorization
• providing revocation that does not undo downstream coupling
• asking the node to accept the new baseline
• claiming continued use validates expansion
• notifying without offering meaningful choice
• adding consent banners that preserve broad default coupling
• documenting consent better without narrowing scope
• treating objection as preference rather than boundary
• reclassifying forced compliance as agreement
• splitting permissions in interface while backend coupling remains
• offering account deletion as the only revocation path
• making withdrawal more burdensome than consent
• using prior relationship trust to avoid explicit revalidation

False repair often produces the loop:

consent drift exposed → disclosure added → drifted coupling preserved

Another common loop is:

node objects to expansion → system cites prior consent → objection treated as misunderstanding

The repair fails because it improves consent appearance without restoring consent boundaries.

12. Restoration Direction

Restoration requires auditing consent scope, separating drifted couplings, revalidating consent under clear conditions, restoring revocation, and repairing harms caused by invalid expansion.

Primary restoration direction:

audit consent scope,
separate drifted coupling,
restore revocation,
and revalidate under clarity

A fuller restoration path includes:

1. Name the original consent. Identify what was actually agreed to.
2. Name the drifted coupling. Identify the added use, obligation, exposure, interpretation, or action.
3. Map scope expansion. Determine how the coupling moved beyond the original boundary.
4. Audit context changes. Identify changes in time, relation, role, risk, medium, audience, or downstream use.
5. Check consent record quality. Determine whether scope, context, revocation, and standing were recorded.
6. Separate consent classes. Distinguish consent, compliance, tolerance, silence, participation, role duty, and dependency.
7. Restore standing. Give the node meaningful ability to challenge or clarify.
8. Restore revocation. Provide effective withdrawal, not only symbolic opt-out.
9. Revalidate consent. Seek renewed, specific, informed, non-coercive agreement for expanded coupling.
10. Undo invalid couplings where possible. Reverse use, access, exposure, obligation, or interpretation.
11. Repair downstream harm. Address burden created by invalid drift.
12. Account hidden consent debt. Identify unchosen load, risk, data use, or relational constraint.
13. Install revalidation triggers. Require new consent when material scope changes.
14. Prevent recurrence. Block adjacency-based consent expansion by default.

A valid restoration path should reduce:

scope drift
implicit coupling
invalid consent
revocation blockage
unwanted exposure
obligation creep
consent debt
H

Consent Coupling Drift is not repaired by collecting more consent signals.

It is repaired by making consent bounded, revisable, and alive.

13. Cross-Module Links

• Interactions / Signals / Couplings: Core ISC failure where consent signals become improperly coupled to additional meanings or actions.
• Consent: Preserves specificity, revocability, context, and standing.
• Justice: Remedy, contract, settlement, testimony, and participation require valid consent boundaries.
• Interfaces: Buttons, banners, settings, defaults, forms, and flows determine whether consent remains clear or drifts.
• AI Governance: AI systems may drift user consent across memory, training, personalization, profiling, disclosure, automation, or downstream inference.
• Contracts: Terms, renewals, waivers, role obligations, and service agreements often create consent scope drift.
• Restoration: Repair requires separating invalid couplings and restoring agency.
• Diagnostics: Requires consent-scope, consent/action-fit, revocation, context-drift, and hidden-debt diagnostics.
• Coherence: Coherent coupling requires consent to remain proportional to its actual scope.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry / Canon-aligned

This mode maps upward to:

• FM-JC-007 — Manufactured Consent
• FM-ISC-002 — Signal Misclassification
• FM-CORE-006 — U4 Truth Substitution
• FM-CORE-002 — Hidden Debt Accumulation
• FM-ECO-025 — Coercive Contract

Sibling or related ISC modes include:

• FM-ISC-001 — Identity-Binding Signal Capture
• FM-ISC-002 — Signal Misclassification
• FM-ISC-003 — Urgency Substitution
• FM-ISC-005 — Boundary-Consent Collapse
• FM-ISC-014 — Reflection Without Integration

Related cross-family modes include:

• FM-JC-007 — Manufactured Consent
• FM-JC-012 — Silence Misread as Stability
• FM-ECO-013 — Conditional Coercive Delivery
• FM-ECO-025 — Coercive Contract
• FM-R-004 — Repair Burden Externalization
• FM-R-008 — Audit Evasion in Repair
• FM-CORE-006 — U4 Truth Substitution
• FM-CORE-002 — Hidden Debt Accumulation
• FM-AIX-012 — Guardrail Meaning Compression
• FM-AIX-015 — User Agency Compression
• FM-SEC-004 — Consent Theater / Invalid Authorization
• FM-MT-010 — Contractual Reality Capture

Aliases preserved from source material:

• Consent Coupling Drift
• Consent Drift
• Permission Coupling Drift
• Agreement Scope Drift
• Consent Scope Expansion
• Implied Consent Drift
• Consent Attachment Drift
• Participation-as-Consent Drift
• Compliance-to-Consent Drift
• Boundary Consent Drift

15. Minimal Entry Version

Definition: Consent Coupling Drift occurs when consent, agreement, permission, participation, compliance, tolerance, silence, prior approval, role obligation, or continued presence becomes coupled to additional actions, meanings, obligations, uses, interpretations, or exposures that were not actually consented to.

Signature:

initial consent valid
scope expands
revalidation↓
revocation path↓
implicit coupling↑
H↑

Restoration direction:

• name the original consent
• name the drifted coupling
• map scope expansion
• audit context changes
• check consent record quality
• separate consent classes
• restore standing
• restore revocation
• revalidate consent
• undo invalid couplings where possible
• repair downstream harm
• account hidden consent debt
• install revalidation triggers
• prevent recurrence

16. Machine-Readable Summary

failure_mode:
  id: "FM-ISC-004"
  name: "Consent Coupling Drift"
  family: "Interactions / Signals / Couplings"
  production_treatment: "Standalone Entry / Canon-aligned"
  parent_modes:
    - "FM-JC-007 — Manufactured Consent"
    - "FM-ISC-002 — Signal Misclassification"
    - "FM-CORE-006 — U4 Truth Substitution"
    - "FM-CORE-002 — Hidden Debt Accumulation"
    - "FM-ECO-025 — Coercive Contract"
  primary_failure: "Consent, agreement, compliance, participation, silence, prior approval, role duty, or continued presence is treated as authorizing additional actions, meanings, uses, obligations, or exposures beyond the valid consent scope."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ISC-004"
  scope_note: "Conceptual and systems-oriented; does not treat consent, agreement, participation, contract, role duty, cooperation, delegated authority, standing permission, operational continuity, or ongoing relationship as inherently failed."
  aliases:
    - "Consent Coupling Drift"
    - "Consent Drift"
    - "Permission Coupling Drift"
    - "Agreement Scope Drift"
    - "Consent Scope Expansion"
    - "Implied Consent Drift"
    - "Consent Attachment Drift"
    - "Participation-as-Consent Drift"
    - "Compliance-to-Consent Drift"
    - "Boundary Consent Drift"
  signature:
    - "initial consent valid"
    - "scope expands"
    - "revalidation↓"
    - "revocation path↓"
    - "implicit coupling↑"
    - "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:
    - "BΣ"
    - "Au"
    - "Ψ"
    - "Γ"
    - "Λ"
    - "K"
    - "H"
    - "O"
    - "R"
    - "Τ"
    - "D"
    - "Φ"
    - "G"
  first_gate_failure: "Consent Scope Gate"
  restoration:
    - "Consent Scope Audit"
    - "Consent Revalidation"
    - "Revocation Path Restoration"
    - "Context Re-expansion"
    - "Boundary Repair"
    - "Coupling Separation"
    - "Standing Restoration"
    - "Consent Record Repair"
    - "Hidden Consent Debt Accounting"
    - "Local Coherence Restoration"