0. Registry Classification

1. Purpose

1.1 What This Arc Repairs

Consent Re-Formation repairs conditions where consent has become stale, coerced, unclear, hidden, non-revocable, scope-invalid, structurally pressured, or no longer aligned with the actual coupling, permission, role, access, contract, memory, tool, or participation state.

It applies when agreement-like participation exists but the underlying consent geometry has degraded.

This arc repairs invalid consent by:

• reducing urgency and coercive pressure;
• clarifying scope and terms;
• restoring auditability around consent history;
• restoring exit or revocation;
• identifying asymmetry and dependency;
• repairing boundary state;
• retesting compatibility;
• renewing consent only after choice-space is real;
• blocking recoupling or enforcement when consent remains invalid.

Consent Re-Formation is the canonical arc for restoring consent as a living boundary condition rather than a one-time artifact.

1.2 Core Restoration Function

This arc restores consent validity by reducing coercive pressure, clarifying scope, restoring exit, increasing auditability, mitigating asymmetry, and renewing authorization only when participation is revocable, informed, bounded, and compatible.

Consent Re-Formation prevents participation, access, agreement, or cooperation from being misread as valid consent.

2. Use Conditions

2.1 When to Apply

Use this arc when:

• consent is stale, outdated, or no longer matched to present conditions;
• scope has changed since consent was given;
• participation continues because exit is costly, unclear, punished, or unavailable;
• agreement was obtained under urgency, dependency, asymmetry, fear, exhaustion, or survival pressure;
• permissions, memory, access, role, data, tool use, representation, or contract terms have drifted;
• consent is hidden inside a broad policy, interface, default setting, social pressure, or institutional procedure;
• revocation is technically allowed but practically blocked;
• the affected node cannot meaningfully understand, audit, or contest the consent state;
• a system is treating compliance, silence, use, continued participation, or lack of objection as consent;
• renewed coupling, role restoration, enforcement, or contract continuation depends on consent validity.

Examples:

• an AI system retains memory or tool access under an old or unclear permission state;
• a platform treats continued use as consent after material scope changes;
• an institution treats participation in a process as agreement to its expanded scope;
• a contract continues under dependency or survival-edge conditions;
• a governance system asks for testimony, mediation, or reintegration before affected-node boundaries are restored;
• a meaning or relationship system treats loyalty, forgiveness, silence, or harmony as consent.

2.2 When Not to Apply

Do not apply this arc when:

• active harm is still cascading and emergency stabilization must occur first;
• consent is clearly invalid and the correct next step is immediate decoupling or release;
• scope cannot be disclosed;
• exit cannot be restored;
• auditability cannot be increased;
• asymmetry cannot be mitigated enough for meaningful choice;
• the system is using “renewed consent” to erase prior harm;
• the arc would pressure affected nodes to re-authorize an unsafe coupling;
• the system needs material repair before any consent request is admissible.

Consent Re-Formation must not become consent theater.

2.3 Required Preconditions

Before this arc begins, the following must be true:

If required preconditions fail:

Arc cannot validly begin.

The system must return to boundary reconstitution, controlled decoupling, contract release, audit surface expansion, or safe decoupling.

3. Failure / Damage Signature

3.1 Pre-State Across S

3.2 Primary Failure Links

3.3 Origin-Layer Localization

Canon rule:

Consent is invalid when scope, revocability, auditability, and exit are absent or structurally compromised.

4. Restoration Objective

4.1 Canonical Objective

Restore consent validity by clarifying scope, exposing consent history, reducing coercive pressure, restoring exit, mitigating asymmetry, and renewing authorization only if compatibility is positive and participation remains revocable.

Formal objective:

BΣ ↑
Au_consent ↑
scope clarity ↑
exit viability ↑
coercive pressure ↓
Perm stable
Λ tested
H_consent ↓
recurrence ↓

Expanded objective:

Convert apparent agreement into valid consent or route the system toward decoupling, contract release, boundary repair, or successor topology when consent cannot be restored.

4.2 Non-Goals

This arc does not aim to:

• obtain agreement at all costs;
• retroactively legitimize invalid consent;
• make continued participation count as consent;
• erase prior harm through renewed agreement;
• restore old terms by default;
• use disclosure to shift responsibility;
• pressure affected nodes to re-authorize unsafe coupling;
• treat signatures, clicks, silence, attendance, loyalty, or compliance as sufficient proof;
• improve retention or cooperation while boundaries remain invalid.

5. Operator Sequence

5.1 Minimal Operator Scaffold

Π consent boundary hold → Σ invariant lock → Au consent trace → Θ urgency/asymmetry reduction → scope disclosure → exit restoration → Λ compatibility test → ℛ consent repair → Τ revocation/recurrence validation

Universal grammar alignment:

Σ + Θ → Π → Au↑ → ℛ(U2 consent layer) → Λ → ⊗_Λ only if valid → Τ → Temporal Proof

Consent Re-Formation may route into Contract Revalidation, Controlled Decoupling, Safe Decoupling, Compatibility Recoupling, Boundary Reconstitution, or AI Boundary Restoration.

5.2 Operator Step Table

5.3 Sequence Notes

This arc is revocability-gated, scope-gated, and asymmetry-gated.

Consent cannot be repaired by asking for renewed consent while the same coercive conditions remain active.

The sequence must distinguish:

valid consent
stale consent
coerced consent
manufactured consent
implied participation
procedural consent
invalid consent

The following steps cannot be skipped:

consent-dependent action hold
scope disclosure
consent-history audit
pressure reduction
exit / revocation restoration
compatibility testing
temporal validation

If exit remains symbolic, consent remains invalid.

If participation is treated as consent while dependency remains active, the arc has failed.

6. Restoration Phases

Phase 0 — Identify Consent Object

Purpose: Name what consent is allegedly authorizing.

Actions:

• identify the specific permission, access, role, memory, tool, contract, process, data use, participation, coupling, or representation;
• identify who is authorizing and who is acting;
• identify whether consent is current, stale, implied, inherited, hidden, or absent;
• identify whether action depends on consent validity.

Validation:

consent object named
acting authority identified
consent dependency visible

Phase 1 — Pause Consent-Dependent Expansion

Purpose: Prevent continued action under invalid or unclear consent.

Actions:

• pause new access or expanded scope;
• suspend unclear permissions;
• block recoupling or enforcement;
• prevent new data, labor, testimony, participation, or role demand;
• preserve current state for audit.

Validation:

new consent-dependent expansion stopped
BΣ stops degrading
state remains auditable

Phase 2 — Reconstruct Consent History

Purpose: Make the consent state traceable.

Actions:

• identify original scope;
• map changes in terms, context, permissions, or power;
• identify default settings or hidden clauses;
• identify what was disclosed and when;
• identify whether revocation was available;
• identify pressure, dependency, or asymmetry at the time of agreement.

Validation:

Au_consent ↑
scope-change history visible
validity gaps named

Phase 3 — Clarify Present Scope

Purpose: Make the current request or authorization legible.

Actions:

• state what is being requested now;
• state what access, data, role, authority, or coupling is included;
• state what is excluded;
• state duration and review conditions;
• state risks and alternatives;
• separate essential from optional terms.

Validation:

present scope explicit
Perm stable and bounded
hidden terms removed

Phase 4 — Reduce Coercive Pressure

Purpose: Restore choice-space before any renewal.

Actions:

• reduce urgency;
• reduce threat of penalty;
• reduce dependency pressure;
• reduce survival-edge pressure where applicable;
• create time to decide;
• provide support for refusal or exit.

Validation:

coercive pressure ↓
K / σ ↑
choice no longer forced by immediate constraint

Phase 5 — Restore Exit / Revocation

Purpose: Make consent revocable and refusal meaningful.

Actions:

• define how to refuse;
• define how to revoke;
• define rollback or deletion where applicable;
• define consequence boundaries;
• define post-exit support where needed;
• remove punitive exit pathways where possible.

Validation:

exit viable
revocation path clear
refusal does not collapse protected status

Phase 6 — Renew, Revise, Release, or Decouple

Purpose: Determine whether consent can be validly re-formed.

Actions:

• renew only if scope is understood, exit is real, asymmetry is mitigated, and compatibility is positive;
• revise if scope or terms must change;
• release if consent cannot be restored;
• decouple if coupling remains invalid;
• route to contract revalidation if formal agreement governs the relation.

Validation:

valid consent renewed, revised, or refused
Λ tested
invalid coupling not preserved

Phase 7 — Temporal Proof

Purpose: Confirm consent remains valid over time.

Actions:

• monitor whether revocation remains real;
• check whether scope drifts;
• check whether dependency pressure returns;
• check whether participation becomes coerced again;
• check whether permissions remain inspectable.

Validation:

BΣ(t+n) ≥ BΣ(t)
exit remains viable
Perm remains stable
recurrence ↓

7. Gates

7.1 Required Gates

7.2 Gate Failure Rule

If any required gate fails:

∅ — Consent Re-Formation cannot validly proceed in that form.

The system must either:

• pause consent-dependent action;
• clarify scope;
• increase auditability;
• reduce coercive pressure;
• restore exit;
• route to controlled decoupling;
• route to contract release;
• block recoupling or enforcement.

8. Diagnostics

8.1 Required Diagnostic Trends

8.2 Arc-Specific Diagnostic Thresholds

Suggested thresholds:

Au_consent ↑
scope clarity ↑
Perm stable
exit viable
coercive pressure ↓
Λ tested before renewed coupling
BΣ(t+n) ≥ BΣ(t)
recurrence ↓ across U7

Consent Re-Formation is not complete if:

exit remains symbolic
scope remains hidden or broad
revocation is punitive
participation is treated as consent
permissions remain untraceable
asymmetry remains unmitigated
recoupling occurs before Λ > 0

9. Anti-Patterns / False Restorations

9.1 Common False Versions

This arc is being simulated, not executed, if:

• consent is requested before scope is disclosed;
• consent is requested while exit is blocked;
• refusal carries hidden penalty;
• revocation exists only in policy text;
• continued participation is treated as agreement;
• a checkbox, signature, attendance, silence, or platform use substitutes for consent;
• consent renewal is used to erase prior boundary damage;
• the system preserves broad access while narrowing language;
• “choice” exists only under dependency or survival pressure;
• the affected node must prove non-consent.

9.2 Named Anti-Pattern Links

10. Completion Criteria

10.1 Post-State Signature

10.2 Temporal Proof

Consent Re-Formation cannot be declared complete until scope, revocation, and exit remain valid over time.

Template:

Completion requires BΣ(t+n) ≥ BΣ(t),
Perm(t+n) stable and inspectable,
exit remaining viable,
and consent drift decreasing across U7.

Minimum temporal proof:

• revocation remains usable;
• scope does not silently expand;
• permissions remain traceable;
• participation remains non-coerced;
• exit does not become punitive;
• consent does not drift under renewed pressure.

10.3 Completion Statement

Canonical format:

This arc is complete only when consent is informed, bounded, traceable, revocable where applicable, non-coerced, compatible, and stable over time without scope drift, hidden dependency, or symbolic exit.

11. Cross-Links

11.1 Related Restoration Arcs

11.2 Related Failure Modes

11.3 Related Diagnostics

BΣ, Au, Perm, Λ, H, K, σ(t), R, ι, τ_m, recurrence, Φ/O divergence

11.4 Related Laws / Invariants

INV — Consent requires scope, revocability, and exit.
INV — Boundary integrity is required for valid coupling.
INV — Coherence cannot be inferred from compliance.
INV — Participation is not consent when exit is structurally blocked.
LAW — Forced coupling accumulates hidden debt.
LAW — Consent decays when scope changes faster than auditability.
LAW — Recoupling before compatibility recreates failure geometry.
LAW — Φ improvement is not O restoration.

12. Domain Notes

12.1 AI / Cognitive Infrastructure

Check:

• memory consent;
• tool consent;
• data retention;
• context reuse;
• API access;
• agent authority;
• default permissions;
• user appeal and deletion paths;
• whether interaction history is being treated as blanket authorization.

AI consent re-formation requires explicit scope, traceable memory/tool permissions, revocation paths, and no hidden expansion through product defaults or model behavior.

12.2 Justice / Governance / Legitimacy

Check:

• whether participation is required to receive protection;
• whether reporting, testimony, mediation, or reintegration is being coerced;
• whether process consent is bundled with unsafe exposure;
• whether public legitimacy depends on affected-node participation;
• whether refusal carries retaliation, exclusion, disbelief, or loss of support.

JGL consent repair must preserve affected-node sovereignty before truth, repair, or reintegration demands are made.

12.3 Biology / Medicine

Conceptual systems mapping only.

Consent Re-Formation in biological or medical-adjacent systems means preserving agency, scope, pacing, revocability, and informed participation in any intervention, interpretation, monitoring, or data use.

Not diagnosis.

Not treatment.

Not medical advice.

12.4 Economy

Check:

• contract terms;
• hidden fees;
• exit penalties;
• survival-edge pressure;
• debt dependency;
• bargaining asymmetry;
• platform lock-in;
• whether “choice” is structurally coerced by scarcity.

Economic consent repair requires real exit, understandable terms, non-coercive participation, and traceable scope.

12.5 CMS / Meaning / Archetypes

Check:

• spiritualized agreement;
• identity pressure;
• loyalty language;
• taboo against refusal;
• consent hidden inside devotion, belonging, mission, healing, forgiveness, or archetypal role;
• symbolic meaning used to override exit.

Meaning systems require consent that remains alive, bounded, and revocable without collapsing symbolic depth.

13. Machine-Readable Metadata

id: "RA-018"
title: "Consent Re-Formation"
aliases:
  - "Consent Repair"
family_primary: "Boundary"
families_secondary:
  - "Core"
  - "Contract"
  - "Coupling"
  - "Justice / Governance / Legitimacy"
  - "AI Governance"
  - "Security"
  - "Economy"
  - "CMS"
treatment: "Specialized Grammar"
status: "Canon-Ready"
scope:
  - "Local"
  - "Relational"
  - "Institutional"
  - "AI"
  - "Economic"
  - "Civilizational"
  - "Cross-Domain"
u_layers:
  failure_origin:
    - "usually U2 boundary / consent / permission / interface"
    - "may originate in U1 dependency pressure"
    - "may originate in U3 control architecture"
  symptom_visible:
    - "U4 agreement narrative"
    - "legal language"
    - "policy text"
    - "harmony claim"
    - "Φ participation / retention"
  repair_required:
    - "same or lower than layer where consent was invalidated"
  validation:
    - "U5"
    - "U6"
    - "U7"
operators:
  scaffold: "Π consent boundary hold → Σ invariant lock → Au consent trace → Θ urgency/asymmetry reduction → scope disclosure → exit restoration → Λ compatibility test → ℛ consent repair → Τ revocation/recurrence validation"
  sequence:
    - "Π"
    - "Σ"
    - "Au"
    - "Θ"
    - "scope disclosure"
    - "exit restoration"
    - "Λ"
    - "ℛ"
    - "Τ"
state_variables:
  primary:
    - "BΣ"
    - "Au"
    - "Perm"
    - "Λ"
  secondary:
    - "H"
    - "K"
    - "R"
    - "ι"
    - "Φ"
diagnostics:
  - "σ(t)"
  - "τ_m"
  - "recurrence"
  - "Φ/O divergence"
gates_required:
  - "FI-Gate"
  - "HR-Gate"
  - "MS-Gate"
  - "Au-Actuation"
  - "BΣ-Gate"
  - "Λ-Gate"
  - "☷ᵢ"
linked_failure_modes:
  - "Consent Drift"
  - "Consent Theater"
  - "Manufactured Consent"
  - "Forced Coupling"
  - "Scope Creep"
  - "Permission Drift"
  - "Exit Denial"
  - "Coercive Dependency"
  - "Interface Capture"
  - "Contract Drift"
  - "Boundary Collapse"
  - "Restoration Bypass"
linked_restoration_arcs:
  - "RA-005"
  - "RA-010"
  - "RA-011"
  - "RA-019"
  - "RA-020"
  - "RA-021"
  - "RA-040"
  - "RA-045"
  - "RA-049"
  - "RA-057"
  - "RA-065"
anti_patterns:
  - "Consent Theater"
  - "Manufactured Consent"
  - "Checkbox Sovereignty"
  - "Revocation Theater"
  - "Participation-as-Consent"
  - "Scope Laundering"
  - "Renewal-as-Erasure"
completion_tests:
  - "Au_consent increases"
  - "scope clarity increases"
  - "Perm stable"
  - "exit viable"
  - "coercive pressure decreases"
  - "Λ tested before renewed coupling"
  - "BΣ(t+n) ≥ BΣ(t)"
  - "recurrence decreases across U7"
summary: "Consent Re-Formation restores valid consent after scope drift, coercion, dependency, hidden terms, stale agreement, unclear revocability, or exit failure has made authorization structurally invalid."

Final Calibration Rule

Consent Re-Formation answers six questions:

What hidden debt is being generated by invalid or drifted consent?
What boundary, scope, permission, revocation, or exit path must be repaired?
What auditability proves the consent state is traceable?
What coupling, enforcement, access, or participation must remain paused until consent is valid?
What trajectory becomes viable once consent is informed, bounded, revocable, and compatible?
How is consent validity proven over time without scope drift, coercion, or symbolic exit?