Reintegration is not automatic restoration of prior access. After harm, breach, failure, invalid coupling, exile, suspension, decoupling, or boundary damage, renewed participation must pass through a membrane. That membrane should define conditions, scope, limits, auditability, reversibility, and proof over time.

1. Formal Definition

The Reintegration Membrane Law states that recoupling after restoration must occur through a structured membrane rather than automatic reinstatement.

When a system has decoupled, restricted access, separated nodes, suspended trust, removed permissions, ended participation, broken contract, isolated a component, or interrupted a coupling regime, reintegration cannot be assumed simply because a repair action occurred.

Reintegration changes coupling geometry. It reintroduces access, influence, load, trust, permissions, visibility, dependency, demand, or shared field effects. If reintegration happens too quickly or without conditions, it can reactivate the same failure basin that required decoupling in the first place.

Therefore, reintegration must be:

conditional — based on explicit requirements;
graduated — reintroduced in stages;
auditable — visible enough to verify;
reversible — able to pause or roll back safely;
time-validated — tested under recurrence, load, and perturbation.

Reintegration is not a reward, apology acceptance, forgiveness requirement, or return to prior status. It is a coupling transition that must preserve coherence.

2. Canonical Form

Core form:

textScroll

reintegration ⇒ conditional + graduated + auditable + reversible + time-validated

Access-restoration warning form:

textScroll

repair action ≠ automatic restoration of prior access

Failure form:

textScroll

automatic recoupling after boundary damage ⇒ H↑ + recurrence↑ + O↓

Reintegration-valid form:

textScroll

BΣ stable ∧ Λ valid ∧ Au intact ∧ exit available ∧ recurrence↓ over Τ ⇒ reintegration admissible

Related variables:

textScroll

O, H, ε, ι, Au, R, R_eff, BΣ, K, σ, µᵢ, Φ, Λ, ⊗, Γ, Π, ℛ, Θ, Σ, Ψ, Τ, FI

Where:

TableScroll

Variable	Meaning in this law
`⊗`	Coupling intensity being reintroduced through reintegration
`BΣ`	Boundary integrity required before renewed access or coupling
`Λ`	Compatibility; must be revalidated before reintegration
`Au`	Auditability; reintegration must be inspectable and traceable
`Σ`	Scope, permissions, limits, access level, exit, and rollback conditions
`Τ`	Time validation period for proving reintegration holds
`ℛ`	Restoration action that may make reintegration possible but does not automatically authorize it
`R / R_eff`	Restoration capacity required to support and monitor reintegration
`H`	Hidden debt that increases when reintegration reactivates prior failure geometry
`ι / Ξ`	Inversion when forced or premature reintegration is called restoration
`O`	Coherence; should remain stable or improve during reintegration
`K / σ`	Slack / sovereignty required for voluntary, non-extractive recoupling
`FI`	Feedback integrity required to detect reintegration stress honestly
`recurrence`	Must remain decreasing during reintegration stages
`𝓓`	Ring-down should improve or remain stable after coupling is reintroduced
`µᵢ`	Meaning / agent integrity protected when reintegration conditions are truthful
`Φ`	Visible normalcy; not proof that reintegration is coherent
`Γ`	Classifies readiness, stage, failure, rollback, and validation status
`Π`	Controls may gate access, restrict scope, or enforce rollback during reintegration
`Θ`	Humility / uncertainty prevents premature full access restoration
`Ψ`	Field and affected-node feedback validates whether reintegration is safe

3. Core Mechanism

The law unfolds because reintegration reintroduces coupling into a system that has already demonstrated coupling risk.

Coherent reintegration pathway

textScroll

decoupling / restriction occurs
→ origin-layer and boundary repair begin
→ reintegration criteria are defined
→ access is reintroduced gradually
→ auditability and rollback remain active
→ recurrence and ring-down are monitored
→ reintegration expands only after temporal proof

Premature reintegration pathway

textScroll

decoupling / restriction occurs
→ visible repair action happens
→ prior access is restored automatically
→ coupling load returns too fast
→ boundary or recurrence pathway reactivates
→ H↑ and recurrence↑
→ trust / legitimacy / coherence decline

The core mechanism is:

textScroll

reintegration is a membrane transition, not a reset to prior access

Detailed mechanism:

A coupling regime is interrupted.

Access, trust, relationship, participation, permission, exposure, collaboration, or representation is limited or removed because of harm, breach, overload, failure, or incompatibility.

A repair action occurs.

The system may apologize, patch, compensate, complete a process, reduce symptoms, or satisfy one repair condition.

Pressure rises to restore prior access.

Normalcy, productivity, belonging, legitimacy, relationship, public optics, or operational continuity may push the system toward rapid recoupling.

If reintegration lacks a membrane, old coupling geometry returns.

The same access, dependency, load, influence, or recurrence pattern may reappear before the system can hold it.

Reintegration becomes reinjury.

Hidden debt rises, boundaries destabilize, recurrence returns, and the repaired node or field loses confidence in the restoration process.

Coherent reintegration requires staged proof.

Each stage must preserve boundary integrity, restore trust through evidence, reduce recurrence, remain reversible, and hold over time.

4. When This Law Applies

This law applies whenever a system attempts renewed coupling after decoupling, restriction, harm, breach, suspension, conflict, boundary failure, contract failure, exile, exclusion, quarantine, containment, account restriction, institutional discipline, biological intolerance, security compromise, or AI representation failure.

It is especially important when:

access was removed for a reason;
trust was damaged;
boundaries were violated;
harmed nodes are asked to reengage;
suspended nodes are reinstated;
a system wants to return to normal quickly;
a security boundary is restored after compromise;
an AI resumes acting on behalf of a user;
an employee, institution, platform, or agent is reinstated after failure;
a biological system reintroduces inputs after intolerance;
a community attempts reconciliation after rupture;
a contract resumes after consent or exit failure;
a governance body seeks restored legitimacy after harm.

The law applies strongly when:

textScroll

prior access is restored without conditions, stages, audit, exit, or time proof

or when:

textScroll

reintegration is treated as automatic evidence of restoration

Typical domains:

TableScroll

Domain	Reintegration Membrane Expression
AI systems	AI representation, personalization, automation, or memory access must be conditional, scoped, auditable, reversible, and time-tested.
Security	Restored trust should be staged through least privilege, monitoring, rollback, and recurrence validation.
Institutions	Reinstatement or renewed participation should not erase boundary, repair, consequence, or monitoring conditions.
Medicine / biology	Reintroduction of foods, exposures, exercise, stimulation, or interventions must be gradual and tolerance-tested.
Economy	Contractual recoupling requires repaired consent, exit, scope, and bargaining conditions.
Governance	Legitimacy reintegration requires conditional trust, participation safety, repair proof, and recurrence monitoring.
Culture	Reconciliation should be graduated and reversible, not demanded as an immediate return to closeness.
Restoration	Reintegration is a controlled membrane, not automatic restoration of prior coupling.

5. When This Law Does Not Apply

This law should not be used to permanently block reintegration when repair has become coherent.

The law does not say that trust, access, participation, or connection can never return. It says return should occur through conditions that protect coherence.

Reintegration can be appropriate when:

boundary repair has occurred;
consent is structurally valid;
scope is clear;
exit and rollback are available;
auditability remains intact;
recurrence has decreased;
restoration capacity is sufficient;
affected-node burden is reduced;
time validation supports expanded coupling.

False-positive cases:

TableScroll

Case	Why it is not a violation
Access is restored gradually under monitoring	Reintegration membrane is functioning
A node is reinstated with bounded permissions and review	Coupling is conditional, not automatic
A biological input is reintroduced slowly with tolerance tracking	Graduated recoupling supports coherence
A relationship resumes with clear boundaries and exit	Recoupling is consented and reversible
AI automation resumes with user audit, scope, and rollback	Representation membrane is restored

Important distinction:

Reintegration is possible. Automatic restoration of prior access is not the same as coherent reintegration.

6. Diagnostic Signature

Canonical diagnostic:

textScroll

reintegration = conditional + graduated + auditable + reversible + time-validated

Warning signature:

textScroll

prior access restored
conditions absent
audit weak
rollback absent
recurrence untested
BΣ still fragile
⇒ reintegration failure risk↑

Common indicators:

TableScroll

Diagnostic	Expected movement	Interpretation
`BΣ`	stable / ↑	Boundaries must hold before and during reintegration
`Λ`	validated	Compatibility must be rechecked after failure
`⊗`	gradual ↑	Coupling should increase in stages
`Au`	intact / ↑	Reintegration must remain auditable
`FI`	intact	Feedback must detect stress, recurrence, or boundary failure
`R_eff`	sufficient	Capacity must support monitoring and rollback
`H`	↓	Hidden debt should not increase during reintegration
`recurrence`	↓ / stable-low	Old failure pattern should not return
`𝓓`	↑ / stable	Damping should improve or remain stable
`K / σ`	stable / ↑	Slack and sovereignty should not be consumed by reintegration
`O`	stable / ↑	Coherence should hold as coupling increases
`Φ`	not sufficient	Visible normalcy does not prove reintegration
`ι / Ξ`	↓	Inversion decreases when recoupling is conditional and truthful

Additional diagnostics:

TableScroll

Diagnostic	Use
Reintegration Readiness	Tests whether conditions for recoupling are present
Boundary Integrity	Verifies the membrane can hold renewed coupling
Safe Coupling	Assesses whether coupling intensity is admissible
Consent Validity	Confirms participation is voluntary, informed, scoped, and reversible
Coupling Load	Tracks burden added by renewed access
Reversibility	Confirms rollback is possible without new harm
Effective Auditability	Keeps reintegration inspectable
Recurrence	Detects return of old coupling failure
Ring-Down	Tests recovery after reintegration perturbations
Temporal Proof	Validates reintegration over time

7. Failure Pattern

If ignored, this law produces premature recoupling, reinjury, and legitimacy loss.

General failure pathway:

textScroll

decoupling occurs
→ repair action occurs
→ prior access restored automatically
→ coupling load returns
→ boundary stress rises
→ recurrence returns
→ H↑
→ trust / legitimacy / coherence decline

Common failure modes:

Automatic Reinstatement — prior access returns without membrane conditions.
Premature Reintegration — coupling resumes before repair is validated.
Forced Reintegration — participation is demanded before boundary, consent, or capacity conditions exist.
Irreversible Recoupling — no safe rollback exists if recurrence returns.
Unauditable Reintegration — reintegration occurs without traceability or monitoring.
Boundary Reinjury — renewed coupling reopens the damaged membrane.
Consent Theater — formal agreement exists while real exit or scope is absent.
Reinjury Loop — reintegration repeatedly recreates harm.
Recurrence Persistence — the same pattern returns under renewed coupling.
Pseudo-Restoration — visible normalcy masks unresolved debt.
Legitimacy Debt — authority decays when reintegration fails.
Delayed Collapse — reintegration appears stable until load returns.

Compact failure signature:

textScroll

automatic recoupling + weak BΣ + no rollback ⇒ recurrence↑ + H↑

8. Restoration Implications

Restoration requires designing reintegration as a membrane.

The first restoration question is not:

textScroll

Can prior access be restored?

The first restoration question is:

textScroll

What membrane conditions make renewed coupling coherent, reversible, and time-validatable?

Restoration priorities:

Confirm boundary-first repair has occurred.
Define reintegration scope.
Define conditions for each stage.
Validate consent, exit, and rollback.
Restore auditability and feedback integrity.
Begin with limited coupling.
Monitor recurrence, ring-down, and hidden debt.
Expand only after time validation.
Pause or reverse if boundary stress returns.
Do not treat reintegration as closure until proof exists.

Relevant restoration arcs:

TableScroll

Restoration Arc	Why it applies
Reintegration Membrane	Directly governs conditional recoupling
Boundary Reconstitution	Reintegration requires repaired boundaries
Controlled Decoupling	Provides the prior state and rollback pathway
Consent Restoration	Ensures renewed coupling is voluntary and scoped
Graduated Recoupling	Reintroduces coupling in stages
Auditability Restoration	Keeps reintegration traceable
Hidden Debt Reduction	Tests whether reintegration creates or reduces debt
Restoration Capacity Rebuild	Supports monitoring, repair, and rollback
Temporal Validation	Confirms reintegration holds over time
Recurrence Reduction	Detects whether old failure patterns remain
Closure Stack Completion	Prevents reintegration from substituting for closure

Minimal restoration sequence:

textScroll

BΣ repair
→ define reintegration conditions
→ validate consent / scope / exit
→ limited reversible coupling
→ monitor H / recurrence / 𝓓 / O
→ expand only after Τ proof

Temporal validation requirement:

textScroll

BΣ stable or rising
Λ valid
⊗ increased gradually
Au intact
rollback available
exit available
consent valid
H↓ or stable-low
recurrence↓
𝓓↑ or stable
R_eff ≥ Load × Gain
O stable or rising

9. Design Rule

Do not restore prior access automatically after repair; route reintegration through a membrane.

Operational design requirements:

Treat reintegration as a separate phase from repair.
Require boundary stability before recoupling.
Define eligibility conditions.
Define scope and access level.
Define stage gates.
Preserve auditability.
Preserve affected-node feedback.
Preserve rollback and exit.
Increase coupling gradually.
Monitor recurrence at each stage.
Require time validation before expanding access.
Keep full reintegration conditional on sustained proof.

Avoid:

automatic reinstatement;
full access after one repair action;
reintegration without auditability;
reintegration without rollback;
forced dialogue;
forced forgiveness;
irreversible recoupling;
scope creep during repair;
assuming apology restores compatibility;
assuming punishment restores compatibility;
restoring AI agency without user audit and exit;
restoring security trust without least privilege and monitoring;
treating visible normalcy as reintegration proof.

10. Cross-Scale Expressions

TableScroll

Scale / Layer	Expression of the Law
U0 — Substrate	Physical, biological, infrastructural, or hardware reintegration must be gradual and load-tested.
U1 — Energy / capacity	Reintegration should not demand capacity before slack and restoration capacity return.
U2 — Boundary / interface	The primary layer: access, consent, permissions, scope, and exit define the membrane.
U3 — Process / execution	Reintegration workflows must include stage gates, monitoring, and rollback.
U4 — Classification / claim	Claims of reinstatement or restored trust must match actual membrane conditions.
U5 — Time / delay	Reintegration requires time validation before expansion.
U6 — Field effect	Affected-node and field outcomes reveal whether recoupling is safe.
U7 — Recurrence / memory	Reintegration must test whether old patterns remain encoded.
U8 — Environment / forcing	External pressure can force premature reintegration unless buffered by membrane design.

11. Examples

Example A — Institutional Reinstatement

Scenario:

A person, team, or leader is reinstated after a repair action, but prior access, influence, and authority return immediately without monitoring, conditions, affected-node feedback, or rollback.

Law expression:

textScroll

repair action + automatic prior access ⇒ reintegration failure risk↑

Interpretation:

Reinstatement is not restoration by itself. Renewed access should be conditional, graduated, auditable, reversible, and time-validated.

Example B — Security Trust Restoration

Scenario:

A compromised account is restored to full privileges immediately after a password reset.

Law expression:

textScroll

credential repair + full privilege restoration without membrane ⇒ recurrence risk↑

Interpretation:

Security reintegration should use least privilege, monitoring, session review, staged trust, and rollback until temporal proof exists.

Example C — AI Representation After Scope Failure

Scenario:

An AI system resumes autonomous action for a user after a scope or consent failure, without renewed authorization, traceability, rollback, or user-visible audit.

Law expression:

textScroll

AI representation restored without Au / scope / exit ⇒ inadmissible reintegration

Interpretation:

AI representation requires a reintegration membrane. Restored automation must be scoped, auditable, reversible, and consent-valid.

Example D — Biological Reintroduction

Scenario:

A biological system improves after a flare, then immediately reintroduces multiple high-load foods, exercises, stimuli, or interventions at once.

Law expression:

textScroll

BΣ / tolerance fragile + rapid reintroduction ⇒ recurrence↑

Interpretation:

Reintroduction should be graduated and time-tested. Full exposure before tolerance proof can reactivate the prior basin.

Example E — Economic Contract Recoupling

Scenario:

A contract relationship resumes after a dispute, but exit remains costly, terms remain opaque, and the weaker party lacks real alternatives.

Law expression:

textScroll

contract recoupling without consent / exit repair ⇒ consent theater

Interpretation:

Economic reintegration requires repaired boundaries, valid consent, clear scope, exit, and auditability.

Example F — Cultural Reconciliation

Scenario:

A community publicly reconciles after harm and immediately demands closeness, trust, participation, or shared identity from harmed nodes.

Law expression:

textScroll

symbolic repair + immediate closeness demand ⇒ forced reintegration risk↑

Interpretation:

Reconciliation requires a membrane. Participation and closeness should be voluntary, staged, reversible, and time-validated.

12. Relationship to Nearby Laws

TableScroll

Related Law	Relationship
LAW-006 — Time Validation Law	Reintegration must be validated over time
LAW-007 — Ring-Down Truth Law	Coherent reintegration should not worsen damping
LAW-008 — Recurrence Validation Law	Recurrence reveals failed reintegration
LAW-009 — U4 / U6 Truth Law	Claims of restored trust require field validation
LAW-010 — Hidden Debt Accumulation Law	Premature reintegration creates hidden debt
LAW-011 — Hidden Debt Return Law	Reintegration can reactivate unrepaired debt
LAW-013 — Auditability-Debt Law	Reintegration must remain auditable
LAW-030 — Slack Sovereignty Law	Voluntary reintegration requires slack and sovereignty
LAW-041 — Boundary Membrane Law	Reintegration is a membrane transition
LAW-042 — Consent Structurality Law	Reintegration requires structurally valid consent
LAW-043 — Safe Coupling Law	Reintegration is renewed coupling and must be safe
LAW-044 — Coupling Gradient Law	Reintegration should be graduated, not binary
LAW-045 — Force Debt Law	Forced reintegration creates force debt
LAW-046 — Contract Validity Law	Contractual reintegration requires valid terms, scope, and exit
LAW-047 — Controlled Decoupling Law	Reintegration relies on reversible decoupling pathways
LAW-050 — Control-Restoration Separation Law	Access restriction is not restoration unless reintegration repair follows
LAW-052 — Stability Proof Law	Reintegration must survive perturbation
LAW-061 — Restoration Sequencing Law	Reintegration occurs after earlier restoration dependencies
LAW-062 — Restoration Is Not the Inverse of Failure Law	Reintegration is not simply reversing decoupling
LAW-063 — Origin-Layer Repair Law	Reintegration requires origin-layer repair if failure began below access layer
LAW-064 — Restoration Debt Reduction Law	Reintegration should not increase hidden debt
LAW-065 — Pseudo-Restoration Law	Visible normalcy after reintegration can mask false repair
LAW-066 — Restoration Capacity Sufficiency Law	Reintegration load must not exceed restoration capacity
LAW-067 — Temporal Proof Law	Reintegration requires proof across time
LAW-068 — Boundary-First Restoration Law	Boundary repair comes before reintegration membrane
LAW-069 — Closure Stack Law	Reintegration is not closure unless closure stack is complete
LAW-071 — No Forced Forgiveness Law	Forgiveness cannot be required for reintegration
LAW-073 — Restoration Before Scaling Law	Scaling reintegration before proof amplifies debt
LAW-075 — Capacity Before Demand Law	Reintegration cannot demand capacity destroyed by harm
LAW-076 — Supersession Threshold Law	Some systems should not be reintegrated as-is
LAW-108 — Victim Pathway Capacity Law	Reintegration must not overburden harmed nodes
LAW-128 — AI Representation Law	AI representation requires continuous auditability, exit, and scope
LAW-147 — Economic Contract State-Space Law	Formal contract recoupling may remain invalid under coercive state-space
LAW-162 — Membrane Coupling Law	Reintegration changes coupling regime through a membrane
LAW-163 — Elastic Selectivity Law	Reintegration membranes require elastic selectivity

Aliases folded into this law:

Reintegration Membrane Law
Conditional Reintegration Law
Graduated Recoupling Law
Reversible Reintegration Law
Auditable Reintegration Law
No Automatic Reinstatement Law
Time-Validated Reintegration Law

Deduplication note:

This law should remain the root reintegration-membrane law. LAW-068 establishes boundary-first repair, LAW-070 governs the next stage of conditional recoupling, LAW-071 prevents forgiveness from being used as a reintegration condition, and LAW-073 prevents scaling before reintegration has been validated.

13. Operator Mapping

TableScroll

Operator	Role in this law
`Γ`	Classifies reintegration readiness, stage, failure, rollback, or validation status
`Π`	Gates access, enforces conditions, limits scope, and supports rollback
`Ξ`	Captures inversion when forced or premature reintegration is labeled restoration
`⊗`	Coupling intensity being gradually reintroduced
`ℛ`	Repair action that may enable but does not automatically authorize reintegration
`Τ`	Validates reintegration over time and recurrence cycles
`Θ`	Prevents premature full-access confidence
`Σ`	Defines scope, conditions, access, rollback, and exit
`Ψ`	Field and affected-node feedback reveals reintegration stress or validity
`Λ`	Compatibility must be revalidated before expanded coupling

Coherent operator sequence:

textScroll

Γ(readiness) → Θ(uncertainty) → Σ(conditions / scope / rollback / exit) → Π(stage gates) → ⊗ gradual↑ → Ψ(validate effects) → Τ(time proof) → Λ(expand if compatible)

Inverted operator sequence:

textScroll

repair action → Φ_normalcy pressure↑ → prior access restored → ⊗↑ too fast → BΣ stress↑ → recurrence↑ → H↑ → Ξ / ι↑ → pseudo-restoration

14. Machine-Readable Summary

yamlScroll

id: "LAW-070"
name: "Reintegration Membrane Law"
type: "law"
status: "draft"
family:
  - "Restoration Laws"
summary: "Reintegration after harm, failure, or decoupling must be conditional, graduated, auditable, reversible, and time-validated."
canonical_statement: "Reintegration must be conditional, graduated, auditable, reversible, and time-validated."
core_form: "reintegration ⇒ conditional + graduated + auditable + reversible + time-validated"
access_restoration_warning_form: "repair action ≠ automatic restoration of prior access"
failure_form: "automatic recoupling after boundary damage ⇒ H↑ + recurrence↑ + O↓"
reintegration_valid_form: "BΣ stable ∧ Λ valid ∧ Au intact ∧ exit available ∧ recurrence↓ over Τ ⇒ reintegration admissible"
variables:
  primary:
    - "⊗"
    - "BΣ"
    - "Λ"
    - "Au"
    - "Σ"
    - "Τ"
    - "ℛ"
    - "R"
    - "R_eff"
    - "H"
    - "O"
  secondary:
    - "ε"
    - "ι"
    - "Ξ"
    - "FI"
    - "K"
    - "σ"
    - "µᵢ"
    - "Φ"
    - "Γ"
    - "Π"
    - "Θ"
    - "Ψ"
diagnostics:
  - "Reintegration Readiness"
  - "Boundary Integrity"
  - "Safe Coupling"
  - "Consent Validity"
  - "Coupling Load"
  - "Reversibility"
  - "Effective Auditability"
  - "Recurrence"
  - "Ring-Down"
  - "Restoration Capacity"
  - "Hidden Debt"
  - "Temporal Proof"
  - "Coherence Trajectory"
failure_modes:
  - "Automatic Reinstatement"
  - "Premature Reintegration"
  - "Forced Reintegration"
  - "Irreversible Recoupling"
  - "Unauditable Reintegration"
  - "Boundary Reinjury"
  - "Consent Theater"
  - "Reinjury Loop"
  - "Recurrence Persistence"
  - "Pseudo-Restoration"
  - "Legitimacy Debt"
  - "Delayed Collapse"
restoration_arcs:
  - "Reintegration Membrane"
  - "Boundary Reconstitution"
  - "Controlled Decoupling"
  - "Consent Restoration"
  - "Graduated Recoupling"
  - "Auditability Restoration"
  - "Hidden Debt Reduction"
  - "Restoration Capacity Rebuild"
  - "Temporal Validation"
  - "Recurrence Reduction"
  - "Closure Stack Completion"
related_laws:
  - "LAW-006"
  - "LAW-007"
  - "LAW-008"
  - "LAW-009"
  - "LAW-010"
  - "LAW-011"
  - "LAW-013"
  - "LAW-030"
  - "LAW-041"
  - "LAW-042"
  - "LAW-043"
  - "LAW-044"
  - "LAW-045"
  - "LAW-046"
  - "LAW-047"
  - "LAW-050"
  - "LAW-052"
  - "LAW-061"
  - "LAW-062"
  - "LAW-063"
  - "LAW-064"
  - "LAW-065"
  - "LAW-066"
  - "LAW-067"
  - "LAW-068"
  - "LAW-069"
  - "LAW-071"
  - "LAW-073"
  - "LAW-075"
  - "LAW-076"
  - "LAW-108"
  - "LAW-128"
  - "LAW-147"
  - "LAW-162"
  - "LAW-163"
related_invariants:
  - "INV-001"
  - "INV-006"
  - "INV-078"
  - "INV-079"
operator_sequence:
  coherent:
    - "Γ readiness"
    - "Θ uncertainty"
    - "Σ conditions / scope / rollback / exit"
    - "Π stage gates"
    - "⊗ gradual↑"
    - "Ψ validate effects"
    - "Τ time proof"
    - "Λ expand if compatible"
  inverted:
    - "repair action"
    - "Φ_normalcy pressure↑"
    - "prior access restored"
    - "⊗↑ too fast"
    - "BΣ stress↑"
    - "recurrence↑"
    - "H↑"
    - "Ξ / ι↑"
    - "pseudo-restoration"
aliases:
  - "Reintegration Membrane Law"
  - "Conditional Reintegration Law"
  - "Graduated Recoupling Law"
  - "Reversible Reintegration Law"
  - "Auditable Reintegration Law"
  - "No Automatic Reinstatement Law"
  - "Time-Validated Reintegration Law"
deduplication_note: "Root reintegration-membrane law. LAW-068 establishes boundary-first repair, LAW-070 governs the next stage of conditional recoupling, LAW-071 prevents forgiveness from being used as a reintegration condition, and LAW-073 prevents scaling before reintegration has been validated."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-070 — Reintegration Membrane Law

Reintegration must be conditional, graduated, auditable, reversible, and time-validated.

Core form:

textScroll

reintegration ⇒ conditional + graduated + auditable + reversible + time-validated

Access-restoration warning form:

textScroll

repair action ≠ automatic restoration of prior access

Plain meaning:

Reintegration is not automatic restoration of prior access. After harm, breach, failure, invalid coupling, exile, suspension, decoupling, or boundary damage, renewed participation must pass through a membrane that defines conditions, scope, limits, auditability, reversibility, and proof over time.

Failure form:

textScroll

automatic recoupling after boundary damage ⇒ H↑ + recurrence↑ + O↓

Reintegration-valid form:

textScroll

BΣ stable ∧ Λ valid ∧ Au intact ∧ exit available ∧ recurrence↓ over Τ ⇒ reintegration admissible

Primary variables:

⊗, BΣ, Λ, Au, Σ, Τ, ℛ, R, R_eff, H, O, FI, K, σ, µᵢ, Γ, Π, Θ, Ψ

Diagnostic signature:

Prior access is restored after repair without clear conditions, staged coupling, auditability, rollback, exit, recurrence testing, or time validation while boundaries remain fragile.

Failure risk:

Automatic reinstatement, premature reintegration, forced reintegration, irreversible recoupling, unauditable reintegration, boundary reinjury, consent theater, reinjury loop, recurrence persistence, pseudo-restoration, legitimacy debt, delayed collapse.

Restoration priority:

Confirm boundary repair, define reintegration conditions, validate consent, scope, exit, and rollback, begin with limited coupling, monitor hidden debt, recurrence, ring-down, and coherence, then expand only after temporal proof.

LAW-069 — Closure Stack Law

Registry

LAW-071 — No Forced Forgiveness Law