A system can appear to repair itself while becoming less coherent. When a response improves public appearance, visible metrics, institutional comfort, or short-term stability while hidden debt, inversion, boundary damage, recurrence, or harmed-node burden increase, the process is not restoration. It is pseudo-restoration.

1. Formal Definition

The Pseudo-Restoration Law states that a repair process becomes pseudo-restoration when it improves visible success proxies while degrading coherence or preserving hidden debt.

Pseudo-restoration usually appears as repair language without restoration mechanics.

It can look like:

PR repair without debt reduction;
symptom suppression without resilience;
policy update without origin-layer repair;
compliance improvement without legitimacy;
apology without boundary restoration;
punishment without repair;
closure without hidden debt reduction;
forgiveness pressure without restored sovereignty;
safety dashboard improvement without auditability;
public calm without recurrence reduction.

Pseudo-restoration is not always deliberate deception. Often, it emerges because systems optimize visible stability, procedural completion, reputational protection, or immediate pressure reduction rather than coherence.

The central test is not whether the action looks restorative.

The test is whether O improves and H, ι, and recurrence decrease.

2. Canonical Form

Core form:

textScroll

Φ↑ while O↓ ⇒ ι↑ ⇒ pseudo-restoration

Expanded form:

textScroll

Φ↑ ∧ H unchanged/↑ ∧ ι unchanged/↑ ∧ recurrence unchanged/↑ ⇒ pseudo-restoration

Debt-preservation form:

textScroll

repair_claim + H not reduced + origin not repaired ⇒ pseudo-restoration risk↑

Restoration-valid contrast:

textScroll

ℛ_valid ⇒ H↓ + ι↓ + recurrence↓ + BΣ↑/stable + R_eff↑ + O↑/stable over Τ

Related variables:

textScroll

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

Where:

TableScroll

Variable	Meaning in this law
`Φ`	Visible success proxy; often improves during pseudo-restoration
`O`	Coherence; declines or remains brittle when repair is false
`H`	Hidden debt; remains, migrates, or increases under pseudo-restoration
`ι / Ξ`	Inversion; rises when false repair is labeled restoration
`ℛ`	Restoration action; becomes pseudo-restorative if it fails to reduce debt
`R / R_eff`	Restoration capacity; may be insufficient, misallocated, or performative
`BΣ`	Boundary integrity; remains damaged when apologies or policies replace boundary repair
`K / σ`	Slack / sovereignty; often decreases when harmed nodes carry the cost of false closure
`Au`	Auditability; often decreases when pseudo-restoration hides unresolved debt
`FI`	Feedback integrity; degraded when dissent or recurrence signals are suppressed
`recurrence`	Persists or increases because the origin pattern remains active
`𝓓`	Ring-down damping remains poor when repair is only optical
`µᵢ`	Meaning / agent integrity declines when repair claims contradict lived effects
`ε`	Observable error may decrease temporarily while debt remains
`Γ`	Classifies visible improvement as restoration, often incorrectly
`Π`	Control may reduce visible pressure while preserving the failure pattern
`Θ`	Humility / uncertainty required to avoid premature restoration claims
`Σ`	Scope of repair; often narrowed to optics instead of the true damage field
`Ψ`	Field and affected-node feedback reveal whether restoration is real
`Τ`	Time validation exposes pseudo-restoration when recurrence returns
`Λ`	Compatibility may be falsely claimed before boundary and debt repair occur
`⊗`	Coupling may continue extracting from damaged nodes under the repair narrative

3. Core Mechanism

The law unfolds when a system resolves the appearance of failure faster than it repairs the mechanics of failure.

Pseudo-restoration pathway

textScroll

failure / harm appears
→ pressure threatens legitimacy or stability
→ visible repair action is applied
→ Φ improves
→ H remains or migrates
→ ι rises because repair is claimed
→ recurrence returns
→ O declines or becomes brittle

Valid restoration pathway

textScroll

failure / harm appears
→ debt and origin layer are audited
→ restoration capacity is rebuilt
→ boundary and origin repair occur
→ H↓ and ι↓
→ recurrence↓
→ O stabilizes or improves over Τ

The core mechanism is:

textScroll

visible repair can reduce pressure while preserving the failure geometry

Detailed mechanism:

A failure becomes visible.

The system faces pressure from error, harm, exposure, legitimacy loss, conflict, symptoms, breach, complaint, or instability.

The system selects a visible repair pathway.

It chooses an action that can be seen, measured, announced, enforced, or documented quickly.

The visible success proxy improves.

Complaints may decrease, metrics may improve, dashboards may stabilize, public attention may move on, or formal compliance may rise.

The origin-layer debt remains active.

The damaged boundary, depleted capacity, invalid contract, recurrence memory, hidden coercion, or degraded auditability remains unresolved.

The repair claim creates inversion.

Because the system now labels itself repaired, future feedback is harder to hear. The repair narrative shields the remaining debt.

Recurrence reveals the false repair.

The same failure returns, migrates, or appears as delayed collapse, legitimacy shock, chronic instability, or basin self-defense.

4. When This Law Applies

This law applies when a system claims restoration while coherence, debt, boundaries, recurrence, or auditability do not improve.

It is especially important when:

public relations substitutes for repair;
visible symptoms are suppressed without resilience;
policy language changes without origin-layer repair;
compliance improves while legitimacy declines;
apology occurs without boundary restoration;
punishment occurs without repair;
forgiveness is requested before restoration;
closure is claimed without hidden debt reduction;
visible metrics improve while auditability decreases;
the harmed node carries more burden after the repair;
the system becomes harder to question after claiming restoration;
recurrence continues after a “successful” repair;
scaling resumes after shallow repair;
a basin preserves itself by adopting restoration language.

The law applies strongly when:

textScroll

repair claim improves Φ while H, ι, recurrence, or boundary damage persist

or when:

textScroll

the restoration narrative becomes a shield against further audit

Typical domains:

TableScroll

Domain	Pseudo-Restoration Expression
AI systems	Safety metrics improve while auditability, appeals, recurrence, or user agency degrade.
Security	Incidents are closed while root access paths, logging gaps, persistence, or boundary failures remain.
Institutions	Apology, policy, or discipline improves optics while harmed-node burden and legitimacy debt remain.
Medicine / biology	Symptoms are suppressed while ring-down, recurrence, tolerance, or restoration capacity worsens.
Economy	Settlement, relief, or market optimism appears while extraction, exit cost, or circulation debt remain.
Governance	Public statements or procedural reforms calm pressure while consequence, repair, and prevention remain absent.
Culture	Symbolic acknowledgement occurs while the basin, incentive field, and normalization shield remain unchanged.
Restoration	Any repair action that improves appearance while preserving debt is pseudo-restoration.

5. When This Law Does Not Apply

This law should not be used to reject visible repair actions merely because they are visible.

A visible action can be part of real restoration when it is connected to debt reduction, origin-layer repair, recurrence reduction, auditability, and time validation.

False-positive cases:

TableScroll

Case	Why it is not pseudo-restoration
A public statement opens auditability and commits to measurable repair	Visibility supports repair rather than replacing it
A symptom is reduced while deeper restoration capacity is rebuilt	Symptom relief supports, but does not claim to complete, restoration
A policy update includes boundary repair, enforcement, audit, and affected-node restoration	Procedure is connected to real repair
A compliance improvement reduces recurrence and increases legitimacy	Compliance reflects actual coherence gain
An apology is paired with material repair, boundary redesign, and prevention	Apology becomes one part of restoration

Important distinction:

Visible repair is not the problem. Visible repair becomes pseudo-restoration when it substitutes for coherence repair.

6. Diagnostic Signature

Canonical diagnostic:

textScroll

Φ↑ while O↓ ⇒ ι↑ ⇒ pseudo-restoration

Warning signature:

textScroll

repair announced
Φ↑
H unchanged/↑
Au↓ or selective
BΣ unchanged/damaged
recurrence unchanged/↑
O brittle or ↓
⇒ pseudo-restoration

Common indicators:

TableScroll

Diagnostic	Expected movement	Interpretation
`Φ`	↑	Visible success proxy improves
`O`	↓ / brittle / unstable	Coherence does not improve or becomes fragile
`H`	unchanged / ↑	Hidden debt remains or increases
`ι / Ξ`	↑	Repair claim becomes inversion
`Au`	↓ / selective	Auditability narrows after repair claim
`FI`	degraded	Feedback challenging the repair is filtered or dismissed
`BΣ`	unchanged / ↓	Boundaries remain damaged
`R_eff`	insufficient / performative	Restoration capacity does not match repair load
`K / σ`	↓	Slack and sovereignty decline, often for harmed nodes
`recurrence`	unchanged / ↑	Failure pattern persists
`𝓓`	↓ / unchanged	Ring-down does not improve
`µᵢ`	↓	Meaning integrity degrades when claims contradict effects
`ε`	↓ temporarily	Observable error may improve before recurrence returns

Additional diagnostics:

TableScroll

Diagnostic	Use
Pseudo-Restoration Risk	Detects optics improvement without coherence repair
Restoration Validity	Tests whether repair reduces debt
Hidden Debt	Detects stored cost preserved by repair narrative
Inversion	Detects false repair claims
Coherence Trajectory	Shows whether `O` actually improves
Visible Success Proxy	Tracks misleading improvement
Recurrence	Reveals whether failure geometry remains
Ring-Down	Tests whether recovery quality improves
Boundary Integrity	Detects unrepaired boundary damage
Effective Auditability	Tests whether repair remains inspectable
Legitimacy Baseline	Detects whether authority coherence improves or decays
Temporal Proof	Exposes pseudo-restoration over time

7. Failure Pattern

If ignored, this law allows false repair to stabilize the failure pattern.

General failure pathway:

textScroll

failure visible
→ repair optics selected
→ Φ improves
→ restoration claimed
→ H remains
→ ι rises
→ audit narrows
→ recurrence returns
→ legitimacy shock / delayed collapse

Common failure modes:

Pseudo-Restoration — repair is claimed while coherence does not improve.
Restoration Theater — visible performance replaces restoration mechanics.
Optics Repair — appearance improves while debt remains.
PR Repair Without Debt Reduction — communication substitutes for repair.
Symptom Suppression Without Resilience — symptoms improve while recovery quality declines.
Policy Update Without Origin-Layer Repair — rules change without repairing the source layer.
Compliance Improvement Without Legitimacy — formal success rises while trust and coherence decline.
Apology Without Boundary Restoration — emotional or symbolic repair replaces membrane repair.
Public Statement Substitution — statement becomes closure instead of repair routing.
Quiet Minimization — conflict is reduced by hiding debt.
Hidden Debt Persistence — stored cost remains active.
Inversion Persistence — repair language protects the failure pattern.
Delayed Collapse — unresolved debt returns under future load.
Legitimacy Shock — authority loses coherence when false repair is exposed.

Compact failure signature:

textScroll

Φ↑ + H↑/unchanged + ι↑ + recurrence↑ ⇒ pseudo-restoration basin

8. Restoration Implications

Restoration requires interrupting the false repair loop and returning to debt, origin, boundary, recurrence, and time validation.

The first restoration question is not:

textScroll

Did the repair look successful?

The first restoration question is:

textScroll

Did hidden debt, inversion, boundary damage, and recurrence actually decrease?

Restoration priorities:

Suspend the restoration claim until verified.
Separate visible proxy improvement from coherence improvement.
Audit hidden debt after the repair action.
Audit inversion created by the repair narrative.
Trace whether origin-layer repair occurred.
Verify whether boundaries and capacity improved.
Check whether harmed-node burden decreased.
Check whether auditability improved or narrowed.
Measure recurrence and ring-down over time.
Reopen repair if debt persists.

Relevant restoration arcs:

TableScroll

Restoration Arc	Why it applies
Pseudo-Restoration Detection	Identifies false repair and separates optics from coherence
Hidden Debt Reduction	Tests whether repair actually reduced stored burden
Origin-Layer Repair	Prevents surface repair from substituting for source repair
Boundary Reconstitution	Restores membranes damaged by failure or false repair
Auditability Restoration	Prevents repair claims from narrowing inspection
Restoration Capacity Rebuild	Ensures repair capacity can meet repair load
Slack Regeneration	Restores harmed-node capacity and sovereignty
Controlled Decoupling	Prevents ongoing coupling from generating more debt
Temporal Validation	Exposes pseudo-restoration through recurrence testing
Recurrence Reduction	Confirms the failure pattern has weakened
Closure Stack Completion	Prevents closure from replacing restoration

Minimal restoration sequence:

textScroll

pause restoration claim
→ audit Φ vs O
→ audit H / ι / BΣ / recurrence
→ restore auditability
→ repair origin layer
→ reduce debt and inversion
→ validate over Τ

Temporal validation requirement:

textScroll

Φ improvement not sufficient
H↓
ι↓
BΣ stable or rising
R_eff↑
K / σ↑
recurrence↓
𝓓↑
Au↑
FI intact
µᵢ stable
O stable or rising

9. Design Rule

Do not allow visible repair proxies to substitute for coherence repair.

Operational design requirements:

Track Φ separately from O.
Require debt-reduction evidence before restoration claims.
Require inversion-reduction evidence before closure.
Preserve auditability after repair announcements.
Include affected-node feedback in restoration validation.
Test recurrence after the repair action.
Verify origin-layer repair occurred.
Track whether harmed-node burden decreased.
Distinguish public calm from coherence.
Distinguish compliance from legitimacy.
Distinguish symptom relief from recovery.
Distinguish apology from boundary repair.

Avoid:

PR repair without debt reduction;
symptom suppression without resilience;
policy update without origin-layer repair;
compliance improvement without legitimacy;
apology without boundary restoration;
punishment without repair;
forced forgiveness;
closure through silence;
dashboard success without field validation;
restricting feedback after claiming repair;
scaling after optics improvement alone;
treating reduced conflict as proof of restoration.

10. Cross-Scale Expressions

TableScroll

Scale / Layer	Expression of the Law
U0 — Substrate	Substrate harm is hidden by symptom management or surface performance.
U1 — Energy / capacity	Depleted capacity is reframed as restored because output temporarily improves.
U2 — Boundary / interface	Boundary damage remains after apology, policy, or symbolic repair.
U3 — Process / execution	Tickets close and workflows update while root execution failure remains.
U4 — Classification / claim	The system classifies itself as repaired despite unresolved debt.
U5 — Time / delay	Delay hides recurrence until after restoration has been claimed.
U6 — Field effect	Affected-node outcomes reveal that repair did not restore coherence.
U7 — Recurrence / memory	The same pattern remains encoded and returns under load.
U8 — Environment / forcing	Environmental pressure continues generating the failure despite visible repair.

11. Examples

Example A — PR Repair Without Debt Reduction

Scenario:

An organization responds to harm with a polished public statement, updated language, and visible concern, but no material repair, boundary redesign, consequence, audit, or recurrence prevention occurs.

Law expression:

textScroll

Φ_public↑ ∧ H unchanged ∧ BΣ unchanged ⇒ pseudo-restoration

Interpretation:

The organization appears responsive, but the debt remains. The statement may become inversion if it shields the system from further accountability.

Example B — Symptom Suppression Without Recovery

Scenario:

A biological symptom decreases after an intervention, but the system’s tolerance remains low, ring-down remains poor, recurrence remains high, and energy remains depleted.

Law expression:

textScroll

ε_symptom↓ ∧ 𝓓 unchanged/↓ ∧ recurrence↑ ⇒ pseudo-recovery

Interpretation:

Symptom relief may be useful, but it is not restoration if resilience and recovery quality do not improve.

Example C — AI Safety Dashboard Improvement

Scenario:

An AI platform reports improved safety numbers, but user appeals fail, auditability decreases, classifier recurrence persists, and users cannot understand or challenge decisions.

Law expression:

textScroll

Φ_safety↑ ∧ Au↓ ∧ recurrence↑ ⇒ pseudo-restoration

Interpretation:

The dashboard improved, but the underlying safety state may have degraded because auditability and recurrence worsened.

Example D — Policy Update Without Origin Repair

Scenario:

An institution updates policy after a boundary violation, but access rights, reporting pathways, consent structures, and enforcement realities remain unchanged.

Law expression:

textScroll

policy_update(U4) without BΣ repair(U2) ⇒ pseudo-restoration

Interpretation:

The policy update is not restoration unless it changes the layer where the failure originated.

Example E — Compliance Without Legitimacy

Scenario:

A governance system increases reporting, documentation, and procedural compliance, but affected participants experience lower agency, lower trust, higher burden, and no meaningful repair.

Law expression:

textScroll

Φ_compliance↑ ∧ L↓ ∧ H↑ ⇒ pseudo-restoration

Interpretation:

Compliance can rise while legitimacy falls. Formal order is not proof of restoration.

Example F — Apology Without Boundary Restoration

Scenario:

A person or institution apologizes for a boundary violation while preserving the same access, pressure, dependency, or recurrence pathway.

Law expression:

textScroll

apology(U4) + BΣ unchanged(U2) ⇒ pseudo-restoration risk↑

Interpretation:

The apology may matter, but it cannot substitute for boundary repair.

12. Relationship to Nearby Laws

TableScroll

Related Law	Relationship
LAW-006 — Time Validation Law	Pseudo-restoration is exposed over time
LAW-007 — Ring-Down Truth Law	False repair does not improve damping
LAW-008 — Recurrence Validation Law	Recurrence reveals preserved failure geometry
LAW-009 — U4 / U6 Truth Law	U4 repair claims require field validation
LAW-010 — Hidden Debt Accumulation Law	Pseudo-restoration preserves or increases debt
LAW-011 — Hidden Debt Return Law	Hidden debt returns after false repair
LAW-012 — Error Lag Law	Visible errors may fall before false repair fails
LAW-013 — Auditability-Debt Law	Pseudo-restoration often narrows auditability
LAW-015 — Suppressed Auditability Debt Law	Hiding unresolved repair creates more debt
LAW-016 — Inversion Formation Law	Pseudo-restoration is a major inversion pattern
LAW-030 — Slack Sovereignty Law	False repair often transfers burden to harmed nodes
LAW-045 — Force Debt Law	Forceful closure can create pseudo-restoration
LAW-050 — Control-Restoration Separation Law	Pseudo-restoration often confuses control with repair
LAW-052 — Stability Proof Law	False repair fails perturbation testing
LAW-053 — Wrong-Solution Basin Law	Pseudo-restoration can stabilize the wrong basin
LAW-061 — Restoration Sequencing Law	Wrong sequence can produce false repair
LAW-062 — Restoration Is Not the Inverse of Failure Law	Reversal without repair can become pseudo-restoration
LAW-063 — Origin-Layer Repair Law	Repair above the origin layer often becomes pseudo-restoration
LAW-064 — Restoration Debt Reduction Law	L064 defines the proof standard; L065 defines the failure mode
LAW-066 — Restoration Capacity Sufficiency Law	Insufficient capacity can turn repair attempts into pseudo-restoration
LAW-067 — Temporal Proof Law	Pseudo-restoration lacks durable proof
LAW-068 — Boundary-First Restoration Law	Boundary damage must be repaired before restoration claims
LAW-069 — Closure Stack Law	Closure without full stack becomes pseudo-restoration
LAW-071 — No Forced Forgiveness Law	Forced forgiveness is a pseudo-restoration pathway
LAW-072 — Quiet Minimization Debt Law	Quiet minimization is a common pseudo-restoration method
LAW-073 — Restoration Before Scaling Law	Scaling pseudo-restoration amplifies hidden debt
LAW-075 — Capacity Before Demand Law	False repair often demands capacity from damaged nodes
LAW-076 — Supersession Threshold Law	Repeated pseudo-restoration may indicate non-restorability
LAW-077 — Pseudo-Coherent Basin Law	Pseudo-restoration helps maintain pseudo-coherent basins
LAW-078 — Pseudo-Coherent Basin Export Law	False repair often exports debt elsewhere
LAW-079 — Local Stability Export Law	Local calm after false repair may depend on externalized burden
LAW-082 — Basin Supersession Law	Persistent pseudo-restoration may require basin redesign
LAW-083 — Normalization Shield Law	Normalized false repair escapes scrutiny

Aliases folded into this law:

Pseudo-Restoration Law
False Restoration Law
Optics Repair Law
Surface Restoration Law
Restoration Theater Law
Coherence-Degrading Repair Law
Apparent Repair Inversion Law

Deduplication note:

This law should remain the root false-restoration law. LAW-064 defines the valid restoration proof condition, LAW-063 defines repair-depth failure, LAW-069 defines closure stack failure, LAW-072 defines quiet minimization as debt issuance, and LAW-077 through LAW-079 describe basin-level pseudo-coherence patterns that pseudo-restoration often preserves.

13. Operator Mapping

TableScroll

Operator	Role in this law
`Γ`	Misclassifies visible improvement as restoration, or correctly distinguishes repair from optics
`Π`	Controls visible pressure and may improve proxies without repairing coherence
`Ξ`	Captures the inversion created when false repair is named restoration
`⊗`	Coupling may continue extracting or destabilizing while repair is claimed
`ℛ`	True restoration is absent, incomplete, or performative in pseudo-restoration
`Τ`	Time exposes whether the repair was durable
`Θ`	Prevents premature certainty and restoration overclaiming
`Σ`	Defines whether repair scope includes real debt or only optics
`Ψ`	Field and affected-node feedback reveal false repair
`Λ`	Compatibility may be falsely claimed before debt and boundary repair

Coherent operator sequence:

textScroll

Γ(distinguish Φ from O) → Θ(repair uncertainty) → Σ(scope real debt) → Au/FI(trace effects) → ℛ(reduce H + ι) → Ψ(validate field effects) → Τ(validate recurrence↓ + O stable/↑)

Inverted operator sequence:

textScroll

failure visible → Π(reduce visible pressure) → Φ↑ → Γ(restoration claimed) → Au narrows → H persists → Ξ / ι↑ → recurrence → pseudo-restoration

14. Machine-Readable Summary

yamlScroll

id: "LAW-065"
name: "Pseudo-Restoration Law"
type: "law"
status: "draft"
family:
  - "Restoration Laws"
summary: "A repair process that improves optics while degrading coherence is pseudo-restoration."
canonical_statement: "A repair process that improves optics while degrading coherence is pseudo-restoration."
core_form: "Φ↑ while O↓ ⇒ ι↑ ⇒ pseudo-restoration"
expanded_form: "Φ↑ ∧ H unchanged/↑ ∧ ι unchanged/↑ ∧ recurrence unchanged/↑ ⇒ pseudo-restoration"
debt_preservation_form: "repair_claim + H not reduced + origin not repaired ⇒ pseudo-restoration risk↑"
restoration_validity_form: "ℛ_valid ⇒ H↓ + ι↓ + recurrence↓ + BΣ↑/stable + R_eff↑ + O↑/stable over Τ"
variables:
  primary:
    - "Φ"
    - "O"
    - "H"
    - "ι"
    - "Ξ"
    - "ℛ"
    - "R"
    - "R_eff"
    - "BΣ"
    - "K"
    - "σ"
  secondary:
    - "ε"
    - "Au"
    - "FI"
    - "µᵢ"
    - "Λ"
    - "⊗"
    - "Γ"
    - "Π"
    - "Θ"
    - "Σ"
    - "Ψ"
    - "Τ"
diagnostics:
  - "Pseudo-Restoration Risk"
  - "Restoration Validity"
  - "Hidden Debt"
  - "Inversion"
  - "Coherence Trajectory"
  - "Visible Success Proxy"
  - "Recurrence"
  - "Ring-Down"
  - "Boundary Integrity"
  - "Restoration Capacity"
  - "Effective Auditability"
  - "Slack"
  - "Legitimacy Baseline"
  - "Temporal Proof"
failure_modes:
  - "Pseudo-Restoration"
  - "Restoration Theater"
  - "Optics Repair"
  - "PR Repair Without Debt Reduction"
  - "Symptom Suppression Without Resilience"
  - "Policy Update Without Origin-Layer Repair"
  - "Compliance Improvement Without Legitimacy"
  - "Apology Without Boundary Restoration"
  - "Public Statement Substitution"
  - "Quiet Minimization"
  - "Hidden Debt Persistence"
  - "Inversion Persistence"
  - "Delayed Collapse"
  - "Legitimacy Shock"
restoration_arcs:
  - "Pseudo-Restoration Detection"
  - "Hidden Debt Reduction"
  - "Origin-Layer Repair"
  - "Boundary Reconstitution"
  - "Auditability Restoration"
  - "Restoration Capacity Rebuild"
  - "Slack Regeneration"
  - "Controlled Decoupling"
  - "Temporal Validation"
  - "Recurrence Reduction"
  - "Closure Stack Completion"
related_laws:
  - "LAW-006"
  - "LAW-007"
  - "LAW-008"
  - "LAW-009"
  - "LAW-010"
  - "LAW-011"
  - "LAW-012"
  - "LAW-013"
  - "LAW-015"
  - "LAW-016"
  - "LAW-030"
  - "LAW-045"
  - "LAW-050"
  - "LAW-052"
  - "LAW-053"
  - "LAW-061"
  - "LAW-062"
  - "LAW-063"
  - "LAW-064"
  - "LAW-066"
  - "LAW-067"
  - "LAW-068"
  - "LAW-069"
  - "LAW-071"
  - "LAW-072"
  - "LAW-073"
  - "LAW-075"
  - "LAW-076"
  - "LAW-077"
  - "LAW-078"
  - "LAW-079"
  - "LAW-082"
  - "LAW-083"
related_invariants:
  - "INV-001"
  - "INV-004"
  - "INV-006"
  - "INV-077"
  - "INV-078"
  - "INV-080"
operator_sequence:
  coherent:
    - "Γ distinguish Φ from O"
    - "Θ repair uncertainty"
    - "Σ scope real debt"
    - "Au/FI trace effects"
    - "ℛ reduce H + ι"
    - "Ψ validate field effects"
    - "Τ validate recurrence↓ + O stable/↑"
  inverted:
    - "failure visible"
    - "Π reduce visible pressure"
    - "Φ↑"
    - "Γ restoration claimed"
    - "Au narrows"
    - "H persists"
    - "Ξ / ι↑"
    - "recurrence"
    - "pseudo-restoration"
aliases:
  - "Pseudo-Restoration Law"
  - "False Restoration Law"
  - "Optics Repair Law"
  - "Surface Restoration Law"
  - "Restoration Theater Law"
  - "Coherence-Degrading Repair Law"
  - "Apparent Repair Inversion Law"
deduplication_note: "Root false-restoration law. LAW-064 defines the valid restoration proof condition, LAW-063 defines repair-depth failure, LAW-069 defines closure stack failure, LAW-072 defines quiet minimization as debt issuance, and LAW-077 through LAW-079 describe basin-level pseudo-coherence patterns that pseudo-restoration often preserves."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-065 — Pseudo-Restoration Law

A repair process that improves optics while degrading coherence is pseudo-restoration.

Core form:

textScroll

Φ↑ while O↓ ⇒ ι↑ ⇒ pseudo-restoration

Expanded form:

textScroll

Φ↑ ∧ H unchanged/↑ ∧ ι unchanged/↑ ∧ recurrence unchanged/↑ ⇒ pseudo-restoration

Plain meaning:

A system can appear to repair itself while becoming less coherent. When public appearance, visible metrics, institutional comfort, or short-term stability improve while hidden debt, inversion, boundary damage, recurrence, or harmed-node burden increase, the process is not restoration.

Debt-preservation form:

textScroll

repair_claim + H not reduced + origin not repaired ⇒ pseudo-restoration risk↑

Restoration validity contrast:

textScroll

ℛ_valid ⇒ H↓ + ι↓ + recurrence↓ + BΣ↑/stable + R_eff↑ + O↑/stable over Τ

Primary variables:

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

Diagnostic signature:

Visible repair is announced and success proxies improve, but hidden debt, inversion, boundary damage, recurrence, poor ring-down, or harmed-node burden remain while auditability narrows.

Failure risk:

Restoration theater, optics repair, PR repair without debt reduction, symptom suppression without resilience, policy update without origin-layer repair, compliance improvement without legitimacy, apology without boundary restoration, quiet minimization, delayed collapse.

Restoration priority:

Separate visible proxy improvement from coherence improvement, audit hidden debt and inversion, restore auditability, repair the origin layer, reduce recurrence, and time-validate that O remains stable or improves.

LAW-064 — Restoration Debt Reduction Law

Registry

LAW-066 — Restoration Capacity Sufficiency Law