0. Registry Classification

1. Purpose

1.1 What This Arc Repairs

Origin-Layer Repair repairs damage that persists because prior interventions addressed the visible symptom layer instead of the layer where the failure, burden, or hidden debt is actually generated.

It applies when a system has stabilized enough to proceed beyond containment and causal clarification, but repair is at risk of being performed too high in the stack.

This arc repairs the wrong-layer repair pattern by:

• localizing the failure origin;
• distinguishing origin layer from symptom layer;
• rejecting symbolic or procedural substitutes;
• provisioning restoration capacity at the correct layer;
• applying repair at the same or lower U-layer than the failure origin;
• validating that recurrence decreases after repair.

Origin-Layer Repair is the canonical arc that prevents restoration from becoming appearance management.

1.2 Core Restoration Function

This arc restores coherence by locating the layer where hidden debt is actually generated, blocking insufficient higher-layer repair, applying `ℛ` at the same or lower U-layer than the failure origin, and validating that recurrence weakens over time.

Origin-Layer Repair is the bridge between truth work and actual restoration. It converts causal clarification into layer-correct repair.

2. Use Conditions

2.1 When to Apply

Use this arc when:

• the active harm has been stabilized;
• the causal chain is sufficiently clarified to identify likely origin layer;
• prior repairs have not reduced recurrence;
• the system is offering explanation, apology, policy, dashboard, punishment, or symbolic closure as repair;
• visible symptoms appear at one U-layer while damage originates lower in the stack;
• hidden debt remains after apparent intervention;
• repair is being attempted where authority is visible rather than where damage is generated;
• recurrence persists under new labels;
• material, boundary, energetic, infrastructural, or capacity damage is being answered with narrative or policy alone.

Examples:

• a policy update is offered for a boundary violation that requires access, consent, and exit repair;
• an apology is offered for material or economic harm without restitution;
• a dashboard improvement is offered for a security failure without architecture repair;
• an explanation is offered for biological, energetic, or logistical overload;
• a governance procedure is completed while affected-node repair remains absent;
• an AI model correction is claimed while memory, evaluator, tool, or permission layers remain unchanged.

2.2 When Not to Apply

Do not apply this arc when:

• active harm is still cascading and emergency stabilization is required;
• causal clarification has not identified even a likely origin layer;
• the system cannot increase auditability enough to distinguish symptom from source;
• repair capacity is insufficient for the origin layer;
• the arc would force affected nodes to perform the repair work;
• the system refuses to reject symbolic substitutes;
• origin-layer repair would be used to bypass immediate boundary protection;
• a safe rollback or review path does not exist.

Origin-Layer Repair must not become deep repair rhetoric.

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 stabilization, causal clarification, audit surface expansion, or slack regeneration before attempting origin-layer repair.

3. Failure / Damage Signature

3.1 Pre-State Across S

3.2 Primary Failure Links

3.3 Origin-Layer Localization

Canon rule:

Repair must occur at the same or lower U-layer than the failure origin.

Layer examples:

4. Restoration Objective

4.1 Canonical Objective

Restore coherence by applying repair at the layer where hidden debt is generated, reducing recurrence, and preventing higher-layer symbolic action from being mistaken for restoration.

Formal objective:

origin layer identified
repair layer ≤ failure origin layer
H_origin ↓
R_origin sufficient
recurrence ↓
Φ/O divergence ↓

Expanded objective:

Convert causal clarification into real repair by ensuring the intervention reaches the layer that generates the failure, not merely the layer where the failure is visible.

4.2 Non-Goals

This arc does not aim to:

• improve appearance of recovery;
• complete symbolic closure;
• preserve the prior baseline by default;
• replace material repair with apology;
• replace boundary repair with intent;
• replace capacity repair with policy;
• replace architecture repair with dashboard improvement;
• replace recurrence repair with one-time correction;
• use complexity as an excuse to avoid repair;
• assign repair burden to the harmed node.

5. Operator Sequence

5.1 Minimal Operator Scaffold

Μ layer map → Au trace confirmation → Σ substitute rejection → Π repair boundary → ℛ(origin layer) → Τ recurrence validation

Universal grammar alignment:

Σ + Θ → Π → ℛ(U_origin or lower) → Au + FI → Τ → Temporal Proof

This arc is complete only when the repair reaches the origin layer and recurrence begins to decline.

5.2 Operator Step Table

5.3 Sequence Notes

This arc is layer-gated.

The sequence may repeat if recurrence reveals that the true origin layer was lower or different than initially identified.

The following steps cannot be skipped:

origin-layer localization
symbolic substitute rejection
repair at same or lower layer
feedback integrity check
temporal recurrence validation

If repair improves the visible symptom layer while hidden debt continues at the origin layer, the arc has failed.

If Φ improves while O remains unstable, the arc has inverted.

6. Restoration Phases

Phase 0 — Confirm Causal Readiness

Purpose: Ensure the system has enough causal legibility to attempt layer-correct repair.

Actions:

• confirm active harm is contained;
• review causal map from RA-002 or equivalent truth work;
• identify origin-layer candidates;
• identify visible symptom layer;
• check whether auditability is sufficient for repair assignment.

Validation:

origin-layer candidates visible
symptom layer separated from likely source
repair assignment does not exceed evidence

Phase 1 — Localize Origin Layer

Purpose: Identify where hidden debt is generated or sustained.

Actions:

• map U-layer origin;
• distinguish trigger from source;
• distinguish symptom from damage;
• distinguish amplifier from cause;
• identify where repair must reach;
• identify whether multiple layers require staged repair.

Validation:

failure origin localized or narrowed
required repair layer named
wrong-layer repair risk visible

Phase 2 — Reject Insufficient Substitutes

Purpose: Prevent higher-layer repair theater from replacing actual repair.

Actions:

• identify symbolic substitute paths;
• block premature apology, policy, dashboard, report, punishment, or recoupling as closure;
• compare proposed repair layer to failure origin layer;
• name any mismatch;
• require layer-correct repair before completion claim.

Validation:

repair layer ≤ failure origin layer
symbolic substitutes blocked
Φ cannot certify restoration alone

Phase 3 — Provision Restoration Capacity

Purpose: Ensure the system has enough repair capacity at the required layer.

Actions:

• estimate R_eff required for origin-layer repair;
• reduce load or gain if needed;
• route resources to the damaged layer;
• protect affected nodes from carrying repair burden;
• create rollback and review paths.

Validation:

R_eff sufficient for origin-layer repair
repair burden assigned by responsibility gradient
affected-node capacity preserved

Phase 4 — Apply Origin-Layer Repair

Purpose: Reduce hidden debt where it is actually generated.

Actions:

• repair material, boundary, classifier, narrative, timing, field, or recurrence layer as indicated;
• restore damaged interface, capacity, access, consent, feedback, or memory structure;
• remove conditions regenerating hidden debt;
• document repair action and trace.

Validation:

H_origin ↓
Au preserved
BΣ restored where applicable
R increases rather than depletes

Phase 5 — Feedback Integrity Check

Purpose: Verify that repair is being measured by coherence rather than appearance.

Actions:

• separate Φ from O;
• identify dashboard, reputation, compliance, or silence effects;
• compare affected-node field effects to internal claims;
• monitor recurrence signals;
• verify feedback channels remain uncaptured.

Validation:

Φ/O divergence ↓
FI restored
field response matches repair claim

Phase 6 — Temporal Proof

Purpose: Confirm the repair survives recurrence, delay, and perturbation.

Actions:

• monitor recurrence;
• test delayed effects;
• verify affected-node state where applicable;
• check whether hidden debt re-accumulates;
• re-localize if recurrence returns.

Validation:

H(t+n) ≤ H(t)
τ_m ↓
recurrence ↓
O stable under Δ

7. Gates

7.1 Required Gates

7.2 Gate Failure Rule

If any required gate fails:

∅ — Origin-Layer Repair cannot validly proceed in that form.

The system must either:

• return to causal clarification;
• expand audit surface;
• regenerate slack;
• protect boundaries;
• reroute to a lower layer;
• abort symbolic repair;
• delay recoupling until compatibility can be tested.

8. Diagnostics

8.1 Required Diagnostic Trends

8.2 Arc-Specific Diagnostic Thresholds

Suggested thresholds:

repair layer ≤ failure origin layer
H_origin decreases after repair
R_eff sufficient for repair load
Au preserved through intervention
Φ/O divergence decreases
recurrence decreases across U7

Origin-Layer Repair is not complete if:

visible symptoms improve but H_origin persists
repair is symbolic only
repair layer is higher than failure origin layer
affected nodes carry repair burden
recurrence returns under a new label
Φ improves while O remains unstable

9. Anti-Patterns / False Restorations

9.1 Common False Versions

This arc is being simulated, not executed, if:

• apology replaces restitution;
• policy replaces boundary repair;
• dashboard improvement replaces architecture repair;
• explanation replaces capacity restoration;
• punishment replaces system repair;
• visible silence replaces field coherence;
• temporary symptom reduction replaces recurrence reduction;
• the harmed node is required to adapt instead of the failure source being repaired;
• repair is performed where authority is easiest, not where damage originates;
• layer ambiguity is used to avoid responsibility;
• the system declares repair before temporal validation.

9.2 Named Anti-Pattern Links

10. Completion Criteria

10.1 Post-State Signature

10.2 Temporal Proof

Origin-Layer Repair cannot be declared complete until the repair survives recurrence monitoring and delayed review.

Template:

Completion requires repair_layer ≤ failure_origin_layer,
H_origin(t+n) ≤ H_origin(t),
O stable under Δ,
and recurrence decreasing across U7.

Minimum temporal proof:

• the same failure does not recur under a new label;
• hidden debt does not re-accumulate at origin layer;
• field effects match repair claim;
• affected boundaries remain repaired;
• repair remains traceable;
• follow-on arcs can proceed from a cleaner baseline.

10.3 Completion Statement

Canonical format:

This arc is complete only when repair has reached the same or lower U-layer than the failure origin, hidden debt at that layer is reduced, visible improvement no longer depends on symbolic substitution, and recurrence decreases over time.

11. Cross-Links

11.1 Related Restoration Arcs

11.2 Related Failure Modes

11.3 Related Diagnostics

H, Au, BΣ, R, 𝓓(t), τ_resp, τ_m, recurrence, Φ/O divergence

11.4 Related Laws / Invariants

INV — Repair must occur at the same or lower U-layer than failure origin.
INV — Coherence cannot be inferred from appearance alone.
LAW — Restoration is not the inverse of failure.
LAW — Φ improvement is not O restoration.
LAW — Slack is required for repair.
LAW — Hidden debt persists when repair occurs above the damage layer.
LAW — Recurrence proves unresolved origin geometry.

12. Domain Notes

12.1 AI / Cognitive Infrastructure

Check:

• whether the failure originated in model behavior, system prompt, classifier, evaluator, tool permission, memory scope, policy layer, infrastructure, or governance authority;
• whether a visible answer correction masks evaluator or memory drift;
• whether rollback repairs the actual failing layer;
• whether logs preserve the chain between trigger and output;
• whether user meaning is restored rather than merely reclassified.

AI origin-layer repair must not treat response rewriting as sufficient when the failure originated in memory, policy, classifier, tooling, governance, or incentive structure.

12.2 Justice / Governance / Legitimacy

Check:

• whether apology substitutes for material repair;
• whether personnel action substitutes for structural repair;
• whether policy update substitutes for boundary repair;
• whether public statement substitutes for truth;
• whether harmed nodes are asked to adapt to an unrepaired system;
• whether rank immunity protects the actual origin layer.

JGL origin-layer repair requires responsibility gradient mapping before repair burden is assigned.

12.3 Biology / Medicine

Conceptual systems mapping only.

Origin-layer repair in biological systems means distinguishing visible symptoms from boundary, classifier, circulation, timing, recurrence, load, or clearance layer conditions.

Not diagnosis.

Not treatment.

Not medical advice.

12.4 Economy

Check:

• whether growth substitutes for clearance;
• whether liquidity substitutes for debt repair;
• whether market confidence substitutes for hidden-cost reduction;
• whether local profit masks global burden;
• whether survival-edge pressure remains unchanged;
• whether extraction pathways are preserved under new terms.

Economic origin-layer repair must reach circulation, debt, externality, allocation, contract, or clearance geometry where the burden is generated.

12.5 CMS / Meaning / Archetypes

Check:

• whether symbolic insight substitutes for boundary repair;
• whether meaning replaces material action;
• whether sacred language bypasses auditability;
• whether identity certainty blocks layer localization;
• whether archetypal coherence is being claimed while geometry remains unchanged.

Meaning systems require preserving symbolic value while refusing symbolic immunity.

13. Machine-Readable Metadata

id: "RA-003"
title: "Origin-Layer Repair"
aliases:
  - "Origin Repair"
family_primary: "Core"
families_secondary:
  - "Coherence"
  - "Auditability"
  - "Boundary"
  - "Scaling"
  - "Cybernetics"
  - "Justice / Governance / Legitimacy"
  - "AI Governance"
  - "Biology-Medicine"
  - "Economy"
treatment: "Canon Parent Arc"
status: "Canon-Ready"
scope:
  - "Local"
  - "Relational"
  - "Institutional"
  - "AI"
  - "Biological"
  - "Economic"
  - "Civilizational"
  - "Cross-Domain"
u_layers:
  failure_origin:
    - "U0"
    - "U1"
    - "U2"
    - "U3"
    - "U4"
    - "U5"
    - "U6"
    - "U7"
  symptom_visible:
    - "often U4"
    - "often U6"
    - "often Φ dashboards"
  repair_required:
    - "same or lower than failure origin layer"
  validation:
    - "U5"
    - "U6"
    - "U7"
operators:
  scaffold: "Μ layer map → Au trace confirmation → Σ substitute rejection → Π repair boundary → ℛ(origin layer) → Τ recurrence validation"
  sequence:
    - "Μ"
    - "Au"
    - "Σ"
    - "Π"
    - "ℛ"
    - "FI"
    - "Τ"
state_variables:
  primary:
    - "H"
    - "Au"
    - "R"
    - "recurrence"
  secondary:
    - "O"
    - "ι"
    - "BΣ"
    - "K"
    - "Φ"
diagnostics:
  - "𝓓(t)"
  - "τ_resp"
  - "τ_m"
  - "Φ/O divergence"
gates_required:
  - "FI-Gate"
  - "HR-Gate"
  - "MS-Gate"
  - "Au-Actuation"
  - "BΣ-Gate"
  - "Λ-Gate"
  - "☷ᵢ"
linked_failure_modes:
  - "Wrong-Layer Repair"
  - "Symbolic Repair"
  - "Pseudo-Restoration"
  - "Hidden Debt Persistence"
  - "Restoration Bypass"
  - "Procedural Theater"
  - "Policy Theater"
  - "Boundary Collapse"
  - "Capacity Collapse"
  - "Meaning Collapse"
linked_restoration_arcs:
  - "RA-001"
  - "RA-002"
  - "RA-004"
  - "RA-005"
  - "RA-006"
  - "RA-012"
  - "RA-014"
  - "RA-017"
anti_patterns:
  - "Wrong-Layer Repair"
  - "Symbolic Repair"
  - "Policy Theater"
  - "Procedural Theater"
  - "Pseudo-Restoration"
  - "Restoration Bypass"
  - "False Calm"
completion_tests:
  - "repair layer is same or lower than failure origin layer"
  - "H_origin decreases after repair"
  - "R_eff sufficient for repair load"
  - "Au preserved through intervention"
  - "Φ/O divergence decreases"
  - "recurrence decreases across U7"
summary: "Origin-Layer Repair restores coherence by locating the layer where hidden debt is generated, blocking higher-layer substitutes, repairing at the same or lower U-layer, and validating recurrence reduction over time."

Final Calibration Rule

Origin-Layer Repair answers six questions:

What hidden debt is still being generated at the source?
What boundary, capacity, interface, or structure must be repaired at its own layer?
What auditability proves the repair reached the origin rather than the symptom?
What coupling must remain blocked until origin-layer debt is reduced?
What trajectory becomes viable after repair reaches the correct layer?
How is recurrence reduction proven over time?