0. Registry Classification

1. Purpose

1.1 What This Arc Repairs

Victim-Centered Restoration repairs systems where the harmed, injured, affected, exploited, misrepresented, coerced, or burdened node has been displaced from the center of the repair geometry.

It applies when a system attempts restoration by prioritizing institutional legitimacy, public harmony, offender reintegration, reconciliation, process closure, reputation recovery, or symbolic healing before the affected node’s boundary, truth, agency, consent, safety, and repair needs are protected.

This arc repairs victim-displacement by:

• centering the affected node’s boundary and agency;
• protecting the harmed node from additional burden;
• restoring truth and causal clarity around harm;
• assigning repair burden to responsible and capable nodes;
• preventing forced reconciliation, comfort labor, or symbolic closure;
• distinguishing repair from apology, empathy, explanation, mediation, or reintegration;
• preserving consent, refusal, exit, privacy, and appeal;
• validating that restoration reduces hidden debt and recurrence without requiring the harmed node to stabilize the system.

Victim-Centered Restoration is the canonical arc for ensuring repair geometry begins from the harmed node’s reality rather than the system’s need for closure.

1.2 Core Restoration Function

This arc restores legitimate repair by making the affected node’s boundary, agency, truth, consent, dignity, and material restoration the organizing center before reconciliation, reintegration, legitimacy recovery, or symbolic closure is attempted.

Victim-Centered Restoration prevents restoration from becoming a second extraction.

2. Use Conditions

2.1 When to Apply

Use this arc when:

• the harmed node is being asked to participate before safety, consent, or repair is established;
• an institution prioritizes legitimacy recovery before affected-node repair;
• apology, empathy, mediation, or reconciliation is offered before material restoration;
• the harmed node is expected to educate, forgive, explain, comfort, stabilize, or validate the responsible node or system;
• process completion is treated as repair;
• affected-node testimony is extracted without adequate boundary protection;
• responsibility is flattened into “both sides” framing;
• reintegration is proposed before trust viability is proven;
• an AI, platform, institution, or governance process harmed users and seeks closure through communication rather than repair;
• the system wants to be seen as restorative before the harmed node’s conditions have changed.

Examples:

• an institution asks harmed people to participate in a listening session while retaining the harmful policy;
• a platform apologizes while keeping hidden data, access, or consent problems unresolved;
• a restorative process asks for empathy before repair obligations are assigned;
• a governance system treats testimony collection as healing while affected-node burden rises;
• a security system frames users as partners in repair while exporting review burden to them;
• a symbolic community asks harmed members to forgive to restore group harmony.

2.2 When Not to Apply

Do not apply this arc when:

• active harm is still cascading and emergency stabilization must occur first;
• the affected node has not been identified or harm reality remains unclear;
• the system lacks the auditability needed to establish harm, responsibility, or repair path;
• victim-centered language is being used to avoid responsibility mapping or broader structural repair;
• centering one node would erase other affected nodes without review;
• the harmed node is being required to define the entire repair path alone;
• the correct immediate move is boundary reconstitution, safe decoupling, or emergency harm stabilization.

Victim-Centered Restoration must not become victim-symbol 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, truth clarification, audit surface expansion, boundary reconstitution, responsibility gradient mapping, or repair-first intake.

3. Failure / Damage Signature

3.1 Pre-State Across S

3.2 Primary Failure Links

3.3 Origin-Layer Localization

Canon rule:

Restoration is invalid when the harmed node is made to carry the labor of restoring the system that harmed them.

4. Restoration Objective

4.1 Canonical Objective

Restore repair legitimacy by centering the affected node’s boundary, agency, truth, and repair needs while routing responsibility and repair burden to the proper responsible and capable nodes.

Formal objective:

BΣ_victim ↑
victim_agency ↑
burden_transfer ↓
repair_alignment ↑
Au_harm ↑
H_victim ↓
R_repair-directed ↑
trust_viability tested
Φ/O divergence ↓
recurrence ↓

Expanded objective:

Rebuild restoration around the harmed node’s reality, not the system’s need for closure, legitimacy, forgiveness, or reintegration.

4.2 Non-Goals

This arc does not aim to:

• make the harmed node responsible for repair design;
• force testimony, forgiveness, reconciliation, or empathy;
• erase broader systemic responsibility;
• treat victim status as permanent identity;
• use harmed-node symbolism for legitimacy;
• replace material repair with apology or listening;
• make offender comfort a repair priority;
• flatten all perspectives into equal burden;
• restore institutional trust before repair;
• declare closure without affected-node boundary and repair validation.

5. Operator Sequence

5.1 Minimal Operator Scaffold

Π affected-node boundary protection → Σ victim-centered repair invariant → Au harm / burden trace → FI affected-node feedback integrity → Θ pressure / legitimacy-gain damping → ℛ repair obligation routing → Λ trust / contact viability test → Τ burden / recurrence validation

Universal grammar alignment:

Σ + Θ → Π → Au↑ → FI↑ → ℛ(affected-node repair) → Λ → Τ → Temporal Proof

Victim-Centered Restoration may route into Repair-First Intake, Responsibility Gradient Mapping, Equality-Conserving Accountability, Legitimacy Re-Anchoring, Future-Compatible Accountability, or Reintegration Membrane.

5.2 Operator Step Table

5.3 Sequence Notes

This arc is boundary-gated, agency-gated, and repair-gated.

Victim-Centered Restoration does not mean the affected node must manage the process. It means the process is organized so the affected node is not further used, exposed, pressured, or displaced.

The sequence must distinguish:

victim-centered repair
victim-managed repair
symbolic victim centering
legitimacy-first repair
reconciliation-first repair
repair-first accountability

The following steps cannot be skipped:

affected-node boundary protection
harm / burden trace
responsibility and repair routing
affected-node feedback integrity
pressure damping
trust viability test
temporal proof

If participation increases but burden transfer rises, the arc has failed.

If the harmed node is centered symbolically but not materially, the arc has inverted.

6. Restoration Phases

Phase 0 — Identify Affected Node and Harm

Purpose: Name who or what was harmed, burdened, misrepresented, coerced, exploited, or injured.

Actions:

• identify affected node / group;
• identify harm or burden;
• identify current exposure;
• identify current repair need;
• identify whether immediate safety, boundary, or consent repair is required.

Validation:

affected node named
harm or burden visible
repair need provisionally identified

Phase 1 — Protect Boundary, Consent, and Refusal

Purpose: Prevent the repair process from creating secondary harm.

Actions:

• protect privacy;
• protect testimony boundaries;
• protect refusal;
• protect exit;
• protect non-participation;
• define contact constraints;
• prevent forced mediation, apology receipt, reconciliation, or public participation.

Validation:

BΣ_victim ↑
participation remains consent-valid
refusal remains protected

Phase 2 — Trace Harm, Burden, and Responsibility

Purpose: Make the repair surface auditable.

Actions:

• trace what happened;
• trace who benefited;
• trace who had authority;
• trace who carried burden;
• trace what repair has been delayed;
• trace whether process itself added burden;
• route unresolved responsibility to Responsibility Gradient Mapping.

Validation:

Au_harm ↑
burden_transfer visible
responsibility path clearer

Phase 3 — Stop Burden Transfer

Purpose: Remove repair labor from the harmed node.

Actions:

• stop comfort labor demands;
• stop educational labor demands;
• stop proof repetition where already established;
• stop forced participation;
• stop forgiveness pressure;
• stop symbolic use of the harmed node for legitimacy;
• provide support without requiring exposure.

Validation:

burden_transfer ↓
victim_agency ↑
H_victim growth slows

Phase 4 — Route Repair to Responsible Nodes

Purpose: Convert repair into obligation and action.

Actions:

• assign material repair;
• assign procedural repair;
• assign technical repair;
• assign boundary repair;
• assign record correction;
• assign prevention work;
• assign monitoring and validation duties.

Validation:

repair_alignment ↑
R_repair-directed ↑
affected node no longer carries repair burden

Phase 5 — Restore Affected-Node Agency and Options

Purpose: Rebuild choice-space around the harmed node.

Actions:

• provide options without coercion;
• preserve no-contact or low-contact paths;
• restore access, appeal, portability, compensation, support, or representation where applicable;
• allow timing control where possible;
• define what information or repair proof the affected node can access.

Validation:

victim_agency ↑
K / σ ↑
repair becomes less coercive

Phase 6 — Test Trust, Contact, or Reintegration Viability

Purpose: Prevent premature closure or reconciliation.

Actions:

• test whether contact is safe;
• test whether trust can be considered;
• test whether apology can be received without burden;
• test whether reintegration membrane is admissible;
• test whether repair is sufficient before any relational or public closure.

Validation:

trust_viability tested
Λ assessed before contact or reintegration
closure not assumed

Phase 7 — Temporal Proof

Purpose: Confirm victim-centered repair holds over time.

Actions:

• monitor burden transfer;
• monitor recurrence;
• monitor trust viability;
• monitor repair completion;
• monitor affected-node boundary;
• monitor whether legitimacy or harmony pressures return.

Validation:

BΣ_victim(t+n) ≥ BΣ_victim(t)
burden_transfer ↓
H_victim(t+n) ≤ H_victim(t)
recurrence ↓

7. Gates

7.1 Required Gates

7.2 Gate Failure Rule

If any required gate fails:

∅ — Victim-Centered Restoration cannot validly proceed in that form.

The system must either:

• restore affected-node boundaries;
• stop burden transfer;
• increase auditability;
• reroute responsibility;
• delay reconciliation;
• route to repair-first intake;
• route to safe decoupling or reintegration membrane depending on trust viability.

8. Diagnostics

8.1 Required Diagnostic Trends

8.2 Arc-Specific Diagnostic Thresholds

Suggested thresholds:

BΣ_victim ↑
victim_agency ↑
burden_transfer ↓
repair_alignment ↑
Au_harm ↑
H_victim ↓
R_repair-directed ↑
trust_viability tested before contact
recurrence ↓ across U7

Victim-Centered Restoration is not complete if:

affected node still carries repair labor
testimony is extracted for system legitimacy
reconciliation is pursued before repair
apology substitutes for material change
responsibility remains flattened
participation is treated as consent
closure is declared without temporal proof

9. Anti-Patterns / False Restorations

9.1 Common False Versions

This arc is being simulated, not executed, if:

• harmed nodes are centered in language but not protected in process;
• testimony is collected without repair obligation;
• reconciliation is framed as the repair;
• public apology replaces boundary or material repair;
• affected nodes must educate responsible nodes;
• harmed nodes must comfort or validate institutional transition;
• “healing” language hides burden transfer;
• participation metrics are treated as trust;
• refusal is framed as obstruction;
• legitimacy recovery is prioritized over repair.

9.2 Named Anti-Pattern Links

10. Completion Criteria

10.1 Post-State Signature

10.2 Temporal Proof

Victim-Centered Restoration cannot be declared complete until affected-node burden decreases and repair remains valid over time.

Template:

Completion requires BΣ_victim(t+n) ≥ BΣ_victim(t),
victim_agency(t+n) ≥ victim_agency(t),
burden_transfer decreasing,
H_victim(t+n) ≤ H_victim(t),
and recurrence decreasing across U7.

Minimum temporal proof:

• affected node carries less repair burden;
• repair obligations are completed or progressing;
• refusal remains protected;
• contact or reintegration remains compatibility-tested;
• public closure does not outrun actual repair;
• recurrence and secondary harm decline.

10.3 Completion Statement

Canonical format:

This arc is complete only when affected-node boundaries, agency, truth, consent, and repair needs are protected; repair burden is routed to responsible and capable nodes; and no reconciliation, reintegration, legitimacy recovery, or closure claim outruns temporal proof of actual repair.

11. Cross-Links

11.1 Related Restoration Arcs

11.2 Related Failure Modes

11.3 Related Diagnostics

BΣ, BΣ_victim, H, H_victim, Au, Au_harm, R, O, K, σ(t), µᵢ, ι, burden_transfer, repair_alignment, victim_agency, trust_viability, Φ/O divergence, recurrence

11.4 Related Laws / Invariants

INV — Harmed nodes must not be assigned responsibility for repairing the harm done to them.
INV — Repair precedes reconciliation.
INV — Participation is not proof of trust.
INV — Refusal remains valid during restoration.
LAW — Legitimacy-first repair accumulates hidden debt.
LAW — Testimony extraction without repair becomes secondary harm.
LAW — False reconciliation preserves failure geometry.
LAW — Φ improvement is not O restoration.

12. Domain Notes

12.1 AI / Cognitive Infrastructure

Check:

• user harm reports;
• misclassification victims;
• privacy or memory harm;
• affected-user burden in appeal processes;
• whether users must provide repeated proof;
• whether product trust recovery outruns actual repair;
• whether AI systems center platform reputation over user boundary restoration.

AI victim-centered restoration requires affected-user boundary, appeal, data repair, memory correction, consent repair, and burden reduction before trust or legitimacy claims.

12.2 Justice / Governance / Legitimacy

Check:

• harmed-node safety;
• testimony burden;
• public apology;
• reconciliation pressure;
• institutional legitimacy recovery;
• process participation;
• material repair;
• accountability and prevention.

JGL victim-centered restoration ensures repair proceeds from harmed-node reality rather than institutional closure needs.

12.3 Biology / Medicine

Conceptual systems mapping only.

Victim-Centered Restoration in biological or medical-adjacent systems means protecting the affected node’s agency, pacing, consent, interpretation boundaries, and repair needs rather than centering institutional, professional, or explanatory closure.

Not diagnosis.

Not treatment.

Not medical advice.

12.4 Economy

Check:

• harmed workers;
• harmed consumers;
• debt-burdened nodes;
• platform users;
• exploited communities;
• externalized-cost victims;
• compensation, portability, exit, and burden reduction.

Economic victim-centered restoration requires repair of real burden, not merely apology, discount, dispute workflow, or brand recovery.

12.5 CMS / Meaning / Archetypes

Check:

• forgiveness pressure;
• healing narratives;
• sacred reconciliation;
• victim-symbol use;
• collective harmony;
• rescuer / healer archetypes;
• pressure to transform harm into lesson for others.

Meaning systems require victim-centered restoration when symbolic healing risks extracting meaning, forgiveness, or legitimacy from harmed nodes.

13. Machine-Readable Metadata

id: "RA-041"
title: "Victim-Centered Restoration"
aliases:
  - "Victim-Centered Repair"
family_primary: "Justice / Governance / Legitimacy"
families_secondary:
  - "Core"
  - "Boundary"
  - "Consent"
  - "Coherence"
  - "Auditability"
  - "Institutional Design"
  - "AI Governance"
  - "Security"
  - "Economy"
  - "CMS"
treatment: "Canon Parent Arc"
status: "Canon-Ready"
scope:
  - "Relational"
  - "Institutional"
  - "AI"
  - "Security"
  - "Economic"
  - "Civilizational"
  - "Cross-Domain"
u_layers:
  failure_origin:
    - "usually U2 boundary / consent / exposure"
    - "often U3 repair process / governance pathway"
    - "often U4 reconciliation / legitimacy narrative"
  symptom_visible:
    - "U4 apology / empathy / healing / reconciliation / legitimacy language"
    - "Φ process completion / public trust optics"
  repair_required:
    - "same or lower than layer where harmed node was displaced or burdened"
  validation:
    - "U5"
    - "U6"
    - "U7"
operators:
  scaffold: "Π affected-node boundary protection → Σ victim-centered repair invariant → Au harm / burden trace → FI affected-node feedback integrity → Θ pressure / legitimacy-gain damping → ℛ repair obligation routing → Λ trust / contact viability test → Τ burden / recurrence validation"
  sequence:
    - "Π"
    - "Σ"
    - "Au"
    - "FI"
    - "Θ"
    - "ℛ"
    - "Λ"
    - "Τ"
state_variables:
  primary:
    - "BΣ"
    - "H"
    - "Au"
    - "R"
    - "O"
  secondary:
    - "K"
    - "µᵢ"
    - "ι"
    - "Φ"
diagnostics:
  - "BΣ_victim"
  - "H_victim"
  - "Au_harm"
  - "burden_transfer"
  - "repair_alignment"
  - "victim_agency"
  - "trust_viability"
  - "Φ/O divergence"
  - "recurrence"
gates_required:
  - "FI-Gate"
  - "HR-Gate"
  - "MS-Gate"
  - "Au-Actuation"
  - "BΣ-Gate"
  - "Λ-Gate"
  - "☷ᵢ"
linked_failure_modes:
  - "Victim Burden Transfer"
  - "Repair Burden Inversion"
  - "False Reconciliation"
  - "Restoration Bypass"
  - "Affected-Node Labor Capture"
  - "Consent Theater"
  - "Responsibility Flattening"
  - "Both-Sides Flattening"
  - "Legitimacy-First Repair"
  - "Procedural Extraction"
  - "Compassion Theater"
  - "Rank Immunity"
linked_restoration_arcs:
  - "RA-001"
  - "RA-002"
  - "RA-005"
  - "RA-014"
  - "RA-018"
  - "RA-033"
  - "RA-034"
  - "RA-040"
  - "RA-042"
  - "RA-043"
  - "RA-044"
  - "RA-045"
  - "RA-046"
anti_patterns:
  - "Victim-Symbol Theater"
  - "Testimony Extraction"
  - "Reconciliation-First Repair"
  - "Apology-as-Repair"
  - "Healing Narrative Capture"
  - "Refusal-as-Obstruction"
  - "Participation-as-Trust"
completion_tests:
  - "BΣ_victim increases"
  - "victim_agency increases"
  - "burden_transfer decreases"
  - "repair_alignment increases"
  - "Au_harm increases"
  - "H_victim decreases"
  - "R_repair-directed increases"
  - "trust_viability tested before contact"
  - "recurrence decreases across U7"
summary: "Victim-Centered Restoration restores repair geometry around the harmed or affected node by protecting boundary, agency, consent, truth, dignity, burden allocation, and repair priority before reconciliation, reintegration, legitimacy recovery, or system closure is attempted."

Final Calibration Rule

Victim-Centered Restoration answers six questions:

What hidden debt is being generated by displacing the harmed or affected node from the repair center?
What boundary, agency, consent, truth, burden, or repair path must be restored around the affected node?
What auditability proves harm, process burden, responsibility, and repair obligations are traceable?
What apology, participation metric, healing narrative, reconciliation claim, or legitimacy signal must remain provisional until affected-node repair is proven?
What trajectory becomes viable once repair burden moves away from the harmed node and toward responsible / capable nodes?
How is victim-centered restoration proven over time without testimony extraction, false reconciliation, burden transfer, legitimacy-first repair, or symbolic closure?