0. Plain Statement

Consent is a boundary state, not a checkbox.

Plain-language version:

Consent is not valid just because a person clicked, signed, complied, answered, stayed, or failed to object. Consent is valid only when the surrounding structure preserves real boundary choice.

1. Formal Definition

The Consent Structurality Law states that consent is a boundary condition produced by the full state-space around a decision, not a surface signal.

A checkbox, signature, click, silence, agreement, form submission, biometric action, verbal yes, contract acceptance, or continued participation may signal consent, but it does not prove consent by itself.

Consent is valid only when the node has enough boundary integrity, auditability, scope clarity, exit capacity, non-coercive timing, and practical sovereignty to choose.

Consent fails when the structure around the decision collapses choice into compulsion.

This law protects against consent theater: systems that record formal agreement while the actual state-space makes refusal impossible, unintelligible, unsafe, costly, hidden, or invalid.

2. Canonical Form

formal consent signal ≠ valid consent state

Expanded canonical form:

consent is valid only when BΣ, K, Au, scope clarity, exit capacity, non-coercive pressure, and repair path remain intact

Failure expression:

checkbox / signature / compliance + invalid boundary state ⇒ consent collapse

Invalidity conditions:

urgency
audit suppression
exit penalties
identity-binding low evidence
coercive dependency
asymmetric constraint pressure
hidden scope change
survival coercion

Related variables:

O, H, ε, ι, Au, R, BΣ, K, µᵢ, Φ, Γ, Π, Σ, Θ, Ψ, Λ, ⊗

Where:

3. Core Mechanism

The Consent Structurality Law unfolds when a system treats an observable consent signal as sufficient proof of valid consent.

Coherent consent pathway

request for coupling appears
→ scope is clear
→ boundary state is intact
→ exit is available
→ auditability is sufficient
→ pressure is non-coercive
→ compatibility is checked
→ consent is given or refused
→ repair path remains available
→ coupling proceeds only if valid

Consent-collapse pathway

request for coupling appears
→ urgency / dependency / exit penalty / hidden scope is present
→ checkbox or signature is collected
→ system records consent
→ boundary state is invalid
→ coupling proceeds anyway
→ hidden debt accumulates
→ legitimacy and coherence decline

The core mechanism is:

formal agreement is not valid consent unless the state-space permits real refusal

Consent is a membrane condition, not a UI event.

4. When This Law Applies

This law applies whenever a system records, relies on, enforces, interprets, or claims consent.

It is especially important in:

• contracts;
• employment agreements;
• platform terms;
• AI memory and representation;
• data sharing;
• medical consent;
• governance participation;
• institutional procedures;
• economic contracts;
• security monitoring;
• surveillance;
• identity verification;
• spiritual or relational coupling;
• research participation;
• user onboarding;
• reintegration;
• disclosure;
• opt-in / opt-out systems;
• appeals and waiver systems.

The law applies strongly when:

formal consent signal is used to authorize coupling or constraint

or when:

the consenting node faces urgency, dependency, exit penalties, hidden scope, survival pressure, or audit suppression

Typical domains:

5. When This Law Does Not Apply

This law should not be used to deny all formal consent mechanisms.

Forms, signatures, checkboxes, agreements, verbal confirmation, consent flows, contracts, and opt-ins can be useful when they are embedded in valid boundary conditions.

This law does not reject formal consent signals. It rejects treating them as sufficient.

Formal consent can support valid consent when:

• scope is clear;
• auditability is preserved;
• exit is possible;
• refusal does not trigger excessive penalty;
• no hidden scope change exists;
• pressure is not coercive;
• dependency does not collapse choice;
• identity-binding low evidence is absent;
• the consenting node has enough time and capacity;
• repair and revocation paths exist.

False-positive cases:

Important distinction:

Formal consent signals are useful evidence. They are not consent itself.

6. Diagnostic Signature

The basic diagnostic signature is:

formal consent signal ≠ valid consent state

A stronger warning signature:

checkbox / signature / compliance present
BΣ compromised
K↓
Au suppressed
exit costly
scope unclear
dependency high
H↑
⇒ consent collapse

Common indicators:

Additional diagnostics:

7. Failure Pattern

If ignored, this law produces consent theater, contract inversion, hidden debt, and legitimacy collapse.

General failure pathway:

system requests agreement
→ formal consent signal is collected
→ boundary state is not tested
→ scope / exit / audit / pressure conditions are invalid
→ coupling or constraint proceeds
→ affected node loses agency
→ hidden debt accumulates
→ legitimacy shock appears later

Common failure modes:

• Consent Collapse — formal agreement exists but boundary-state consent is invalid.
• Checkbox Consent — UI signal replaces structural consent.
• Boundary Violation — coupling proceeds across invalid boundary state.
• Coercive Dependency — dependency collapses refusal.
• Survival Coercion — material survival pressure invalidates agreement.
• Exit Penalty Capture — withdrawal cost makes refusal non-real.
• Hidden Scope Change — consent silently expands beyond original scope.
• Audit Suppression — terms, consequences, or data flows cannot be inspected.
• Identity-Binding Coercion — identity pressure distorts choice.
• Invalid Coupling — coupling proceeds without valid consent.
• Contract Inversion — contract enforcement violates coherence conditions.
• Hidden Debt Accumulation — invalid consent creates future repair burden.

Compact failure signature:

formal consent + invalid BΣ/K/Au/exit/scope ⇒ consent debt

8. Restoration Implications

Restoration requires re-evaluating consent as a boundary state, not merely checking whether a consent artifact exists.

The first restoration question is not:

Did they click agree?

The first restoration question is:

Was the boundary state valid enough for consent to be real?

Restoration priorities:

1. Identify the formal consent signal.
2. Audit the state-space surrounding the decision.
3. Check urgency, dependency, scope, exit, auditability, and pressure.
4. Check whether identity-binding low evidence distorted the choice.
5. Check whether scope changed after consent.
6. Suspend enforcement if consent validity fails.
7. Restore boundary integrity and practical refusal capacity.
8. Provide revocation, appeal, rollback, and repair paths.
9. Re-consent only after structural conditions are valid.
10. Time-validate that hidden debt and recurrence decrease.

Relevant restoration arcs:

Minimal restoration sequence:

identify consent signal
→ audit boundary state
→ test invalidity conditions
→ suspend invalid enforcement
→ restore BΣ / K / Au / exit / scope
→ repair harmed node
→ re-consent if conditions become valid
→ validate H↓ and recurrence↓

Temporal validation requirement:

BΣ restored
K / σ sufficient
Au↑
scope clear
exit permitted
dependency pressure reduced
hidden scope changes absent
R available
H↓
recurrence↓
consent remains revocable and auditable

9. Design Rule

Do not treat a consent artifact as valid unless the surrounding boundary state preserves real choice.

Operational design requirements:

• Treat consent as a state-space property.
• Record scope clearly.
• Preserve auditability.
• Preserve exit and revocation.
• Avoid urgency pressure where possible.
• Prevent hidden scope change.
• Avoid identity-binding low-evidence pressure.
• Test dependency and asymmetry.
• Provide repair and rollback.
• Re-consent when scope changes.
• Treat refusal as structurally valid.
• Do not enforce failed consent.

Avoid:

• treating click-through as consent;
• treating silence as consent;
• treating compliance as consent;
• treating continued use as consent when exit is costly;
• treating contract signature as consent under survival pressure;
• treating opt-out as valid when buried or punitive;
• treating coercive dependency as agreement;
• treating identity pressure as free choice;
• treating hidden scope expansion as already consented;
• treating consent as permanent and non-revocable.

10. Cross-Scale Expressions

11. Examples

Example A — AI Memory Consent

Scenario:

A user clicks yes to memory, but the scope of memory, retrieval, sharing, deletion, and future influence is unclear or not auditable.

Law expression:

click signal + unclear scope / weak Au ⇒ consent validity risk

Interpretation:

Memory consent requires scope, auditability, revocation, rollback, and repair.

Example B — Platform Terms

Scenario:

A platform says users consented because they accepted terms, but refusal means losing essential access, work, identity, data, or community.

Law expression:

formal agreement + exit penalty / coercive dependency ⇒ BΣ failure

Interpretation:

The state-space may make consent structurally invalid.

Example C — Economic Contract

Scenario:

A worker signs a contract under survival pressure, with hidden terms, high exit penalties, and unequal bargaining power.

Law expression:

formal consent + survival coercion + asymmetric constraint pressure ⇒ contract inversion risk

Interpretation:

A signature does not prove coherent consent.

Example D — Medical Consent

Scenario:

A patient agrees to a procedure during urgency, fear, low explanation, no alternative path, and unclear repair options.

Law expression:

agreement under urgency + low Au ⇒ consent validity weakened

Interpretation:

Urgency may be unavoidable, but the consent state must be treated as constrained and repaired afterward where possible.

Example E — Institutional Waiver

Scenario:

A person signs a waiver to access a needed service, but the waiver removes appeal, obscures scope, and shifts burden to the harmed node.

Law expression:

waiver + exit penalty + audit suppression ⇒ consent collapse

Interpretation:

The waiver may be an artifact of coercive boundary state.

Example F — Forced Dialogue / Reintegration

Scenario:

A harmed person is asked to participate in dialogue, forgiveness, mediation, or reintegration before repair, safety, and boundary integrity are restored.

Law expression:

forced reintegration + damaged BΣ ⇒ invalid consent

Interpretation:

Restoration cannot require coerced boundary crossing.

12. Relationship to Nearby Laws

Aliases folded into this law:

• Consent Structurality Law
• Consent Is a Boundary State Law
• Checkbox Consent Failure Law
• Structural Consent Law
• Consent Validity Boundary Law

Deduplication note:

This law should remain the root consent-as-boundary-state law. LAW-046 should handle contract validity generally, and LAW-147 should preserve the economy-specific expression of contract state-space under survival coercion.

13. Operator Mapping

Coherent operator sequence:

Γ(consent artifact) → Σ(scope) → Λ(compatibility) → Au(terms / consequences) → K(exit / refusal) → Π(valid constraints) → Ψ(feedback) → ℛ(repair / revocation) → Τ(validate)

Inverted operator sequence:

checkbox / signature → Γ(valid consent assumed) → Π(enforcement) → exit blocked / scope hidden → BΣ↓ → H↑ → Ξ / ι↑

14. Machine-Readable Summary

id: "LAW-042"
name: "Consent Structurality Law"
type: "law"
status: "draft"
family:
  - "Signal and Classification Laws"
  - "Justice, Governance, and Legitimacy"
summary: "Consent is a boundary state, not a checkbox."
canonical_statement: "Consent is a boundary state, not a checkbox."
canonical_form: "formal consent signal ≠ valid consent state"
failure_form: "checkbox / signature / compliance + invalid boundary state ⇒ consent collapse"
invalidity_conditions:
  - "urgency"
  - "audit suppression"
  - "exit penalties"
  - "identity-binding low evidence"
  - "coercive dependency"
  - "asymmetric constraint pressure"
  - "hidden scope change"
  - "survival coercion"
variables:
  primary:
    - "BΣ"
    - "K"
    - "Au"
    - "Σ"
    - "Λ"
    - "⊗"
    - "Π"
  secondary:
    - "O"
    - "H"
    - "ε"
    - "ι"
    - "R"
    - "µᵢ"
    - "Φ"
    - "Γ"
    - "Θ"
    - "Ψ"
diagnostics:
  - "Consent Validity"
  - "Boundary Integrity"
  - "Exit Cost"
  - "Scope Clarity"
  - "Effective Auditability"
  - "Constraint Pressure"
  - "Coercion Risk"
  - "Dependency Pressure"
  - "Identity-Binding Risk"
  - "Hidden Scope Change"
  - "Slack / Sovereignty"
  - "Repair Path Availability"
failure_modes:
  - "Consent Collapse"
  - "Checkbox Consent"
  - "Boundary Violation"
  - "Coercive Dependency"
  - "Survival Coercion"
  - "Exit Penalty Capture"
  - "Hidden Scope Change"
  - "Audit Suppression"
  - "Identity-Binding Coercion"
  - "Invalid Coupling"
  - "Contract Inversion"
  - "Hidden Debt Accumulation"
restoration_arcs:
  - "Boundary Reconstitution"
  - "Auditability Restoration"
  - "Controlled Decoupling"
  - "Origin-Layer Repair"
  - "Restoration Capacity Rebuild"
  - "Temporal Validation"
  - "Recurrence Reduction"
  - "Basin Supersession"
related_laws:
  - "LAW-006"
  - "LAW-013"
  - "LAW-015"
  - "LAW-017"
  - "LAW-030"
  - "LAW-031"
  - "LAW-039"
  - "LAW-040"
  - "LAW-041"
  - "LAW-043"
  - "LAW-044"
  - "LAW-046"
  - "LAW-047"
  - "LAW-060"
  - "LAW-068"
  - "LAW-070"
  - "LAW-088"
  - "LAW-102"
  - "LAW-108"
  - "LAW-109"
  - "LAW-128"
  - "LAW-147"
related_invariants:
  - "INV-001"
  - "INV-078"
operator_sequence:
  coherent:
    - "Γ consent artifact"
    - "Σ scope"
    - "Λ compatibility"
    - "Au terms / consequences"
    - "K exit / refusal"
    - "Π valid constraints"
    - "Ψ feedback"
    - "ℛ repair / revocation"
    - "Τ validate"
  inverted:
    - "checkbox / signature"
    - "Γ valid consent assumed"
    - "Π enforcement"
    - "exit blocked / scope hidden"
    - "BΣ↓"
    - "H↑"
    - "Ξ / ι↑"
aliases:
  - "Consent Structurality Law"
  - "Consent Is a Boundary State Law"
  - "Checkbox Consent Failure Law"
  - "Structural Consent Law"
  - "Consent Validity Boundary Law"
deduplication_note: "Root consent-as-boundary-state law. LAW-046 handles contract validity generally, and LAW-147 preserves the economy-specific expression of contract state-space under survival coercion."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-042 — Consent Structurality Law

Consent is a boundary state, not a checkbox.

Plain meaning:

Consent is not valid just because a person clicked, signed, complied, answered, stayed, or failed to object. Consent is valid only when the surrounding structure preserves real boundary choice.

Canonical form:

formal consent signal ≠ valid consent state

Invalidity conditions:

Urgency, audit suppression, exit penalties, identity-binding low evidence, coercive dependency, asymmetric constraint pressure, hidden scope change, survival coercion.

Failure form:

checkbox / signature / compliance + invalid boundary state ⇒ consent collapse

Primary variables:

BΣ, K, Au, Σ, Λ, ⊗, Π, O, H, ι, R, µᵢ, Γ, Θ, Ψ

Diagnostic signature:

A formal consent artifact exists while scope clarity, auditability, exit, refusal capacity, boundary integrity, non-coercive pressure, and repair path are compromised.

Failure risk:

Consent collapse, checkbox consent, boundary violation, coercive dependency, survival coercion, exit penalty capture, hidden scope change, audit suppression, invalid coupling, contract inversion.

Restoration priority:

Audit the boundary state, suspend invalid enforcement, restore scope clarity, auditability, exit, refusal capacity, repair and rollback, then re-consent only if structural conditions become valid.