INV-036 — Repair Must Match Failure Origin

1. Definition

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

A failure may appear at one layer while originating at another.

Restoration is coherent only when the repair reaches the layer where the failure was generated or the deeper layer sustaining it.

Therefore:

Repair must match failure origin.

A higher-layer intervention may manage symptoms, stabilize the surface, or buy time.

But it cannot fully repair a lower-layer failure unless the origin layer is also addressed.

2. Purpose

This invariant prevents UTS from mistaking surface correction for origin-layer repair.

It protects against the error:

The symptom appeared here,
therefore the repair belongs here.

The correct UTS interpretation is:

The symptom appeared here.
Now localize the origin layer before selecting repair.

This is one of the most important restoration invariants because many systems attempt to repair deep failures with shallow interventions.

Examples:

• narrative repair for resource collapse
• policy repair for substrate failure
• compliance repair for legitimacy failure
• apology for boundary violation
• symptom suppression for biological burden
• dashboard change for operational failure
• AI refusal tuning for memory or representation failure
• messaging update for institutional trust collapse
• punishment for restoration failure
• symbolic ritual for unresolved material harm

These may help at their own layer, but they do not complete restoration if the origin layer remains unrepaired.

3. Constraint Statement

Canonical Form

Repair must match failure origin.

Expanded Form

A repair is incomplete if it occurs only above the layer where the failure
originated. Restoration must address the same U-layer as the origin of the
failure, or a lower sustaining layer, before closure can be considered
coherent.

Minimal Expression

Repair at origin layer.

U-Layer Form

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

Restoration Form

Symptom-layer repair is not origin-layer repair.

Governance Form

Narrative repair cannot restore material or boundary failure.

AI Form

Policy tuning cannot repair substrate, memory, audit, or interface failure by itself.

Biology Form

Symptom relief cannot fully repair burden architecture without origin-layer restoration.

Security Form

Incident response cannot replace root-cause boundary repair.

4. Structural Logic

Failures propagate across layers.

A failure may originate in one layer and appear somewhere else.

For example:

U1 resource collapse
        ↓
appears as U3 execution failure
        ↓
is narrated at U4 as motivation or compliance failure

If the system repairs only the U4 narrative, the U1 resource collapse remains.

That creates restoration debt.

The core pattern is:

failure origin
        ↓
symptom manifestation
        ↓
surface repair applied
        ↓
origin remains unrepaired
        ↓
recurrence returns

Coherent repair requires localization:

symptom appears
        ↓
trace causal path downward / across layers
        ↓
identify origin layer
        ↓
repair origin layer or deeper sustaining layer
        ↓
then repair surface effects
        ↓
validate recurrence reduction

A higher-layer response can be useful for stabilization.

But it must not be mistaken for full repair.

5. State-Vector Impact

Protected State Variables

O   — coherence
H   — hidden debt reduction
R   — restoration capacity
Au  — auditability of causal pathway
BΣ  — boundary integrity
K   — compatibility between repair and failure origin
µᵢ  — meaning / agent integrity

Primary Risk Variables

H   — hidden debt from origin-layer bypass
ι   — inversion when surface repair is misclassified as restoration
ε   — recurrence from unrepaired origin
Φ   — surface repair proxy / closure signal

Healthy Repair Pattern

failure localized
origin layer identified
repair applied at origin or lower layer
surface symptoms addressed after origin repair
H↓
recurrence↓
R↑
O↑ or stable

Violation Pattern

symptom appears
surface repair applied
origin unrepaired
H↑
ι↑
recurrence↑
O↓ over time

Pseudo-Restoration Pattern

U4 closure↑
origin-layer repair absent
recurrence persists
hidden debt remains

The central danger is repair at the wrong layer.

6. U-Layer Localization

Primary Layer

All U-layers, with repair-location logic spanning U0–U8.

This invariant governs how failures and repairs are localized across the whole U-layer stack.

U-Layer Reference

U0 — Substrate
U1 — Power / Budgets
U2 — Configuration / Boundaries
U3 — Execution
U4 — Classification / Metrics
U5 — Coordination / Time
U6 — Coherence Field
U7 — Memory / Recurrence
U8 — Environment / Forcing

Canonical Repair Rule

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

Common Failure Examples

U4 narrative cannot repair U1 resource collapse.
U4 apology cannot repair U2 boundary violation.
U3 enforcement cannot repair U7 recurrence.
U5 coordination cannot repair U6 coherence collapse.
U2 policy cannot repair U0 substrate failure without substrate repair.
U4 dashboard cannot repair U3 execution breakdown.
U3 patch cannot repair U2 scope ambiguity.
U6 meaning repair cannot replace U1 material support.

Common Failure Pattern

failure originates lower
        ↓
symptom appears higher
        ↓
higher-layer repair applied
        ↓
origin remains active
        ↓
recurrence returns

Common Misdiagnosis

Violation of this invariant is often misdiagnosed as:

• communication failure
• motivation failure
• compliance problem
• bad narrative
• insufficient training
• individual error
• symbolic failure
• policy gap
• poor messaging
• cultural resistance
• personality issue
• lack of discipline
• misunderstanding

The deeper issue may be:

The repair was applied above the failure origin.

7. Violation Signatures

7.1 Narrative Repair for Material Failure

A system uses explanation, messaging, framing, or symbolic closure to address resource, budget, labor, or substrate failure.

U1 failure
U4 repair
H remains

7.2 Apology for Boundary Violation Without Boundary Repair

A relational, institutional, AI, or contractual boundary is violated, and the system offers apology without changing the boundary condition.

U2 failure
U4 / U6 repair only
recurrence risk↑

7.3 Enforcement for Recurrence Failure

A system punishes repeated symptoms without repairing the memory or recurrence structure generating them.

U7 recurrence
U3 enforcement
H↑

7.4 Policy for Substrate Failure

A policy or rule is created for a substrate-level impossibility.

U0 failure
U2 policy
repair mismatch

7.5 Coordination for Coherence Collapse

A system schedules more meetings, rituals, reports, or coordination loops to repair a field-level coherence breakdown.

U6 failure
U5 coordination
coordination overhead↑
O not restored

7.6 Dashboard for Execution Failure

Metrics are adjusted or made visible, but execution pathways remain broken.

U3 failure
U4 dashboard
state unchanged

7.7 Symbolic Repair for Structural Harm

A symbolic act attempts to repair material, boundary, legal, economic, or institutional harm without structural repair.

U1 / U2 / U3 failure
U6 symbolic repair only
pseudo-restoration risk↑

7.8 AI Policy Patch for Interface Failure

An AI safety issue is addressed through policy language while memory, tool, consent, appeal, or representation boundaries remain broken.

U2 / U3 / U7 failure
U4 policy update
H remains

8. Related Failure Modes

Primary related failure modes:

• Repair Locality Failure
• Origin-Layer Bypass
• Pseudo-Restoration
• Restoration Bypass
• Premature Closure
• Narrative Substitution
• Policy Theater
• Dashboard Theater
• Symbolic Repair Substitution
• Punishment Substitute for Repair
• Training Theater
• Coordination Overhead Spiral
• Hidden Debt Accumulation
• Recurrence Blindness
• Auditability Collapse
• Boundary Collapse
• Legitimacy Debt
• Symptom Suppression
• Surface Stabilization Trap
• Layer Misdiagnosis

9. Related Restoration Arcs

Primary restoration arcs:

• Origin-Layer Repair
• Failure Localization
• Auditability Restoration
• Causal Path Reconstruction
• Boundary Reconstitution
• Resource Restoration
• Substrate Repair
• Execution Path Repair
• Classification Correction
• Coordination Recalibration
• Coherence Field Restoration
• Memory / Recurrence Repatterning
• Environmental Forcing Adjustment
• Restoration Capacity Rebuild
• Temporal Validation

Restoration Requirement

Repair must be rerouted to the failure origin.

Minimal sequence:

Identify symptom layer
        ↓
Trace causal pathway through U-layers
        ↓
Locate origin layer and sustaining lower layers
        ↓
Pause premature closure
        ↓
Repair at origin or lower layer
        ↓
Repair surface effects
        ↓
Track recurrence and ring-down
        ↓
Reclassify restoration only after time validation

10. Domain Expressions

AI

AI failures often appear as U4 safety or classification problems while originating elsewhere.

Examples:

bad refusal output → may originate in U4 classification, U2 policy boundary, U7 memory, or U3 tool routing
hallucination → may originate in retrieval, context boundary, uncertainty handling, or model substrate
user mistrust → may originate in appeal failure, memory opacity, or representation overreach
dependency → may originate in workflow design, portability, or interface incentives

AI restoration requires locating whether the issue is:

U0 model substrate
U1 compute / budget / capacity
U2 scope / memory / permission boundary
U3 execution / tool use
U4 classification / policy
U5 timing / coordination
U6 user meaning / trust field
U7 memory / recurrence
U8 deployment environment

A policy patch cannot repair all of these.

AI Governance

AI governance failures often appear as public controversy or safety incidents while originating in deeper structures:

appeal overload → R / Au / U3 process failure
false positives → U4 classifier + U6 meaning compression + U2 boundary issue
public distrust → U6 legitimacy field + Au issue
epistemic shaping concern → U6 / U4 / U2 interface issue
model misuse → U3 execution + U8 environment + U4 classification issue

Governance repair must match the origin.

A public statement is not enough if the failure is structural.

Governance / JGL

Governance often repairs at the wrong layer.

Examples:

legitimacy collapse repaired with messaging
boundary violation repaired with apology
justice backlog repaired with slogans
public trust collapse repaired with branding
recurrence repaired with punishment
institutional harm repaired with policy statement

Coherent governance restoration must identify whether the failure originated in:

resources
jurisdiction
due process
execution
classification
timing
legitimacy field
institutional memory
environmental pressure

Security

Security repair must reach root cause.

Examples:

breach patched at exploit level while access boundary remains broken
incident report created while recovery capacity remains absent
user lockouts increased while authentication design remains weak
surveillance increased while bypass incentives remain
policy updated while logs remain unusable

Security restoration requires boundary, access, credential, logging, user burden, and recurrence repair.

Economy

Economic failures often appear as price, debt, labor, or crisis signals while originating deeper.

Examples:

profit problem may originate in circulation failure
labor shortage may originate in boundary / dignity / compensation failure
debt crisis may originate in externalized cost or resource gatekeeping
market instability may originate in opacity or hidden leverage

Economic repair must address the origin layer:

resources
contracts
circulation
maintenance
institutional trust
externalities
time horizons

Biology / Medicine

Biological restoration often fails when symptom layer is repaired without burden origin.

Examples:

symptom suppression without membrane repair
inflammation reduction without trigger / tolerance repair
performance increase without recovery capacity
lab marker correction without recurrence reduction
acute intervention without integration

Biology requires origin-layer repair:

substrate
energy
barrier
immune timing
nervous system regulation
metabolic clearance
environmental forcing
memory / recurrence pattern

CMS / Meaning

Meaning failures may appear as confusion, contradiction, grief, shadow, symbolic dissonance, or identity instability.

But origin may differ:

symbolic confusion may originate in boundary collapse
faith crisis may originate in suppressed contradiction
archetype distortion may originate in role fusion
meaning collapse may originate in hidden debt or false narrative

Meaning repair must match origin:

interpretation
boundary
memory
truth
restoration
relational field
symbolic structure

Principles / Archetypes

Archetypal failures are often repaired symbolically when the origin is structural.

Examples:

Protector distortion repaired with affirmation while boundary control remains
Healer distortion repaired with ritual while dependency remains
Teacher distortion repaired with humility language while authority structure remains
Sovereign distortion repaired with identity claim while isolation remains

Archetype restoration must repair the layer where the distortion lives.

Relationships / Couplings

Relational symptoms often appear as conflict, silence, disconnection, resentment, or rupture.

But origins may be:

U1 resource depletion
U2 boundary violation
U3 behavior pattern
U4 misclassification
U5 timing mismatch
U6 meaning field breakdown
U7 recurrence / memory
U8 external stress

A conversation may help, but if the origin is resource, boundary, recurrence, or environment, conversation alone is incomplete.

11. Scaling Behavior

As scale increases, origin-layer mismatch becomes more common.

Why

At larger scales:

• symptoms appear far from origin
• responsibility diffuses
• dashboards flatten layers
• repair is pushed to easiest layer
• messaging substitutes for material repair
• policy substitutes for execution repair
• enforcement substitutes for recurrence repair
• coordination substitutes for coherence repair
• symbolic repair substitutes for structural repair
• delayed effects obscure causality

Scaling Pattern

Scale↑
        ↓
origin / symptom distance↑
        ↓
layer misdiagnosis risk↑
        ↓
surface repair temptation↑
        ↓
recurrence↑
        ↓
hidden debt↑

Scaling Rule Connection

Scale↑ ⇒ failure localization burden↑
Scale↑ ⇒ causal path reconstruction must strengthen
Scale↑ ⇒ origin-layer repair becomes harder
Scale↑ ⇒ pseudo-restoration risk↑
Scale↑ ⇒ auditability must increase

Therefore, high-scale repair requires stronger:

Au
Μ
Τ
ℛ
BΣ
R
FI
Θ
causal mapping
recurrence tracking
layer-specific restoration capacity

12. Canonical Examples

Example 1 — AI Refusal Patch

An AI system over-refuses legitimate requests. The team changes refusal wording but does not repair classifier logic, appeal path, or meaning restoration.

U4 wording repair
U4 / U6 / U2 origin unresolved
H remains

The repair did not reach origin.

Example 2 — Institutional Apology

An institution apologizes for a harmed-node experience but does not fix the appeal process or boundary violation that caused it.

U4 apology
U2 / U3 process failure remains
recurrence risk↑

Example 3 — Security Incident

A breach is patched at one exploit while access management and logging remain broken.

U3 patch
U2 access boundary unresolved
future breach risk↑

Example 4 — Economic Messaging

A company responds to worker depletion with morale messaging instead of workload, compensation, staffing, or maintenance repair.

U4 narrative repair
U1 resource failure remains
H↑

Example 5 — Biological Symptom Control

A symptom is reduced while the underlying barrier, tolerance, recovery, or environmental burden remains.

visible ε↓
origin-layer H unchanged
recurrence↑

Example 6 — Relationship Conversation

A couple has a good conversation about recurring conflict, but the real origin is time scarcity, financial stress, and unclear boundaries.

U6 emotional repair
U1 / U2 origin remains
recurrence returns

13. Anti-Patterns

Anti-Pattern 1 — “Repair Where the Symptom Appears”

Symptoms can appear above or away from their origin.

Anti-Pattern 2 — “Better Messaging Fixes Structural Failure”

Messaging can help interpretation; it cannot repair material or boundary failure alone.

Anti-Pattern 3 — “Policy Equals Repair”

Policy must become operational repair.

Anti-Pattern 4 — “Punish the Symptom”

Punishment rarely repairs recurrence origin.

Anti-Pattern 5 — “Apology Equals Boundary Repair”

Apology is not interface reconstitution.

Anti-Pattern 6 — “Dashboard Improvement Means Origin Repair”

Metrics can improve while origin remains active.

Anti-Pattern 7 — “Symbolic Closure Is Enough”

Symbolic closure is incomplete when structural debt remains.

14. Related Laws

This invariant connects strongly to:

• Repair Locality Law
• Hidden Debt Return Law
• Recurrence Law
• Temporal Validation Law
• Pseudo-Restoration Law
• Suppressed Error Debt Law
• Boundary Restoration Law
• Auditability Restoration Law
• Layer Misdiagnosis Law
• Restoration Debt Law
• Compression Collapse Law
• Origin-Layer Recurrence Law

15. Related Scaling Rules

Related scaling rules:

• Failure Localization Burden Growth
• Origin-Symptom Distance Growth
• Layer Misdiagnosis Risk Under Scale
• Pseudo-Restoration Risk Under Scale
• Audit Burden Growth
• Recurrence Tracking Burden Growth
• Causal Path Reconstruction Burden
• Restoration Capacity Scaling
• Messaging Substitution Risk Under Scale
• Policy Theater Risk Under Scale
• Coordination Overhead Growth
• Temporal Validation Window Growth

16. Related Gates

Relevant gates:

• Repair Locality Gate
• Restoration Validity Gate
• Origin-Layer Gate
• Boundary Integrity Gate
• FI-Gate
• Au-Actuation Gate
• Temporal Validation Gate
• Hidden Debt Gate
• Classification Validity Gate
• Reintegration Gate
• Scope Change Gate
• Post-Repair Validation Gate

Gate Logic

A repair fails the locality check when:

it addresses only the symptom layer

or when:

the origin layer remains unidentified

or when:

repair occurs above the failure origin without origin-layer intervention

or when:

recurrence continues after declared restoration

or when:

surface closure is used to avoid deeper repair

17. Related Operators

18. Machine-Readable Summary

id: UTS-INV-036
name: Repair Must Match Failure Origin
registry: UTS Invariants Registry
category: U-Layer Invariant / Restoration Invariant / Repair Locality Invariant
status: Draft-Integrated
version: 0.1

definition: >
  Repair must occur at the same or lower U-layer than the origin of failure.
  A failure may appear at one layer while originating at another. Restoration
  is coherent only when the repair reaches the layer where the failure was
  generated or the deeper layer sustaining it.

constraint: >
  A repair is incomplete if it occurs only above the layer where the failure
  originated. Restoration must address the same U-layer as the origin of the
  failure, or a lower sustaining layer, before closure can be considered
  coherent.

canonical_form:
  - "Repair must match failure origin"
  - "Repair at origin layer"
  - "Repair must occur at the same or lower U-layer than failure origin"
  - "Symptom-layer repair is not origin-layer repair"
  - "No origin-layer repair, no restoration"

protects:
  - restoration_integrity
  - hidden_debt_reduction
  - recurrence_reduction
  - auditability
  - causal_path_integrity
  - boundary_integrity
  - origin_layer_accuracy
  - long_horizon_coherence
  - repair_capacity

state_vector_effects_when_preserved:
  O: "stable_or_increasing_after_origin_repair"
  H: "decreasing_at_origin_layer"
  ε: "recurrence_decreasing"
  ι: "stable_or_decreasing"
  Au: "sufficient_for_causal_path_and_layer_localization"
  µᵢ: "preserved_through_truthful_repair"
  BΣ: "repaired_if_boundary_origin"
  K: "repair_compatible_with_failure_origin"
  R: "engaged_at_correct_layer"
  Φ: "closure_signal_not_misclassified_as_restoration"

state_vector_effects_when_violated:
  O: "decreasing_or_unrestored"
  H: "remaining_or_increasing_at_origin_layer"
  ε: "recurring_through_same_or_shifted_symptom"
  ι: "increasing_when_surface_repair_is_misclassified_as_restoration"
  Au: "insufficient_for_origin_localization"
  µᵢ: "degraded_by_false_closure"
  BΣ: "unrepaired_if_boundary_origin"
  K: "low_between_repair_and_failure_origin"
  R: "misdirected_or_symbolic_only"
  Φ: "surface_repair_or_closure_signal_misread_as_repair"

primary_u_layer: "All U-layers U0-U8"
u_layer_rule: "Repair must occur at the same or lower U-layer than failure origin"
u_layers:
  U0: "Substrate"
  U1: "Power / Budgets"
  U2: "Configuration / Boundaries"
  U3: "Execution"
  U4: "Classification / Metrics"
  U5: "Coordination / Time"
  U6: "Coherence Field"
  U7: "Memory / Recurrence"
  U8: "Environment / Forcing"

violation_signatures:
  - narrative_repair_for_material_failure
  - apology_for_boundary_violation_without_boundary_repair
  - enforcement_for_recurrence_failure
  - policy_for_substrate_failure
  - coordination_for_coherence_collapse
  - dashboard_for_execution_failure
  - symbolic_repair_for_structural_harm
  - ai_policy_patch_for_interface_failure

related_failure_modes:
  - Repair Locality Failure
  - Origin Layer Bypass
  - Pseudo-Restoration
  - Restoration Bypass
  - Premature Closure
  - Narrative Substitution
  - Policy Theater
  - Dashboard Theater
  - Symbolic Repair Substitution
  - Punishment Substitute For Repair
  - Training Theater
  - Coordination Overhead Spiral
  - Hidden Debt Accumulation
  - Recurrence Blindness
  - Auditability Collapse
  - Boundary Collapse
  - Legitimacy Debt
  - Symptom Suppression
  - Surface Stabilization Trap
  - Layer Misdiagnosis

related_restoration_arcs:
  - Origin Layer Repair
  - Failure Localization
  - Auditability Restoration
  - Causal Path Reconstruction
  - Boundary Reconstitution
  - Resource Restoration
  - Substrate Repair
  - Execution Path Repair
  - Classification Correction
  - Coordination Recalibration
  - Coherence Field Restoration
  - Memory Recurrence Repatterning
  - Environmental Forcing Adjustment
  - Restoration Capacity Rebuild
  - Temporal Validation

related_laws:
  - Repair Locality Law
  - Hidden Debt Return Law
  - Recurrence Law
  - Temporal Validation Law
  - Pseudo Restoration Law
  - Suppressed Error Debt Law
  - Boundary Restoration Law
  - Auditability Restoration Law
  - Layer Misdiagnosis Law
  - Restoration Debt Law
  - Compression Collapse Law
  - Origin Layer Recurrence Law

related_scaling_rules:
  - Failure Localization Burden Growth
  - Origin Symptom Distance Growth
  - Layer Misdiagnosis Risk Under Scale
  - Pseudo Restoration Risk Under Scale
  - Audit Burden Growth
  - Recurrence Tracking Burden Growth
  - Causal Path Reconstruction Burden
  - Restoration Capacity Scaling
  - Messaging Substitution Risk Under Scale
  - Policy Theater Risk Under Scale
  - Coordination Overhead Growth
  - Temporal Validation Window Growth

related_gates:
  - Repair Locality Gate
  - Restoration Validity Gate
  - Origin Layer Gate
  - Boundary Integrity Gate
  - FI-Gate
  - Au-Actuation Gate
  - Temporal Validation Gate
  - Hidden Debt Gate
  - Classification Validity Gate
  - Reintegration Gate
  - Scope Change Gate
  - Post Repair Validation Gate

19. Compact Canon Statement

UTS-INV-036 states that repair must match failure origin. A failure may appear at one U-layer while originating at another, and restoration is incomplete if it repairs only the symptom layer. Coherent repair must reach the same or lower U-layer than the failure origin, then validate recurrence reduction over time. Higher-layer repair can stabilize, explain, or coordinate, but it cannot fully restore a lower-layer failure by itself.

20. Short Reference Version

UTS-INV-036 — Repair Must Match Failure Origin

Repair where the failure originated,
not merely where the symptom appeared.

Core rule:

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

U4 narrative cannot repair U1 resource collapse.
U4 apology cannot repair U2 boundary violation.
U3 enforcement cannot repair U7 recurrence.
U2 policy cannot repair U0 substrate failure.

Symptom-layer repair is not origin-layer restoration.