0. Plain Statement

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

Plain-language version:

A system cannot be truly repaired by acting only at a surface layer if the failure originated deeper in the stack. Explanations, apologies, policies, dashboards, symbolic gestures, or compliance updates may be useful, but they do not restore coherence unless the repair reaches the layer where the damage was created.

1. Formal Definition

The Origin-Layer Repair Law states that restoration must reach the same U-layer as the failure origin, or a lower supporting layer capable of reconditioning that origin layer.

Failure is often detected at a layer different from where it began. A U2 boundary violation may appear as a U4 narrative dispute. A U1 energy deficit may appear as U3 underperformance. A U7 recurrence debt may appear as a U4 misunderstanding. A U0 substrate injury may appear as a behavioral, symbolic, or procedural issue.

When repair only addresses the layer where the failure is visible, the system may look improved while the originating condition remains active.

Therefore, valid restoration requires origin-layer tracing and layer-matched repair.

This law does not say higher-layer action is useless. A statement, explanation, policy, ritual, apology, or dashboard can begin repair by making the problem legible. But it becomes restoration only if it leads to repair at the layer where the failure originated.

2. Canonical Form

Core form:

Failure at Ux ⇒ repair at Ux or lower

Expanded form:

origin(Ux failure) > depth(repair) ⇒ H persists ∧ recurrence↑ ∧ pseudo-restoration risk↑

Restoration-valid form:

repair_depth ≤ failure_origin_depth ⇒ H↓ + recurrence↓ + BΣ↑/stable + R_eff↑ + O↑/stable over Τ

Layer-order convention:

U0 < U1 < U2 < U3 < U4 < U5 < U6 < U7 < U8

This means lower U-layers are more foundational support layers. Repair may occur at the failure layer itself or beneath it, but repair above the origin layer is not sufficient by itself.

Related variables:

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

Where:

3. Core Mechanism

The law unfolds when a system misidentifies the visible symptom layer as the repair layer.

Coherent origin-layer restoration pathway

failure appears
→ symptom layer is distinguished from origin layer
→ origin layer is audited
→ repair is routed to Ux or lower
→ hidden debt and recurrence drivers decrease
→ restoration is time-validated

Shallow repair pathway

failure appears
→ visible layer is treated as source
→ surface repair is applied
→ observable pressure temporarily decreases
→ origin debt remains
→ recurrence returns or migrates

The core mechanism is:

repair above the failure origin cannot recondition the layer that generated the failure

Detailed mechanism:

1. Failure originates at a specific U-layer.

The actual break may occur in substrate, energy, boundary, execution, classification, timing, field effect, recurrence, or environment.

1. The system detects a higher-layer expression.

The visible failure often appears in language, behavior, output, policy, symbol, process, performance, or public legitimacy.

1. Repair is routed to the visible layer.

The system offers explanation, apology, control, compliance, messaging, process adjustment, or symbolic closure.

1. Observable pressure temporarily decreases.

The system may see fewer complaints, fewer visible errors, calmer dashboards, better optics, or a return to apparent stability.

1. The origin layer remains unrepaired.

The damaged boundary, depleted capacity, corrupted memory, invalid contract, broken logistics, substrate injury, or environmental forcing continues generating the same pattern.

1. Recurrence reveals the repair-depth error.

The failure returns, migrates, or reappears under load because the repair did not reach the origin layer.

4. When This Law Applies

This law applies when the visible failure layer differs from the failure origin layer.

It is especially important when:

• an apology is used for a boundary violation;
• an explanation is used for a material injury;
• a compliance update is used for a legitimacy failure;
• a policy patch is used for a structural failure;
• a dashboard improvement is used for an operational failure;
• a behavioral demand is used for an energy deficit;
• a symptom reduction is used for substrate repair;
• a public statement is used for recurrence repair;
• a process update is used for a contract validity failure;
• a security ticket is closed without repairing the exploited membrane;
• an AI output patch is used without classifier, memory, or governance repair;
• an affected node is asked to move on before the origin layer has been repaired.

The law applies strongly when:

repair_layer > failure_origin_layer

or when:

visible symptom repair is claimed as full restoration

Typical domains:

5. When This Law Does Not Apply

This law should not be used to dismiss higher-layer repair actions.

Higher-layer actions can be useful when they:

• make the failure legible;
• stop ongoing harm;
• preserve safety during triage;
• restore auditability;
• initiate accountability;
• coordinate repair;
• explain the repair path;
• reduce confusion while deeper repair proceeds;
• signal commitment to layer-matched restoration.

The law does not say all repair must begin at the origin layer. Sometimes the system must stabilize at U3 or U4 before deeper work can safely proceed.

The law says restoration should not be claimed until repair reaches the origin layer or a lower supporting layer.

False-positive cases:

Important distinction:

Higher-layer action can initiate, coordinate, or communicate restoration. It cannot substitute for origin-layer repair.

6. Diagnostic Signature

Canonical diagnostic:

Failure at Ux ⇒ repair at Ux or lower

Warning signature:

visible repair completed
repair_layer > failure_origin_layer
H unchanged
recurrence unchanged
closure claimed
⇒ surface repair / pseudo-restoration

Common indicators:

Additional diagnostics:

7. Failure Pattern

If ignored, this law produces surface repair, recurrence, and pseudo-restoration.

General failure pathway:

failure originates at Ux
→ symptom appears at Uy
→ repair is applied at Uy
→ visible pressure decreases
→ origin layer remains damaged
→ H persists
→ recurrence returns
→ trust and legitimacy decline

Where:

Uy > Ux

Common failure modes:

• Surface Repair — the visible layer improves while the failure origin remains unchanged.
• Symbolic Closure — statement, apology, ritual, or acknowledgement replaces material repair.
• Compliance Theater — procedure improves while boundary, legitimacy, or recurrence debt remains.
• Policy Patch Without Boundary Repair — policy changes without repairing the violated membrane.
• Apology Without Material Repair — apology substitutes for consequence, restoration, or prevention.
• Symptom Suppression — observable symptoms decrease while substrate or energy-layer failure persists.
• Hidden Debt Persistence — unrepaired origin-layer cost remains stored.
• Recurrence Persistence — the same pattern returns because the source remains active.
• Premature Closure — closure is claimed before origin repair is validated.
• Pseudo-Restoration — optics improve while coherence does not.
• Delayed Collapse — origin debt resurfaces after apparent repair.

Compact failure signature:

repair_layer > failure_origin_layer ⇒ H persists ∧ recurrence↑ ∧ ι↑

8. Restoration Implications

Restoration requires tracing the origin layer before claiming repair.

The first restoration question is not:

What visible repair will reduce pressure?

The first restoration question is:

Where did the failure originate, and what repair reaches that layer?

Restoration priorities:

1. Map the symptom layer.
2. Trace the origin layer.
3. Distinguish visible expression from failure source.
4. Audit hidden debt created at the origin layer.
5. Stabilize the system enough to prevent further harm.
6. Route repair to the origin layer or lower.
7. Rebuild restoration capacity at the required layer.
8. Repair damaged boundaries, capacity, memory, logistics, or substrate directly.
9. Reduce recurrence drivers.
10. Time-validate repair under renewed load.

Relevant restoration arcs:

Minimal restoration sequence:

map symptom layer
→ trace origin layer
→ stabilize acute harm
→ restore auditability
→ repair at Ux or lower
→ reduce recurrence
→ validate over Τ

Temporal validation requirement:

repair_depth ≤ failure_origin_depth
H↓
BΣ stable or rising
R_eff↑
K / σ↑
recurrence↓
𝓓↑
Au↑
FI intact
µᵢ stable
O stable or rising

9. Design Rule

Do not claim restoration until the repair pathway reaches the failure origin layer.

Operational design requirements:

• Require origin-layer tracing before closure.
• Separate symptom layer from source layer.
• Map every repair action to a U-layer.
• Test whether repair reached the originating layer.
• Preserve auditability across the full restoration pathway.
• Use higher-layer actions as routing, not substitution.
• Require recurrence testing after apparent repair.
• Require material repair when the damaged layer is material.
• Require boundary repair when the damaged layer is boundary-level.
• Require capacity repair when the damaged layer is energy / slack-level.

Avoid:

• apology without boundary restoration;
• explanation without material correction;
• compliance update without legitimacy repair;
• dashboard improvement without operational repair;
• symptom suppression without substrate repair;
• policy update without origin-layer change;
• enforcement without repair;
• recoupling before boundary stability;
• closure before recurrence reduction;
• treating U4 improvement as proof of U0–U3 or U7 repair.

10. Cross-Scale Expressions

11. Examples

Example A — Institutional Boundary Violation

Scenario:

An institution violates a person’s boundary, then issues a public apology without changing access rules, consent structures, reporting pathways, consequence, or prevention.

Law expression:

failure_origin = U2
repair_attempt = U4
U4 apology cannot repair U2 boundary violation

Interpretation:

The apology may begin restoration by acknowledging the violation, but it is not restoration. Repair requires boundary reconstitution, consequence, prevention, harmed-node repair, and auditability at the layer where the violation occurred.

Example B — Biological Energy Deficit

Scenario:

A biological system is depleted at the energy / capacity layer, but the response is increased demand, productivity pressure, motivational framing, or symptom suppression.

Law expression:

failure_origin = U1
repair_attempt = U3 / U4
U3 performance correction cannot repair U1 energy deficit

Interpretation:

The problem is not primarily effort, discipline, or execution. Repair must address energy, slack, restoration capacity, circulation, load, tolerance, and recovery.

Example C — AI Governance Patch

Scenario:

An AI system produces repeated classification harm. The provider changes the public explanation and adds output-level guardrails, but the underlying classifier, audit process, memory, governance, or training pipeline remains unchanged.

Law expression:

failure_origin = U4 / U7
repair_attempt = U4 surface response
surface policy update ≠ origin-layer repair

Interpretation:

A response patch may reduce visible incidents, but recurrence remains likely if the classifier, memory, recurrence pattern, and governance pathway are not repaired.

Example D — Security Incident Closure

Scenario:

A security team closes an incident ticket after removing malware, but does not repair the access path, privilege boundary, logging gap, persistence mechanism, or recurrence pathway that allowed intrusion.

Law expression:

visible incident = U3
origin_failure = U2 / U7
ticket closure ≠ boundary or recurrence repair

Interpretation:

The incident is contained, not restored. True repair requires correcting the first failed membrane and validating that recurrence risk has decreased.

Example E — Economic Contract Harm

Scenario:

A harmful fee is refunded, but the contract remains coercive, exit remains costly, terms remain opaque, and the same population remains structurally unable to refuse.

Law expression:

visible harm = U4 / U3
failure_origin = U2 contract boundary + U1 survival constraint
refund ≠ contract-state repair

Interpretation:

The refund may reduce one visible cost, but the origin-layer failure persists if consent, exit, boundary clarity, and survival coercion remain unrepaired.

Example F — Symbolic Restoration Without Material Repair

Scenario:

A cultural or institutional system publicly acknowledges harm but offers no material repair, no boundary redesign, no accountability, no recurrence prevention, and no transfer of burden away from harmed nodes.

Law expression:

symbolic repair = U4
origin damage = U2 / U6 / U7
U4 acknowledgement cannot repair U2-U7 origin debt alone

Interpretation:

Symbolic recognition can be meaningful, but it becomes pseudo-restoration when treated as a substitute for origin-layer repair.

12. Relationship to Nearby Laws

Aliases folded into this law:

• Origin-Layer Repair Law
• Same-Layer Repair Law
• Origin-Depth Repair Law
• Repair Must Reach the Source Law
• Layer-Matched Restoration Law
• Surface Repair Failure Law

Deduplication note:

This law should remain the root restoration-depth law. LAW-061 handles restoration sequencing, LAW-062 handles non-inverse restoration mechanics, LAW-064 handles debt-reduction proof, LAW-065 handles pseudo-restoration, and LAW-068 handles the boundary-specific case.

13. Operator Mapping

Coherent operator sequence:

Γ(symptom layer + origin layer) → Θ(origin uncertainty) → Σ(repair scope) → Au/FI(trace and feedback) → Π(stabilize if needed) → ℛ(Ux or lower) → Ψ(validate affected state) → Τ(validate H↓ + recurrence↓ + O↑)

Inverted operator sequence:

failure visible at Uy → Γ(Uy treated as source) → Π(surface repair) → closure claimed → H remains at Ux → recurrence persists → Ξ / ι↑ → pseudo-restoration

14. Machine-Readable Summary

id: "LAW-063"
name: "Origin-Layer Repair Law"
type: "law"
status: "draft"
family:
  - "Restoration Laws"
summary: "Repair must occur at the same or lower U-layer than the layer where the failure originated."
canonical_statement: "Repair must occur at the same or lower U-layer than the failure origin."
core_form: "Failure at Ux ⇒ repair at Ux or lower"
expanded_form: "origin(Ux failure) > depth(repair) ⇒ H persists ∧ recurrence↑ ∧ pseudo-restoration risk↑"
restoration_validity_form: "repair_depth ≤ failure_origin_depth ⇒ H↓ + recurrence↓ + BΣ↑/stable + R_eff↑ + O↑/stable over Τ"
variables:
  primary:
    - "Ux"
    - "repair_depth"
    - "failure_origin_depth"
    - "ℛ"
    - "H"
    - "BΣ"
    - "R"
    - "R_eff"
    - "K"
    - "σ"
  secondary:
    - "O"
    - "ε"
    - "ι"
    - "Au"
    - "µᵢ"
    - "Φ"
    - "Λ"
    - "⊗"
    - "Γ"
    - "Π"
    - "Θ"
    - "Σ"
    - "Ψ"
    - "Τ"
    - "FI"
diagnostics:
  - "Origin-Layer Trace"
  - "Repair Depth"
  - "Restoration Validity"
  - "Hidden Debt"
  - "Recurrence"
  - "Ring-Down"
  - "Boundary Integrity"
  - "Restoration Capacity"
  - "Effective Auditability"
  - "Slack"
  - "Temporal Proof"
  - "Coherence Trajectory"
  - "Pseudo-Restoration Risk"
failure_modes:
  - "Surface Repair"
  - "Symbolic Closure"
  - "Compliance Theater"
  - "Policy Patch Without Boundary Repair"
  - "Apology Without Material Repair"
  - "Symptom Suppression"
  - "Hidden Debt Persistence"
  - "Recurrence Persistence"
  - "Premature Closure"
  - "Pseudo-Restoration"
  - "Control-Restoration Confusion"
  - "Delayed Collapse"
restoration_arcs:
  - "Origin-Layer Repair"
  - "Boundary Reconstitution"
  - "Auditability Restoration"
  - "Restoration Capacity Rebuild"
  - "Slack Regeneration"
  - "Controlled Decoupling"
  - "Temporal Validation"
  - "Recurrence Reduction"
  - "Closure Stack Completion"
  - "Material Repair"
related_laws:
  - "LAW-006"
  - "LAW-007"
  - "LAW-008"
  - "LAW-009"
  - "LAW-010"
  - "LAW-011"
  - "LAW-012"
  - "LAW-013"
  - "LAW-030"
  - "LAW-041"
  - "LAW-047"
  - "LAW-050"
  - "LAW-052"
  - "LAW-061"
  - "LAW-062"
  - "LAW-064"
  - "LAW-065"
  - "LAW-066"
  - "LAW-067"
  - "LAW-068"
  - "LAW-069"
  - "LAW-070"
  - "LAW-073"
  - "LAW-075"
  - "LAW-076"
  - "LAW-082"
related_invariants:
  - "INV-001"
  - "INV-006"
  - "INV-077"
  - "INV-078"
  - "INV-079"
operator_sequence:
  coherent:
    - "Γ symptom layer + origin layer"
    - "Θ origin uncertainty"
    - "Σ repair scope"
    - "Au/FI trace and feedback"
    - "Π stabilize if needed"
    - "ℛ Ux or lower"
    - "Ψ validate affected state"
    - "Τ validate H↓ + recurrence↓ + O↑"
  inverted:
    - "failure visible at Uy"
    - "Γ Uy treated as source"
    - "Π surface repair"
    - "closure claimed"
    - "H remains at Ux"
    - "recurrence persists"
    - "Ξ / ι↑"
    - "pseudo-restoration"
aliases:
  - "Origin-Layer Repair Law"
  - "Same-Layer Repair Law"
  - "Origin-Depth Repair Law"
  - "Repair Must Reach the Source Law"
  - "Layer-Matched Restoration Law"
  - "Surface Repair Failure Law"
deduplication_note: "Root restoration-depth law. LAW-061 handles restoration sequencing, LAW-062 handles non-inverse restoration mechanics, LAW-064 handles debt-reduction proof, LAW-065 handles pseudo-restoration, and LAW-068 handles the boundary-specific case."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-063 — Origin-Layer Repair Law

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

Core form:

Failure at Ux ⇒ repair at Ux or lower

Expanded form:

origin(Ux failure) > depth(repair) ⇒ H persists ∧ recurrence↑ ∧ pseudo-restoration risk↑

Plain meaning:

A system cannot be truly restored by repairing only the visible layer if the damage originated deeper in the stack. Surface repair may reduce pressure, but origin debt persists until the source layer is repaired.

Failure form:

repair_layer > failure_origin_layer ⇒ H persists ∧ recurrence↑ ∧ ι↑

Restoration validity form:

repair_depth ≤ failure_origin_depth ⇒ H↓ + recurrence↓ + BΣ↑/stable + R_eff↑ + O↑/stable over Τ

Primary variables:

Ux, repair_depth, failure_origin_depth, ℛ, H, BΣ, R, R_eff, K, σ, O, ι, Au, µᵢ, Γ, Π, Θ, Σ, Ψ, Τ, FI

Diagnostic signature:

The visible repair is completed, but repair occurs above the origin layer; hidden debt, recurrence, boundary damage, or depleted capacity remain while restoration is claimed.

Failure risk:

Surface repair, symbolic closure, compliance theater, apology without material repair, symptom suppression, hidden debt persistence, recurrence persistence, premature closure, pseudo-restoration, delayed collapse.

Restoration priority:

Trace the failure origin, distinguish symptom layer from source layer, stabilize acute harm, restore auditability, repair at the origin layer or lower, reduce recurrence, and time-validate coherence recovery.