0. Registry Classification

1. Purpose

1.1 What This Arc Repairs

Reintegration Membrane repairs the conditions required before a node, role, relationship, institution, AI system, interface, process, or authority can safely re-enter a field after decoupling, accountability, suspension, harm, repair, exile, boundary rupture, contract failure, or trust loss.

It applies when reintegration is being considered, but direct return would risk boundary collapse, forced forgiveness, invalid recoupling, recurrence, accountability bypass, or affected-node burden transfer.

This arc repairs reintegration risk by:

• preserving the boundary between separation and return;
• testing whether repair has actually occurred;
• checking consent, trust viability, and compatibility;
• protecting affected nodes from forced contact or symbolic closure;
• defining scoped access, role, authority, and review conditions;
• preventing old coupling geometry from reactivating;
• requiring temporal proof before full re-entry;
• allowing partial, staged, conditional, or denied reintegration depending on field response.

Reintegration Membrane is the canonical arc for safe, bounded, repair-conditioned return after rupture.

1.2 Core Restoration Function

This arc restores safe re-entry by creating a membrane between exclusion and full return, allowing only repair-validated, consent-valid, compatibility-tested, boundary-safe, temporally proven reintegration to proceed.

Reintegration Membrane prevents the system from mistaking apology, time passage, symbolic repair, or desire for harmony as sufficient proof of safe return.

2. Use Conditions

2.1 When to Apply

Use this arc when:

• a harmed relationship, role, system, process, or authority is being considered for re-entry;
• someone or something was decoupled, suspended, removed, constrained, or isolated due to harm, incompatibility, breach, extraction, or drift;
• affected nodes are being asked to accept contact, trust, access, or role restoration;
• repair has occurred but full recoupling may still be unsafe;
• accountability obligations may be complete enough to test reintegration but not enough to assume it;
• an institution wants to restore a role, office, access, credential, platform, model, interface, or process after failure;
• an AI agent, memory, tool, classifier, evaluator, or product behavior is being restored after boundary or safety repair;
• symbolic reconciliation pressure is rising before compatibility is proven;
• reintegration must occur in phases, with scoped authority and monitoring.

Examples:

• a person seeks return to a community after accountability work;
• an institution restores a suspended role after repair and monitoring conditions;
• an AI system re-enables a tool, memory, or automation after boundary restoration;
• a platform restores access after consent and contract repair;
• a governance process allows participation only through a boundary-safe role;
• a symbolic system considers reconciliation after harm but before full trust is viable.

2.2 When Not to Apply

Do not apply this arc when:

• active harm is still cascading and emergency stabilization must occur first;
• repair has not occurred;
• responsibility has not been mapped;
• affected-node boundaries remain unsafe;
• trust is being demanded rather than tested;
• reintegration is being used to avoid consequence, decoupling, or accountability;
• the correct move is continued safe decoupling, role retirement, or supersession;
• consent cannot be restored;
• compatibility is negative or untestable;
• affected nodes are being asked to carry reintegration labor.

Reintegration Membrane must not become reintegration 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 emergency stabilization, boundary reconstitution, responsibility gradient mapping, victim-centered restoration, safe decoupling, contract revalidation, or future-compatible accountability.

3. Failure / Damage Signature

3.1 Pre-State Across S

3.2 Primary Failure Links

3.3 Origin-Layer Localization

Canon rule:

Reintegration is valid only when boundary, consent, compatibility, accountability, and temporal proof pass before full return.

4. Restoration Objective

4.1 Canonical Objective

Restore safe reintegration by creating a conditional membrane that tests repair, consent, compatibility, boundary stability, role scope, and trust viability before allowing staged or full return.

Formal objective:

BΣ_membrane ↑
Λ tested
trust_viability tested
Au_reintegration ↑
repair_alignment ↑
H_reintegration ↓
scope clarity ↑
rollback viability ↑
recurrence ↓
Φ/O divergence ↓

Expanded objective:

Convert reintegration from symbolic return into a staged, auditable, boundary-safe, consent-valid, repair-conditioned process.

4.2 Non-Goals

This arc does not aim to:

• force reconciliation;
• restore old role by default;
• reward apology with access;
• make time passage count as repair;
• require affected nodes to validate return;
• use reintegration to erase harm;
• collapse all separation into exile;
• collapse all accountability into permanent exclusion;
• treat forgiveness as compatibility proof;
• prioritize institutional harmony over boundary integrity.

5. Operator Sequence

5.1 Minimal Operator Scaffold

Π reintegration membrane boundary → Σ repair-conditioned return invariant → Au repair / role / access trace → FI affected-field correction → Λ compatibility and trust test → Θ harmony / urgency damping → ℛ staged access and rollback repair → Τ recurrence / boundary validation

Universal grammar alignment:

Σ + Θ → Π → Au↑ → FI↑ → Λ → ℛ(staged membrane) → Τ → Temporal Proof

Reintegration Membrane may route into Compatibility Recoupling, Future-Compatible Accountability, Legitimacy Re-Anchoring, Identity Re-Formation, Contract Revalidation, or continued Safe Decoupling.

5.2 Operator Step Table

5.3 Sequence Notes

This arc is membrane-gated, consent-gated, and compatibility-gated.

Reintegration Membrane does not assume that re-entry is owed. It creates the conditions under which re-entry can be tested without violating affected-node boundaries or bypassing repair.

The sequence must distinguish:

reintegration
recoupling
reconciliation
role restoration
access restoration
trust restoration
symbolic inclusion
forced return

The following steps cannot be skipped:

membrane boundary
repair evidence audit
affected-node boundary protection
compatibility and trust viability test
staged scope definition
rollback path
temporal proof

If return occurs before trust viability is tested, the arc has failed.

If the membrane becomes permanent exclusion without review, the arc has frozen.

6. Restoration Phases

Phase 0 — Identify Reintegration Candidate and Rupture History

Purpose: Name what is being considered for return and why separation occurred.

Actions:

• identify the node, role, access, authority, relationship, tool, interface, or process proposed for reintegration;
• identify prior rupture, harm, breach, incompatibility, or decoupling;
• identify who was affected;
• identify what repair was required;
• identify what full return would restore.

Validation:

reintegration candidate named
rupture history visible
affected field identified

Phase 1 — Establish Membrane Boundary

Purpose: Preserve separation while review occurs.

Actions:

• define what remains separated;
• define what limited contact or access is allowed, if any;
• define no-contact, no-access, or limited-access conditions;
• protect affected-node refusal;
• prevent symbolic or informal return;
• maintain rollback authority.

Validation:

BΣ_membrane ↑
full return paused
affected-node boundaries protected

Phase 2 — Audit Repair and Accountability Evidence

Purpose: Determine whether reintegration is even eligible for testing.

Actions:

• review repair obligations;
• review accountability completion;
• review responsibility mapping;
• review contract / consent repair;
• review boundary repair;
• review affected-node burden;
• identify unresolved hidden debt.

Validation:

Au_reintegration ↑
repair_alignment assessed
unresolved H named

Phase 3 — Test Consent and Trust Viability

Purpose: Ensure contact, participation, or role restoration does not require trust extraction.

Actions:

• check consent for contact or access;
• protect refusal;
• test trust viability without demanding trust;
• identify whether affected nodes can safely opt out;
• prevent apology, time, or institutional desire from counting as trust proof.

Validation:

trust_viability tested
consent remains valid
trust extraction ↓

Phase 4 — Test Compatibility and Role Fit

Purpose: Determine whether reintegration is compatible with current field conditions.

Actions:

• test Λ;
• assess role scope;
• assess access scope;
• assess boundary conditions;
• assess recurrence risk;
• assess capacity for monitoring and rollback;
• determine whether continued decoupling is safer.

Validation:

Λ tested
role_fit assessed
recoupling not assumed

Phase 5 — Define Staged Reintegration Conditions

Purpose: Convert eligibility into bounded process.

Actions:

• define stage gates;
• define access levels;
• define role limits;
• define monitoring;
• define review intervals;
• define affected-node protections;
• define rollback triggers;
• define completion criteria.

Validation:

staged conditions explicit
rollback viable
BΣ remains intact

Phase 6 — Activate Limited / Conditional Reintegration

Purpose: Test re-entry without full exposure.

Actions:

• allow limited access only within defined scope;
• monitor boundary effects;
• monitor affected-node burden;
• monitor repair compliance;
• monitor recurrence signals;
• pause or reverse if conditions fail.

Validation:

conditional access remains bounded
H_reintegration does not rise
field response remains admissible

Phase 7 — Temporal Proof

Purpose: Confirm reintegration is stable before expansion or closure.

Actions:

• monitor recurrence;
• monitor boundary stability;
• monitor trust viability;
• monitor hidden debt;
• monitor recapture risk;
• validate whether stage expansion, continued membrane, or renewed decoupling is appropriate.

Validation:

BΣ(t+n) ≥ BΣ(t)
H_reintegration(t+n) ≤ H_reintegration(t)
recurrence ↓
trust_viability stable or ↑

7. Gates

7.1 Required Gates

7.2 Gate Failure Rule

If any required gate fails:

∅ — Reintegration Membrane cannot validly proceed in that form.

The system must either:

• maintain separation;
• restore boundaries;
• complete repair obligations;
• reduce access scope;
• route to safe decoupling;
• route to future-compatible accountability;
• block reconciliation, role restoration, or legitimacy claims until membrane conditions pass.

8. Diagnostics

8.1 Required Diagnostic Trends

8.2 Arc-Specific Diagnostic Thresholds

Suggested thresholds:

BΣ_membrane ↑
Λ tested
trust_viability tested
Au_reintegration ↑
repair_alignment ↑
H_reintegration ↓ or non-increasing
scope clarity ↑
rollback viability ↑
recurrence ↓ across U7

Reintegration Membrane is not complete if:

affected nodes are pressured into contact
trust is demanded as proof of healing
role restoration occurs before repair validation
boundaries collapse under staged access
rollback is unavailable
old coupling returns through informal channels
harmony improves while H rises

9. Anti-Patterns / False Restorations

9.1 Common False Versions

This arc is being simulated, not executed, if:

• reintegration is framed as proof of restoration;
• apology or time passage becomes access entitlement;
• affected nodes must approve return for institutional comfort;
• role restoration occurs without repair evidence;
• no-contact boundaries are softened through informal channels;
• staged access lacks rollback;
• harmony pressure overrides refusal;
• monitoring exists but cannot change access;
• the membrane becomes symbolic while old coupling resumes;
• reintegration becomes public legitimacy theater.

9.2 Named Anti-Pattern Links

10. Completion Criteria

10.1 Post-State Signature

10.2 Temporal Proof

Reintegration Membrane cannot be declared complete until re-entry remains stable under delay, field response, boundary stress, and recurrence monitoring.

Template:

Completion requires BΣ(t+n) ≥ BΣ(t),
Λ remaining positive for continued coupling,
H_reintegration(t+n) ≤ H_reintegration(t),
trust_viability not decreasing,
and recurrence decreasing across U7.

Minimum temporal proof:

• boundaries remain intact;
• trust is earned, not demanded;
• staged access does not expand by default;
• rollback remains viable;
• affected-node burden does not increase;
• old failure geometry does not recur;
• reintegration remains repair-conditioned.

10.3 Completion Statement

Canonical format:

This arc is complete only when reintegration, if allowed, remains consent-valid, compatibility-positive, boundary-safe, repair-conditioned, auditable, reversible where needed, and temporally proven without trust extraction, forced contact, symbolic inclusion, or recurrence of the old harm geometry.

11. Cross-Links

11.1 Related Restoration Arcs

11.2 Related Failure Modes

11.3 Related Diagnostics

BΣ, BΣ_membrane, Λ, Au, Au_reintegration, H, H_reintegration, O, R, K, σ(t), µᵢ, trust_viability, repair_alignment, recurrence, recapture risk, Φ/O divergence, rollback viability

11.4 Related Laws / Invariants

INV — Reintegration requires boundary integrity, consent, and compatibility.
INV — Trust cannot be demanded as a reintegration condition.
INV — Repair precedes role restoration.
INV — Recoupling before compatibility recreates failure geometry.
LAW — Premature reintegration accumulates hidden debt.
LAW — Forced reconciliation preserves harm geometry.
LAW — Informal recapture bypasses membrane repair.
LAW — Φ improvement is not O restoration.

12. Domain Notes

12.1 AI / Cognitive Infrastructure

Check:

• tool re-enablement;
• memory reactivation;
• agent authority restoration;
• classifier redeployment;
• model behavior rollback;
• user trust after incident;
• access restoration after boundary failure;
• staged release and rollback capacity.

AI reintegration membrane requires reactivation of memory, tools, agent autonomy, classifiers, evaluators, or product features to be scoped, auditable, consent-valid, and reversible.

12.2 Justice / Governance / Legitimacy

Check:

• offender reintegration;
• role restoration;
• institutional return to authority;
• trust repair;
• contact conditions;
• affected-node refusal;
• public legitimacy pressure;
• monitoring and rollback.

JGL reintegration membrane prevents reconciliation or role restoration from outrunning affected-node protection and repair proof.

12.3 Biology / Medicine

Conceptual systems mapping only.

Reintegration Membrane in biological or medical-adjacent systems means staged reintroduction of load, exposure, activity, routine, or coupling only after boundary, timing, tolerance, and recurrence indicators support it.

Not diagnosis.

Not treatment.

Not medical advice.

12.4 Economy

Check:

• re-entry into market, platform, role, contract, or exchange;
• restored account access;
• renewed employment or partnership;
• trust after extraction;
• rollback and review conditions;
• whether re-entry repeats prior dependency.

Economic reintegration membrane requires phased access, exit preservation, burden monitoring, and non-extractive recoupling conditions.

12.5 CMS / Meaning / Archetypes

Check:

• reconciliation ritual;
• return to group;
• role restoration;
• sacred forgiveness;
• re-entry after taboo or harm;
• symbolic inclusion;
• archetypal role return.

Meaning systems require reintegration membranes when symbolic belonging or forgiveness might bypass boundary, accountability, or compatibility proof.

13. Machine-Readable Metadata

id: "RA-045"
title: "Reintegration Membrane"
aliases:
  - "Reintegration Gate"
family_primary: "Boundary"
families_secondary:
  - "Core"
  - "Coupling"
  - "Justice / Governance / Legitimacy"
  - "Consent"
  - "Accountability"
  - "Institutional Design"
  - "AI Governance"
  - "Security"
  - "CMS"
  - "Transition"
treatment: "Canon Parent Arc"
status: "Canon-Ready"
scope:
  - "Relational"
  - "Institutional"
  - "AI"
  - "Security"
  - "Economic"
  - "Symbolic"
  - "Civilizational"
  - "Cross-Domain"
u_layers:
  failure_origin:
    - "usually U2 boundary / consent / role access"
    - "often U3 governance / process / authority restoration"
    - "often U4 reconciliation / unity / legitimacy narrative"
  symptom_visible:
    - "U4 forgiveness / inclusion / closure / reintegration / apology / harmony language"
    - "Φ participation / role restoration / public unity"
  repair_required:
    - "same or lower than layer where reintegration would restore access, coupling, authority, or role"
  validation:
    - "U5"
    - "U6"
    - "U7"
operators:
  scaffold: "Π reintegration membrane boundary → Σ repair-conditioned return invariant → Au repair / role / access trace → FI affected-field correction → Λ compatibility and trust test → Θ harmony / urgency damping → ℛ staged access and rollback repair → Τ recurrence / boundary validation"
  sequence:
    - "Π"
    - "Σ"
    - "Au"
    - "FI"
    - "Λ"
    - "Θ"
    - "ℛ"
    - "Τ"
state_variables:
  primary:
    - "BΣ"
    - "Λ"
    - "Au"
    - "H"
    - "O"
  secondary:
    - "R"
    - "K"
    - "µᵢ"
    - "Φ"
diagnostics:
  - "BΣ_membrane"
  - "Au_reintegration"
  - "H_reintegration"
  - "trust_viability"
  - "repair_alignment"
  - "recurrence"
  - "recapture risk"
  - "Φ/O divergence"
  - "rollback viability"
gates_required:
  - "FI-Gate"
  - "HR-Gate"
  - "MS-Gate"
  - "Au-Actuation"
  - "BΣ-Gate"
  - "Λ-Gate"
  - "☷ᵢ"
linked_failure_modes:
  - "Premature Reintegration"
  - "Forced Reintegration"
  - "False Reconciliation"
  - "Recoupling Before Compatibility"
  - "Boundary Collapse"
  - "Trust Extraction"
  - "Accountability Bypass"
  - "Victim Burden Transfer"
  - "Role Restoration Without Repair"
  - "Recapture After Exit"
  - "Symbolic Reintegration"
  - "Restoration Bypass"
linked_restoration_arcs:
  - "RA-005"
  - "RA-010"
  - "RA-011"
  - "RA-018"
  - "RA-019"
  - "RA-020"
  - "RA-021"
  - "RA-024"
  - "RA-033"
  - "RA-040"
  - "RA-041"
  - "RA-044"
  - "RA-046"
anti_patterns:
  - "Reintegration Theater"
  - "Forced Reintegration"
  - "Apology-as-Access"
  - "Time-Passage Repair"
  - "Symbolic Inclusion"
  - "Rollback Theater"
  - "Informal Recapture"
completion_tests:
  - "BΣ_membrane increases"
  - "Λ tested"
  - "trust_viability tested"
  - "Au_reintegration increases"
  - "repair_alignment increases"
  - "H_reintegration decreases or remains non-increasing"
  - "scope clarity increases"
  - "rollback viability increases"
  - "recurrence decreases across U7"
summary: "Reintegration Membrane restores the boundary, trust, access, role, and compatibility conditions required before a previously decoupled, constrained, accountable, or repaired node can safely re-enter a system, role, relationship, institution, interface, or field."

Final Calibration Rule

Reintegration Membrane answers six questions:

What hidden debt would be regenerated by premature or forced reintegration?
What boundary, consent, role, access, trust, or rollback path must be restored before return?
What auditability proves repair, compatibility, and role conditions are traceable?
What apology, time passage, harmony signal, inclusion claim, role restoration, or public unity metric must remain provisional until temporal proof?
What trajectory becomes viable once reintegration is staged, bounded, repair-conditioned, and reversible where needed?
How is reintegration proven over time without trust extraction, symbolic inclusion, forced contact, informal recapture, or recurrence of the old harm geometry?