Archive registry entry

LAW-105 — Repair Before Enforcement Law

Archive registry entry

LAW-105 — Repair Before Enforcement Law

Enforcement without repair accumulates hidden debt; restriction may be needed for safety, but enforcement alone does not restore coherence.

draftid: LAW-105version: 1.0.0updated: 2026-06-17

Archive Progress

This section can be read now; registry depth and cross-references are still being strengthened.

Foundation

Online

The section has a stable overview route and basic reader context.

Technical Layer

Online

A deeper technical overview is available.

Registry

Current

171 registry entries are available.

Cross-links

Curating

Related concepts are being connected conservatively for accuracy.

Jump Through This Page

LAW-104 — Justice Logistics Law

Registry

LAW-106 — Exposure Legibility Law

0. Plain Statement

Enforcement without repair accumulates hidden debt.

Plain-language version:

Restriction may be needed for safety.

Containment may be needed to stop harm.

Enforcement may be needed to preserve boundaries.

But enforcement alone does not restore coherence.

If a system enforces, restricts, punishes, removes, bans, disciplines, detains, denies, suppresses, or controls without repairing the damage, changing recurrence conditions, and restoring affected-node coherence, hidden debt continues to accumulate.

1. Formal Definition

The Repair Before Enforcement Law states that enforcement actions are coherence-valid only when they are connected to repair, restoration, prevention, boundary clarification, and legitimacy repair.

Enforcement can include:

restriction;
containment;
removal;
suspension;
punishment;
sanction;
denial;
refusal;
moderation;
policing;
prosecution;
discipline;
surveillance-triggered action;
boundary closure;
access revocation;
emergency override;
forced decoupling;
coercive control.

These actions may be necessary when harm is active, boundaries are violated, safety is at risk, or further coupling would increase debt.

However, enforcement is not repair.

Enforcement can stop a current pathway of harm, but it does not automatically:

repair harmed-node coherence;
restore agency;
reduce hidden debt;
restore legitimacy;
correct origin-layer causes;
improve recurrence conditions;
rebuild boundaries;
restore trust;
process affected feedback;
convert exposure into restoration;
prevent future harm.

Canonical form:

textScroll

enforcement - ℛ ⇒ H↑

Restriction may be needed for safety, but enforcement alone does not restore coherence.

2. Canonical Form

Core form:

textScroll

enforcement without repair accumulates hidden debt

Canonical form:

textScroll

enforcement - ℛ ⇒ H↑

Containment distinction:

textScroll

containment may stop harm; repair restores coherence

Safety-valid form:

textScroll

active harm + BΣ failure ⇒ containment may be required before repair

Failure form:

textScroll

restriction + no repair + recurrence unchanged ⇒ L↓ + H↑

Restoration-valid contrast:

textScroll

enforcement valid when scoped, auditable, repair-linked, recurrence-reducing, and time-bounded where possible

Related variables:

textScroll

O, H, ε, ι, Au, Au_eff, µᵢ, BΣ, K, σ, R, R_eff, Φ, Λ, ⊗, Γ, Π, Ξ, ℛ, Θ, Σ, Ψ, Τ, FI, MS, L, enforcement_load, containment_need, repair_need, restriction_debt, force_debt, recurrence_risk, harmed_node_O, origin_layer_cause, prevention_integrity

Where:

TableScroll

Variable	Meaning in this law
`enforcement_load`	Burden created by restriction, punishment, discipline, denial, or coercive control
`containment_need`	Degree to which active harm requires immediate restriction before deeper repair
`repair_need`	Restoration demand created by harm, violation, recurrence, or enforcement side effects
`restriction_debt`	Hidden debt created when restriction substitutes for repair or continues beyond need
`force_debt`	Debt created by coercion, even when coercion is necessary for containment
`recurrence_risk`	Likelihood harm repeats because origin conditions are not repaired
`harmed_node_O`	Coherence of harmed or affected nodes after enforcement and repair
`origin_layer_cause`	Layer at which recurrence conditions were generated
`prevention_integrity`	Whether enforcement is connected to recurrence prevention
`ℛ`	Repair / restoration action required to reduce debt
`R / R_eff`	Restoration capacity required to perform actual repair
`BΣ`	Boundary integrity; enforcement may protect or overharden boundaries
`Au / Au_eff`	Auditability of enforcement reasons, scope, effects, and repair obligations
`FI`	Feedback integrity; affected feedback must be able to correct enforcement and repair design
`MS`	Moral / meaning symmetry; enforcement must not be asymmetrical or selectively applied
`L`	Legitimacy; decays when enforcement is unpaired with repair
`O`	Coherence; enforcement is valid only when it preserves or restores coherence over time
`H`	Hidden debt; rises when enforcement substitutes for restoration
`ι / Ξ`	Inversion when safety, justice, or repair language justifies control without restoration
`Φ`	Visible compliance, order, or closure; not sufficient proof of repair
`Λ`	Compatibility between enforcement, repair, and whole-system coherence
`Γ`	Classifies harm, containment need, repair need, enforcement scope, and recurrence conditions
`Π`	Operationalizes enforcement, repair sequence, appeals, review, and prevention architecture
`Θ`	Humility preventing punitive certainty, control inflation, and enforcement pride
`Σ`	Scope, duration, and domain of enforcement and repair
`Ψ`	Field and affected-node feedback validating enforcement and repair effects
`Τ`	Time validation of recurrence reduction and legitimacy stabilization

3. Core Mechanism

The law unfolds because stopping a harm pathway is not the same as repairing the damage or changing recurrence conditions.

Coherent containment-to-repair pathway

textScroll

active harm or boundary failure appears
→ containment is scoped if needed
→ harm pathway is interrupted
→ auditability is preserved
→ repair need is mapped
→ restoration is performed
→ recurrence conditions change
→ enforcement can reduce or terminate
→ legitimacy stabilizes over time

Enforcement substitution pathway

textScroll

harm appears
→ enforcement occurs
→ visible order returns
→ repair is skipped or delayed
→ origin conditions remain
→ recurrence continues
→ hidden debt accumulates
→ legitimacy decays

The core mechanism is:

textScroll

enforcement can interrupt; repair must restore

Detailed mechanism:

A system detects harm, violation, or risk.

Boundaries may be failing. A node may be unsafe. A coupling may need interruption.

Containment may be required.

Some cases require immediate restriction or decoupling to stop ongoing harm.

Enforcement creates its own load and debt.

Even necessary restriction imposes costs and must be scoped, audited, reviewed, and connected to repair.

Repair need remains after enforcement.

Harmed nodes still need restoration. Origin conditions still need correction. Recurrence conditions still need redesign.

If repair follows enforcement, coherence can recover.

Enforcement becomes a phase in restoration sequencing.

If enforcement replaces repair, hidden debt grows.

The system may appear ordered while the underlying conditions persist.

Time validates the sequence.

Enforcement is coherent only if recurrence falls, harmed-node coherence rises, restriction debt decreases, and legitimacy stabilizes over time.

4. When This Law Applies

This law applies whenever a system uses restriction, punishment, discipline, denial, refusal, ban, removal, moderation, policing, prosecution, suspension, emergency power, coercive control, forced decoupling, or enforcement to respond to harm, risk, violation, conflict, error, or disorder.

It is especially important when:

enforcement is treated as justice;
safety is treated as restriction only;
visible order is treated as repair;
punishment replaces restoration;
moderation lacks appeal or repair;
restriction continues after active harm stops;
emergency power persists without sunset;
policing increases without repair capacity;
AI systems refuse, ban, downrank, classify, or restrict without explanation or restoration;
institutions discipline an individual but leave systemic causes intact;
enforcement creates new harmed nodes;
harmed-node repair is delayed or ignored;
recurrence continues despite enforcement;
control capacity scales faster than restoration capacity.

The law applies strongly when:

textScroll

enforcement action is not connected to restoration

or when:

textScroll

restriction is being mistaken for coherence

Typical domains:

TableScroll

Domain	Repair Before Enforcement Expression
AI systems	AI refusals, bans, moderation, account actions, and automated restrictions require explanation, appeal, correction, and restoration pathways.
Security	Containment must be followed by remediation, clearance, boundary repair, and recurrence prevention.
Institutions	Discipline must be paired with harmed-node repair and structural prevention.
Medicine / biology	Symptom suppression or restriction does not equal healing if root restoration is absent.
Economy	Penalties, sanctions, or account closures do not repair extraction, coercion, or circulation damage alone.
Governance	Enforcement without repair creates legitimacy debt and recurrence.
Culture	Social punishment without restoration can become exile, scapegoating, or recurrence displacement.
Restoration	Repair must be designed after containment; otherwise closure remains pseudo-restoration.

5. When This Law Does Not Apply

This law should not be used to prevent urgent containment when active harm is occurring.

Sometimes enforcement must come before repair in time.

The law says repair must not be omitted.

False-positive cases:

TableScroll

Case	Why enforcement may be coherent
Active harm is ongoing	Immediate containment may be necessary
Boundary violation is escalating	Restriction may protect harmed nodes
A node is unsafe to couple with	Controlled decoupling may be valid
Evidence could be destroyed	Temporary restriction may preserve auditability
Emergency risk is real	Emergency power may be valid if scoped, sunsetted, audited, and repair-bound
A system lacks immediate repair capacity	Temporary containment may be needed while capacity is built
A refusal prevents further harm	Refusal can be coherent when connected to restoration or prevention

Important distinction:

Containment may precede repair; containment must not replace repair.

6. Diagnostic Signature

Canonical diagnostic:

textScroll

enforcement - ℛ ⇒ H↑

Warning signature:

textScroll

enforcement↑
visible order↑
repair↓
appeal / feedback↓
recurrence unchanged
restriction duration↑
legitimacy↓
⇒ enforcement substitution

Common indicators:

TableScroll

Diagnostic	Expected movement	Interpretation
`containment_need`	high during active harm	Restriction may be necessary
`enforcement_load`	↑ when restriction is used	Enforcement creates operational and legitimacy load
`repair_need`	remains active	Repair demand does not disappear after enforcement
`ℛ`	must ↑ after containment	Restoration should follow restriction
`R_eff`	must be sufficient	Repair requires actual capacity
`restriction_debt`	should ↓ over time	Restrictions should not persist beyond need without review
`force_debt`	should be acknowledged and repaired where possible	Coercion creates debt even when necessary
`recurrence_risk`	should ↓	Enforcement is valid only if recurrence conditions change
`harmed_node_O`	should ↑	Harmed-node coherence must improve
`BΣ`	should stabilize	Boundaries should become clearer, not merely harsher
`Au`	must remain intact	Enforcement must be traceable and reviewable
`FI`	must remain intact	Feedback and appeal must be able to correct action
`MS`	must remain intact	Comparable cases require comparable enforcement and repair
`L`	↑ if valid, ↓ if not	Legitimacy follows repair-linked enforcement
`Φ`	not sufficient	Order, compliance, or closure is not proof
`Τ`	required	Time validates repair and recurrence reduction

Additional diagnostics:

TableScroll

Diagnostic	Use
Repair Before Enforcement	Tests whether restriction is connected to restoration
Enforcement Load	Measures burden imposed by restriction
Repair Sufficiency	Tests whether repair matches harm
Containment Necessity	Distinguishes safety containment from punitive control
Restriction Debt	Detects hidden debt from ongoing restriction
Force Debt	Tracks debt created by coercive action
Recurrence Risk	Detects unchanged origin conditions
Pseudo-Restoration Risk	Detects enforcement used as closure
Temporal Proof	Confirms recurrence reduction and legitimacy over time

7. Failure Pattern

If ignored, this law allows enforcement to appear successful while coherence decays.

General failure pathway:

textScroll

harm / disorder appears
→ enforcement interrupts visible issue
→ order or compliance returns
→ repair is omitted
→ recurrence conditions remain
→ restriction debt and hidden debt accumulate
→ legitimacy decays

Common failure modes:

Enforcement Substitution — enforcement replaces repair.
Punishment Substitution — punishment is mistaken for justice or restoration.
Restriction Debt — ongoing restriction creates hidden debt.
Control-Restoration Confusion — control is treated as coherence.
Repair Deferral — repair is postponed indefinitely after enforcement.
Containment Drift — temporary containment becomes ordinary control.
Permanent Restriction — restriction persists after active harm or risk changes.
Compliance Theater — visible compliance hides unresolved debt.
Pseudo-Safety — safety is claimed while recurrence conditions remain.
Pseudo-Justice — enforcement is framed as justice without repair.
Legitimacy Debt — trust decays because enforcement cannot survive audit.
Recurrence Persistence — harm repeats because origin conditions remain.
Retaliatory Enforcement — enforcement becomes revenge or dominance.
Audit Suppression — enforcement reasons, scope, or effects cannot be inspected.
Hidden Debt Migration — debt moves to harmed nodes, restricted nodes, operators, or future systems.

Compact failure signature:

textScroll

enforcement↑ + ℛ↓ + recurrence unchanged ⇒ H↑ + L↓

8. Restoration Implications

Restoration requires connecting enforcement to repair, appeal, review, prevention, and decoupling where appropriate.

The first restoration question is not:

textScroll

Was the rule enforced?

The first restoration question is:

textScroll

Did enforcement stop harm, preserve auditability, support repair, reduce recurrence, and stabilize legitimacy?

Restoration priorities:

Identify the enforcement action.
Classify whether containment was necessary.
Define scope and duration.
Preserve auditability.
Preserve feedback and appeal.
Map harmed-node repair needs.
Map restriction and force debt.
Repair affected nodes and boundaries.
Correct origin-layer recurrence conditions.
Reduce or terminate enforcement when no longer needed.
Time-validate recurrence reduction and legitimacy.

Relevant restoration arcs:

TableScroll

Restoration Arc	Why it applies
Repair Before Enforcement	Reorders enforcement into restoration sequence
Containment-to-Repair Sequencing	Converts restriction into a temporary phase of repair
Enforcement Debt Reduction	Repairs costs created by restriction or coercion
Restoration Capacity Increase	Ensures repair can follow containment
Boundary Reconstitution	Repairs violated or overhardened boundaries
Feedback Integrity Restoration	Allows correction, appeal, and review
Legitimacy Repair	Restores trust after enforcement
Force Debt Repair	Repairs debt created by coercive action
Recurrence Prevention	Changes conditions that produced the harm
Governance Re-Sequencing	Aligns authority, enforcement, repair, and review
Hidden Debt Reduction	Repairs debt left by enforcement-only response
Temporal Validation	Confirms enforcement did not become permanent pseudo-restoration

Minimal restoration sequence:

textScroll

identify enforcement
→ test containment_need
→ define Σ scope + duration
→ preserve Au/FI/MS
→ map repair_need + restriction_debt
→ perform ℛ
→ change recurrence conditions
→ reduce enforcement where possible
→ validate O/L over Τ

Temporal validation requirement:

textScroll

active harm decreases
repair capacity activates
harmed-node coherence improves
boundary integrity stabilizes
restriction debt decreases
recurrence risk decreases
feedback remains admissible
appeal / review remains functional
legitimacy stabilizes
coherence holds or rises over time

9. Design Rule

Use enforcement as containment or boundary protection only inside a repair-bound sequence.

Operational design requirements:

Define the harm or risk.
Test containment necessity.
Scope enforcement narrowly.
Preserve auditability.
Preserve appeal and review.
Preserve affected-node feedback.
Separate containment from punishment.
Separate punishment from repair.
Map harmed-node repair needs.
Map origin-layer recurrence conditions.
Build restoration capacity.
Repair enforcement side effects.
Reduce or sunset restriction when possible.
Track recurrence.
Validate legitimacy over time.

Avoid:

enforcement as justice;
restriction as restoration;
punishment as repair;
compliance as coherence;
permanent emergency control;
bans without appeal;
moderation without explanation;
policing without restoration;
discipline without harmed-node repair;
coercion without force-debt accounting;
containment that never transitions into repair;
safety claims without recurrence prevention;
visible order as proof of stability;
institutional reputation protection framed as enforcement;
AI refusal or restriction without correction pathway.

10. Cross-Scale Expressions

TableScroll

Scale / Layer	Expression of the Law
U0 — Substrate	Physical containment can stop damage but must be followed by repair of embodied, material, or ecological effects.
U1 — Energy / capacity	Enforcement consumes capacity; repair requires additional slack and resources.
U2 — Boundary / interface	Enforcement may close or restrict membranes; repair clarifies and restores healthy boundary function.
U3 — Process / execution	Enforcement must be sequenced with intake, review, repair, appeal, prevention, and sunset.
U4 — Classification / claim	Systems must classify containment, punishment, repair, and prevention separately.
U5 — Time / delay	Temporary enforcement becomes debt if duration extends without review and repair.
U6 — Field effect	Outcomes reveal whether enforcement reduced harm or merely displaced it.
U7 — Recurrence / memory	Repair must encode memory and prevention so harm does not recur.
U8 — Environment / forcing	Institutions, platforms, security systems, markets, media, and AI systems can normalize enforcement without repair.

11. Examples

Example A — Ban Without Repair

Scenario:

A platform bans a user after a violation but provides no explanation, appeal, harmed-node repair, recurrence prevention, or correction pathway.

Law expression:

textScroll

ban + no ℛ + no FI ⇒ H↑ + L↓

Interpretation:

The ban may stop immediate coupling, but it does not restore coherence by itself.

Example B — Policing Without Community Repair

Scenario:

A governance system increases enforcement in a harmed community but does not repair the underlying conditions producing harm.

Law expression:

textScroll

enforcement↑ + origin_layer_cause unchanged ⇒ recurrence↑

Interpretation:

Enforcement may interrupt incidents while leaving recurrence geometry intact.

Example C — Security Containment Done Correctly

Scenario:

A security team isolates a compromised system, preserves logs, restores service, patches origin-layer cause, communicates impact, and prevents recurrence.

Law expression:

textScroll

containment → audit → repair → prevention ⇒ O↑

Interpretation:

Containment is coherent because it is embedded in repair.

Example D — Institutional Discipline

Scenario:

An institution fires a visible offender but does not repair harmed nodes, audit leadership failures, change incentives, or prevent recurrence.

Law expression:

textScroll

discipline + systemic ℛ absent ⇒ scapegoating + H↑

Interpretation:

Discipline can become scapegoating when systemic repair is omitted.

Example E — Medical Symptom Suppression

Scenario:

A treatment suppresses a symptom but does not restore the damaged membrane, energy system, circulation, signal ecology, or recurrence condition.

Law expression:

textScroll

symptom suppression - restoration ⇒ false recovery risk

Interpretation:

Suppression may be useful, but recovery requires repair.

Example F — Emergency Restriction

Scenario:

A temporary emergency restriction is used to prevent active harm. It includes scope, sunset, audit, review, restoration, and recurrence reduction.

Law expression:

textScroll

emergency containment + Σ + Τ + Au + ℛ ⇒ coherent restriction

Interpretation:

Emergency enforcement can be valid when bounded and repair-linked.

12. Relationship to Nearby Laws

TableScroll

Related Law	Relationship
LAW-001 — Coherence Priority Law	Enforcement is valid only when coherence is preserved or restored
LAW-002 — Coherence Trajectory Law	Enforcement must improve trajectory, not merely immediate order
LAW-003 — Success Proxy Divergence Law	Compliance can diverge from repair
LAW-004 — Stability-Coherence Separation Law	Order after enforcement may not equal coherence
LAW-006 — Time Validation Law	Enforcement must be validated by long-term recurrence reduction
LAW-010 — Hidden Debt Accumulation Law	Enforcement without repair creates hidden debt
LAW-011 — Hidden Debt Return Law	Unrepaired enforcement debt returns
LAW-012 — Error Lag Law	Enforcement failure may appear late
LAW-013 — Auditability-Debt Law	Enforcement without auditability creates debt
LAW-015 — Suppressed Auditability Debt Law	Opaque enforcement accelerates legitimacy loss
LAW-016 — Inversion Formation Law	Safety or justice language can invert into control
LAW-017 — Silent Extraction Law	Enforcement can silently displace costs onto harmed or restricted nodes
LAW-023 — Restoration Capacity Load Law	Repair after enforcement requires sufficient restoration capacity
LAW-030 — Slack Sovereignty Law	Enforcement can consume slack and sovereignty
LAW-041 — Boundary Membrane Law	Enforcement often acts at boundary membranes
LAW-042 — Consent Structurality Law	Enforcement may be needed when consent boundaries fail
LAW-043 — Safe Coupling Law	Enforcement may interrupt unsafe coupling
LAW-045 — Force Debt Law	Coercion creates debt even when necessary
LAW-046 — Contract Validity Law	Formal authority or contract does not prove coherent enforcement
LAW-047 — Controlled Decoupling Law	Some enforcement is controlled decoupling
LAW-048 — Feedback Integrity Law	Enforcement must preserve feedback and appeal
LAW-050 — Control-Restoration Separation Law	Enforcement is control; repair is restoration
LAW-052 — Stability Proof Law	Enforcement must survive perturbation as repair-linked stability
LAW-061 — Restoration Sequencing Law	Containment may precede repair, but must not replace it
LAW-062 — Restoration Is Not the Inverse of Failure Law	Repair after enforcement is not simply undoing the violation
LAW-063 — Origin-Layer Repair Law	Recurrence prevention often requires origin-layer repair
LAW-064 — Restoration Debt Reduction Law	Enforcement must be paired with debt reduction
LAW-065 — Pseudo-Restoration Law	Enforcement can masquerade as restoration
LAW-066 — Restoration Capacity Sufficiency Law	Repair must be sufficiently resourced
LAW-067 — Temporal Proof Law	Enforcement validity requires temporal proof
LAW-068 — Boundary-First Restoration Law	Boundary repair may require immediate containment
LAW-071 — No Forced Forgiveness Law	Enforcement cannot demand closure from harmed nodes
LAW-072 — Quiet Minimization Debt Law	Minimizing harm after enforcement creates debt
LAW-073 — Restoration Before Scaling Law	Enforcement systems should not scale faster than repair systems
LAW-075 — Capacity Before Demand Law	Enforcement should not impose repair demands beyond harmed-node capacity
LAW-102 — Legitimacy Audit Law	Enforcement without repair decays legitimacy
LAW-103 — Justice Stability Law	Justice stabilizes through repair and prevention, not enforcement alone
LAW-104 — Justice Logistics Law	Repair-linked enforcement requires logistics
LAW-106 — Exposure Legibility Law	Exposure reveals enforcement and repair debt
LAW-107 — Exposure Without Restoration Law	Transparency into enforcement debt destabilizes without repair
LAW-108 — Victim Pathway Capacity Law	Enforcement must not require harmed-node overcapacity
LAW-109 — High-Φ Legitimacy Scaling Law	High-influence actors need proportionally stronger repair-linked enforcement
LAW-110 — Governance Sequencing Law	Governance must sequence containment, repair, enforcement, and review
LAW-111 — Meaning Audit Law	Safety, justice, and enforcement narratives are not audit-exempt
LAW-112 — Security as Sustained Coherence Law	Security requires repair, not only restriction
LAW-114 — Pseudo-Security Law	Enforcement can create security theater
LAW-115 — Surveillance–Restoration Law	Detection and enforcement without restoration create enemies and debt
LAW-116 — Emergency Normalization Law	Emergency enforcement must sunset and repair
LAW-120 — Security Legibility Law	Enforcement claims require traceability
LAW-127 — AI Decision Pipeline Law	AI action must pass through Light before execution or refuse coupling
LAW-128 — AI Representation Law	AI enforcement on behalf of others requires traceability and audit
LAW-131 — Cognitive Infrastructure Scaling Law	Cognitive infrastructure enforcement requires proportional restoration
LAW-132 — AI Legitimacy Function Law	AI legitimacy requires accountable, repair-linked enforcement

Aliases folded into this law:

Repair Before Enforcement Law
Enforcement Without Repair Law
Enforcement Debt Law
Restriction Is Not Restoration Law
Repair-First Justice Law
Containment Before Repair Distinction Law
Enforcement Alone Does Not Restore Law

Deduplication note:

This law should remain the root repair-before-enforcement law. LAW-045 defines force debt generally. LAW-050 separates control from restoration. LAW-103 defines justice as stability. LAW-104 defines justice logistics. LAW-106 and LAW-107 govern exposure and restoration sequencing. LAW-116 specializes the emergency-power version of enforcement drift.

13. Operator Mapping

TableScroll

Operator	Role in this law
`Γ`	Classifies harm, containment need, repair need, enforcement scope, recurrence conditions, and debt
`Π`	Operationalizes enforcement, repair sequence, review, appeal, prevention, and sunset mechanisms
`Ξ`	Captures inversion when safety, justice, or repair language justifies control without restoration
`⊗`	Enforcement interrupts, restricts, or reconfigures coupling; repair restores safe coupling geometry
`ℛ`	Performs repair, harmed-node restoration, force-debt reduction, and recurrence prevention
`Τ`	Validates whether enforcement reduces recurrence and stabilizes legitimacy over time
`Θ`	Prevents punitive certainty, overreach, and enforcement-as-proof
`Σ`	Defines scope, duration, domain, and limits of enforcement and repair
`Ψ`	Field and affected-node feedback validates enforcement and repair effects
`Λ`	Tests compatibility between enforcement, repair, and whole-system coherence

Coherent operator sequence:

textScroll

harm / risk appears
→ Θ prevent punitive overreach
→ Γ classify containment_need + repair_need
→ Σ define enforcement scope and duration
→ Π perform scoped containment if required
→ Au/FI/MS preserve review and correction
→ ℛ repair harm + force debt + origin conditions
→ Ψ validate affected-node effects
→ Τ validate recurrence reduction and L stability

Inverted operator sequence:

textScroll

harm / disorder appears
→ enforcement pressure↑
→ Γ collapses repair into punishment / restriction
→ Π enforces visible order
→ ℛ omitted
→ recurrence persists
→ restriction_debt↑
→ H↑
→ Ξ / ι↑
→ L↓

14. Machine-Readable Summary

yamlScroll

id: "LAW-105"
name: "Repair Before Enforcement Law"
type: "law"
status: "draft"
family:
  - "Justice, Governance, and Legitimacy Laws"
summary: "Enforcement without repair accumulates hidden debt; restriction may be needed for safety, but enforcement alone does not restore coherence."
canonical_statement: "Enforcement without repair accumulates hidden debt."
core_form: "enforcement without repair accumulates hidden debt"
canonical_form: "enforcement - ℛ ⇒ H↑"
containment_distinction: "containment may stop harm; repair restores coherence"
safety_valid_form: "active harm + BΣ failure ⇒ containment may be required before repair"
failure_form: "restriction + no repair + recurrence unchanged ⇒ L↓ + H↑"
restoration_valid_contrast: "enforcement valid when scoped, auditable, repair-linked, recurrence-reducing, and time-bounded where possible"
variables:
  primary:
    - "enforcement_load"
    - "containment_need"
    - "repair_need"
    - "restriction_debt"
    - "force_debt"
    - "recurrence_risk"
    - "harmed_node_O"
    - "origin_layer_cause"
    - "prevention_integrity"
    - "ℛ"
    - "R"
    - "R_eff"
    - "BΣ"
    - "Au"
    - "Au_eff"
    - "FI"
    - "MS"
    - "L"
    - "O"
    - "H"
  secondary:
    - "ε"
    - "ι"
    - "µᵢ"
    - "K"
    - "σ"
    - "Φ"
    - "Λ"
    - "⊗"
    - "Γ"
    - "Π"
    - "Ξ"
    - "Θ"
    - "Σ"
    - "Ψ"
    - "Τ"
diagnostics:
  - "Repair Before Enforcement"
  - "Enforcement Load"
  - "Repair Sufficiency"
  - "Restoration Capacity"
  - "Containment Necessity"
  - "Restriction Debt"
  - "Hidden Debt"
  - "Legitimacy"
  - "Boundary Integrity"
  - "Force Debt"
  - "Recurrence Risk"
  - "Pseudo-Restoration Risk"
  - "Feedback Integrity"
  - "Temporal Proof"
failure_modes:
  - "Enforcement Substitution"
  - "Punishment Substitution"
  - "Restriction Debt"
  - "Control-Restoration Confusion"
  - "Repair Deferral"
  - "Containment Drift"
  - "Permanent Restriction"
  - "Compliance Theater"
  - "Pseudo-Safety"
  - "Pseudo-Justice"
  - "Legitimacy Debt"
  - "Recurrence Persistence"
  - "Retaliatory Enforcement"
  - "Audit Suppression"
  - "Hidden Debt Migration"
restoration_arcs:
  - "Repair Before Enforcement"
  - "Containment-to-Repair Sequencing"
  - "Enforcement Debt Reduction"
  - "Restoration Capacity Increase"
  - "Boundary Reconstitution"
  - "Feedback Integrity Restoration"
  - "Legitimacy Repair"
  - "Force Debt Repair"
  - "Recurrence Prevention"
  - "Governance Re-Sequencing"
  - "Hidden Debt Reduction"
  - "Temporal Validation"
related_laws:
  - "LAW-001"
  - "LAW-002"
  - "LAW-003"
  - "LAW-004"
  - "LAW-006"
  - "LAW-010"
  - "LAW-011"
  - "LAW-012"
  - "LAW-013"
  - "LAW-015"
  - "LAW-016"
  - "LAW-017"
  - "LAW-023"
  - "LAW-030"
  - "LAW-041"
  - "LAW-042"
  - "LAW-043"
  - "LAW-045"
  - "LAW-046"
  - "LAW-047"
  - "LAW-048"
  - "LAW-050"
  - "LAW-052"
  - "LAW-061"
  - "LAW-062"
  - "LAW-063"
  - "LAW-064"
  - "LAW-065"
  - "LAW-066"
  - "LAW-067"
  - "LAW-068"
  - "LAW-071"
  - "LAW-072"
  - "LAW-073"
  - "LAW-075"
  - "LAW-102"
  - "LAW-103"
  - "LAW-104"
  - "LAW-106"
  - "LAW-107"
  - "LAW-108"
  - "LAW-109"
  - "LAW-110"
  - "LAW-111"
  - "LAW-112"
  - "LAW-114"
  - "LAW-115"
  - "LAW-116"
  - "LAW-120"
  - "LAW-127"
  - "LAW-128"
  - "LAW-131"
  - "LAW-132"
related_invariants:
  - "INV-001"
  - "INV-002"
  - "INV-006"
  - "INV-073"
  - "INV-080"
operator_sequence:
  coherent:
    - "harm / risk appears"
    - "Θ prevent punitive overreach"
    - "Γ classify containment_need + repair_need"
    - "Σ define enforcement scope and duration"
    - "Π perform scoped containment if required"
    - "Au/FI/MS preserve review and correction"
    - "ℛ repair harm + force debt + origin conditions"
    - "Ψ validate affected-node effects"
    - "Τ validate recurrence reduction and L stability"
  inverted:
    - "harm / disorder appears"
    - "enforcement pressure↑"
    - "Γ collapses repair into punishment / restriction"
    - "Π enforces visible order"
    - "ℛ omitted"
    - "recurrence persists"
    - "restriction_debt↑"
    - "H↑"
    - "Ξ / ι↑"
    - "L↓"
aliases:
  - "Repair Before Enforcement Law"
  - "Enforcement Without Repair Law"
  - "Enforcement Debt Law"
  - "Restriction Is Not Restoration Law"
  - "Repair-First Justice Law"
  - "Containment Before Repair Distinction Law"
  - "Enforcement Alone Does Not Restore Law"
deduplication_note: "Root repair-before-enforcement law. LAW-045 defines force debt generally. LAW-050 separates control from restoration. LAW-103 defines justice as stability. LAW-104 defines justice logistics. LAW-106 and LAW-107 govern exposure and restoration sequencing. LAW-116 specializes the emergency-power version of enforcement drift."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-105 — Repair Before Enforcement Law

Enforcement without repair accumulates hidden debt.

Core form:

textScroll

enforcement without repair accumulates hidden debt

Canonical form:

textScroll

enforcement - ℛ ⇒ H↑

Plain meaning:

Restriction may be needed for safety. Containment may be needed to stop harm. Enforcement may be needed to preserve boundaries. But enforcement alone does not restore coherence. Repair, prevention, feedback, review, and legitimacy restoration must follow.

Containment distinction:

textScroll

containment may stop harm; repair restores coherence

Failure form:

textScroll

restriction + no repair + recurrence unchanged ⇒ L↓ + H↑

Primary variables:

enforcement_load, containment_need, repair_need, restriction_debt, force_debt, recurrence_risk, harmed_node_O, origin_layer_cause, prevention_integrity, ℛ, R, R_eff, BΣ, Au, Au_eff, FI, MS, L, O, H, Γ, Π, Ξ, Θ, Σ, Ψ, Τ

Diagnostic signature:

Enforcement and visible order rise while repair falls, appeal and feedback weaken, recurrence remains unchanged, restriction duration increases, and legitimacy declines. This indicates enforcement substitution.

Failure risk:

Enforcement substitution, punishment substitution, restriction debt, control-restoration confusion, repair deferral, containment drift, permanent restriction, compliance theater, pseudo-safety, pseudo-justice, legitimacy debt, recurrence persistence, retaliatory enforcement, audit suppression, hidden debt migration.

Restoration priority:

Identify enforcement, test containment necessity, define scope and duration, preserve auditability and appeal, map repair need and restriction debt, restore harmed nodes and boundaries, correct origin-layer recurrence conditions, reduce enforcement where possible, and validate coherence over time.

LAW-104 — Justice Logistics Law

Registry

LAW-106 — Exposure Legibility Law