0. Plain Statement
Justice cannot exceed the substrate and logistics supporting it.
Plain-language version:
A justice system cannot produce coherent justice at scale if it does not have enough repair capacity, audit capacity, pathway capacity, operator capacity, time, money, attention, evidence handling, harmed-node support, and recurrence-prevention infrastructure.
When justice load exceeds restoration logistics, injustice becomes mechanical.
1. Formal Definition
The Justice Logistics Law states that justice is constrained by the material, procedural, informational, relational, temporal, and restoration logistics that support it.
Justice requires more than principles, rights, laws, procedures, authority, or moral claims.
It requires a substrate capable of carrying:
- intake;
- testimony;
- evidence handling;
- auditability;
- classification;
- affected-node support;
- harmed-node capacity protection;
- responsibility mapping;
- repair design;
- restoration execution;
- enforcement where needed;
- recurrence prevention;
- feedback processing;
- appeal;
- review;
- operator slack;
- temporal follow-through;
- legitimacy repair;
- memory and recurrence tracking.
If justice demand exceeds these logistics, the system compresses.
Compression can appear as:
- backlog;
- delay;
- procedural flattening;
- rushed classification;
- harmed-node overburdening;
- low-quality repair;
- enforcement substitution;
- plea-like pressure;
- settlement pressure;
- forced closure;
- evidence loss;
- symbolic apology;
- arbitrary outcomes;
- staff burnout;
- appeal failure;
- recurrence persistence;
- legitimacy collapse.
Canonical form:
R_eff < Load × Gain ⇒ injustice becomes mechanicalA justice system without repair capacity cannot produce coherent justice at scale.
2. Canonical Form
Core form:
justice cannot exceed the substrate and logistics supporting itCanonical load form:
R_eff < Load × Gain ⇒ injustice becomes mechanicalCapacity form:
justice_capacity = f(R_eff, Au_eff, pathway_throughput, operator_slack, repair_logistics, feedback_throughput)Compression form:
justice_load > justice_capacity ⇒ procedural compression + H↑ + L↓Failure form:
justice demand without logistics ⇒ backlog + flattening + repair failure + recurrenceRestoration-valid contrast:
justice valid at scale when logistics capacity ≥ justice load and repair remains proportional over ΤRelated variables:
O, H, ε, ι, Au, Au_eff, µᵢ, BΣ, K, σ, R, R_eff, 𝓑, 𝓓, Φ, Λ, ⊗, Γ, Π, Ξ, ℛ, Θ, Σ, Ψ, Τ, FI, MS, L, justice_capacity, justice_load, pathway_throughput, repair_logistics, feedback_throughput, operator_slack, audit_load, case_backlog, delay_cost, harmed_node_capacity, recurrence_riskWhere:
| Variable | Meaning in this law |
|---|---|
justice_capacity | Total capacity of a system to carry justice processes coherently |
justice_load | Total demand placed on justice pathways |
R_eff | Effective restoration capacity under real load |
Au_eff | Effective auditability under real load |
pathway_throughput | Number and complexity of cases, claims, harms, or disputes that can be processed coherently |
repair_logistics | Material, procedural, relational, and operational infrastructure for repair |
feedback_throughput | Ability to receive, process, and act on affected-node feedback |
operator_slack | Slack available to staff, mediators, judges, auditors, responders, advocates, support nodes, and system operators |
audit_load | Load created by evidence, traceability, testimony, review, appeal, and investigation |
case_backlog | Accumulated unresolved justice load |
delay_cost | Hidden debt created by unresolved harm over time |
harmed_node_capacity | Capacity of affected nodes to participate in justice pathways |
recurrence_risk | Likelihood harm repeats while justice logistics are insufficient |
O | Coherence; justice logistics must preserve system and harmed-node coherence |
H | Hidden debt; rises when justice logistics fail |
BΣ | Boundary integrity; logistics must protect access, scope, consent, and safety boundaries |
FI | Feedback integrity; feedback must not be lost in queues or procedure |
MS | Moral / meaning symmetry; logistics must not create unequal pathway access |
L | Legitimacy; decays when justice capacity cannot carry justice claims |
ι / Ξ | Inversion when justice language hides mechanical failure |
Φ | Visible throughput or case closure; not sufficient proof of justice |
Γ | Classifies cases, harms, priorities, complexity, capacity, and triage needs |
Π | Procedures, pathways, staffing models, escalation rules, triage systems, and repair infrastructure |
ℛ | Restoration action performed through justice logistics |
Θ | Humility required to admit capacity limits |
Σ | Scope of justice promise and pathway coverage |
Ψ | Field and affected-node feedback validating pathway coherence |
Τ | Time validation of whether justice logistics reduce recurrence and debt |
3. Core Mechanism
The law unfolds because justice is not produced by moral intent alone; it must be carried by a substrate.
Coherent justice logistics pathway
justice demand appears
→ load is classified
→ pathway capacity is measured
→ audit and repair logistics are allocated
→ harmed-node capacity is protected
→ repair proceeds proportionally
→ recurrence conditions change
→ legitimacy stabilizes over timeMechanical injustice pathway
justice demand appears
→ load exceeds capacity
→ backlog and delay rise
→ procedure compresses complexity
→ harmed nodes carry excess burden
→ repair becomes insufficient
→ recurrence persists
→ H↑ + L↓The core mechanism is:
justice is capacity-boundDetailed mechanism:
- Justice demand enters the system.
Harm, conflict, breach, abuse, complaint, violation, claim, exposure, or instability requires a justice pathway.
- The system must classify load.
It must understand complexity, affected nodes, evidence requirements, repair needs, urgency, risk, and recurrence conditions.
- The pathway requires logistics.
Justice consumes time, attention, staff, evidence capacity, audit capacity, support capacity, restoration capacity, and follow-through capacity.
- If capacity is sufficient, justice can stabilize.
Harm can be heard, mapped, repaired, prevented, and validated.
- If capacity is insufficient, the system compresses.
Compression forces shortcuts: delay, flattening, forced closure, punishment substitution, weak repair, or denial.
- Mechanical injustice emerges.
The system may not intend injustice, but its logistics produce it repeatedly.
- Time validates logistics.
Coherent justice logistics reduce recurrence, backlog, hidden debt, and legitimacy shock over time.
4. When This Law Applies
This law applies whenever a system promises, administers, designs, scales, reforms, audits, or depends on justice, repair, dispute resolution, complaint handling, enforcement, moderation, appeals, victim pathways, accountability, or governance.
It is especially important when:
- justice demand rises;
- exposure increases complaint volume;
- harm reports exceed processing capacity;
- audit requirements increase;
- affected-node support is insufficient;
- case backlogs grow;
- enforcement substitutes for repair;
- institutions promise justice without staffing repair;
- AI systems scale moderation or appeals without restoration pathways;
- governance systems create rights without usable pathways;
- security systems detect harm without repair capacity;
- justice depends on harmed-node endurance;
- operators are overloaded;
- procedures flatten distinct harms;
- legitimacy depends on justice delivery;
- recurrence continues despite case closure.
The law applies strongly when:
justice_load exceeds R_eff + Au_eff + pathway_throughputor when:
justice promises exceed justice logisticsTypical domains:
| Domain | Justice Logistics Expression |
|---|---|
| AI systems | AI moderation, appeals, safety claims, user reports, model harms, and representation disputes require scalable audit and restoration logistics. |
| Security | Incident response requires not only detection and containment, but repair, clearance, prevention, and affected-node support. |
| Institutions | Complaint systems fail when intake, investigation, repair, and prevention capacity are underbuilt. |
| Medicine / biology | Care justice requires access, time, diagnostics, follow-up, consent, correction, and repair logistics. |
| Economy | Economic justice requires circulation repair, contract pathway repair, debt relief logistics, and capacity transfer. |
| Governance | Rights and laws require usable pathways, staffing, audit, appeal, enforcement, restoration, and prevention. |
| Culture | Cultural justice requires memory, testimony, ritual repair, boundary repair, and recurrence prevention infrastructure. |
| Restoration | Restoration cannot be promised without logistics for harmed-node support, repair execution, and time validation. |
5. When This Law Does Not Apply
This law should not be used to excuse injustice because “capacity is limited.”
Capacity limits explain failure; they do not justify leaving hidden debt unaddressed.
When logistics are insufficient, the coherent response is to:
- narrow scope honestly;
- triage transparently;
- increase capacity;
- reduce load;
- repair pathways;
- protect harmed-node capacity;
- stop making promises the system cannot carry;
- prevent new harm where repair capacity is absent.
False-positive cases:
| Case | Why capacity still matters without excusing harm |
|---|---|
| A system lacks funding | Funding limits explain capacity but do not erase justice debt |
| Staff are overloaded | Operator overload predicts failure but does not validate poor outcomes |
| Backlog is large | Backlog requires triage and capacity repair, not denial |
| Harm is complex | Complexity requires higher throughput and better classification |
| Emergency load spikes | Emergency triage may be valid if transparent, scoped, and repair-bound |
| Full repair is not immediately possible | Partial repair may be coherent if acknowledged and sequenced |
| A pathway must prioritize | Prioritization must be auditable and not become hidden denial |
Important distinction:
Logistics limits are not moral absolution; they are design constraints.
6. Diagnostic Signature
Canonical diagnostic:
R_eff < Load × Gain ⇒ injustice becomes mechanicalWarning signature:
justice demand↑
case backlog↑
operator slack↓
audit load↑
repair capacity flat
pathway throughput saturated
affected-node burden↑
⇒ mechanical injusticeCommon indicators:
| Diagnostic | Expected movement | Interpretation |
|---|---|---|
justice_load | measured | Total justice demand must be visible |
justice_capacity | measured | Capacity must be compared to load |
R_eff | must meet load | Effective restoration capacity determines repair viability |
Au_eff | must meet audit load | Audit must remain meaningful under scale |
pathway_throughput | must be sufficient | Claims must move without flattening |
repair_logistics | must be sufficient | Repair must be executable, not merely promised |
feedback_throughput | must be sufficient | Affected feedback must not disappear |
operator_slack | must remain adequate | Staff overload produces mechanical failure |
case_backlog | should not grow unbounded | Backlog becomes hidden debt |
delay_cost | increases with unresolved harm | Delay itself can create debt |
harmed_node_capacity | must be protected | Pathways should not demand overcapacity |
L | ↓ if logistics fail | Legitimacy decays when justice cannot be delivered |
H | ↑ if logistics fail | Hidden debt accumulates |
Φ | not sufficient | Closure counts or throughput metrics are not justice proof |
Τ | required | Time validates whether logistics reduce recurrence and debt |
Additional diagnostics:
| Diagnostic | Use |
|---|---|
| Justice Logistics | Tests whether justice has sufficient substrate |
| Effective Restoration Capacity | Measures repair capacity under load |
| Justice Load | Measures incoming and accumulated demand |
| Pathway Throughput | Detects bottlenecks and flattening |
| Case Backlog | Tracks unresolved justice debt |
| Repair Sufficiency | Tests whether repair capacity matches harm |
| Victim Pathway Capacity | Tests whether harmed nodes can actually use pathways |
| Staff / Operator Load | Detects burnout-driven mechanical injustice |
| Auditability Capacity | Tests whether audit survives scale |
| Feedback Throughput | Detects affected-node feedback loss |
| Mechanical Injustice | Detects logistics-created injustice independent of intent |
| Temporal Proof | Confirms logistics hold over recurrence |
7. Failure Pattern
If ignored, this law allows justice systems to promise coherence while producing mechanical injustice.
General failure pathway:
justice promise forms
→ demand rises
→ logistics remain insufficient
→ backlog and delay increase
→ complexity is flattened
→ repair becomes symbolic or absent
→ harmed-node capacity collapses
→ recurrence persists
→ legitimacy decaysCommon failure modes:
- Mechanical Injustice — injustice produced by insufficient logistics rather than explicit malice.
- Justice Backlog — unresolved justice load accumulates as hidden debt.
- Repair Capacity Failure — system cannot perform the repair it claims.
- Pathway Saturation — intake, investigation, appeal, or restoration pathways exceed capacity.
- Procedural Compression — complex harms are forced into simplified categories.
- Case Flattening — distinct contexts are treated as identical for throughput.
- Victim Pathway Collapse — harmed nodes cannot endure or access the pathway.
- Audit Bottleneck — evidence, review, or traceability fails under load.
- Feedback Queue Failure — affected feedback is received but not processed.
- Enforcement Substitution — restriction or punishment replaces repair.
- Justice Theater — visible procedure substitutes for coherent justice.
- Legitimacy Debt — trust decays because justice promises cannot be delivered.
- Burnout Cascade — operators lose slack and produce degraded decisions.
- Delayed Repair Debt — unresolved harm worsens because repair is delayed.
- Recurrence Persistence — the same pattern repeats because prevention logistics never engage.
Compact failure signature:
justice_load↑ + R_eff insufficient ⇒ backlog↑ + H↑ + L↓8. Restoration Implications
Restoration requires repairing justice logistics, not only improving justice language.
The first restoration question is not:
Does the system claim justice?The first restoration question is:
Can the system actually carry the justice load without collapsing audit, harmed-node capacity, repair, or prevention?Restoration priorities:
- Measure justice load.
- Measure effective restoration capacity.
- Measure effective auditability.
- Map pathway throughput.
- Identify bottlenecks.
- Protect harmed-node capacity.
- Regenerate operator slack.
- Increase repair logistics.
- Triage transparently where capacity is insufficient.
- Reduce recurrence conditions so future load decreases.
Relevant restoration arcs:
| Restoration Arc | Why it applies |
|---|---|
| Justice Logistics Repair | Repairs the substrate that carries justice |
| Restoration Capacity Increase | Raises R_eff to match load |
| Pathway Throughput Repair | Removes intake, investigation, repair, and appeal bottlenecks |
| Victim Pathway Redesign | Reduces over-demand on harmed nodes |
| Auditability Capacity Increase | Ensures audit survives case volume and complexity |
| Feedback Throughput Restoration | Makes affected feedback actionable |
| Triage Re-Sequencing | Orders cases and harms transparently under capacity limits |
| Repair Sufficiency Increase | Matches repair logistics to harm |
| Backlog Debt Reduction | Clears accumulated unresolved justice debt |
| Operator Slack Regeneration | Prevents burnout-driven degradation |
| Governance Re-Sequencing | Aligns authority, repair, enforcement, and disclosure |
| Temporal Validation | Confirms logistics hold over time |
Minimal restoration sequence:
measure justice_load
→ measure R_eff + Au_eff + pathway_throughput
→ identify bottlenecks
→ protect harmed-node capacity
→ increase repair logistics + operator slack
→ triage transparently
→ reduce backlog and recurrence
→ validate L and O over ΤTemporal validation requirement:
justice load becomes visible
pathway throughput improves
operator slack stabilizes
auditability remains intact
harmed-node burden decreases
repair becomes proportional
backlog decreases
recurrence decreases
hidden debt decreases
legitimacy stabilizes over time9. Design Rule
Do not promise justice beyond the logistics that can carry audit, repair, harmed-node support, and recurrence prevention.
Operational design requirements:
- Measure load before promising outcomes.
- Build intake capacity.
- Build audit capacity.
- Build evidence-handling capacity.
- Build harmed-node support.
- Build repair pathways.
- Build appeal and review.
- Build feedback throughput.
- Build recurrence-prevention systems.
- Preserve operator slack.
- Make capacity limits visible.
- Triage transparently.
- Scale restoration capacity before scaling exposure or enforcement.
- Track delay cost.
- Track backlog as hidden debt.
- Validate outcomes over time.
Avoid:
- rights without pathways;
- policies without staff;
- exposure without restoration logistics;
- complaint intake without repair capacity;
- enforcement without repair;
- appeals without throughput;
- support pathways that require harmed-node overcapacity;
- closure metrics as justice proof;
- dashboards that hide backlog debt;
- AI moderation at scale without appeal and restoration capacity;
- security detection without repair and prevention logistics;
- institutional apology without follow-through logistics;
- pretending moral clarity is enough when substrate capacity is absent.
10. Cross-Scale Expressions
| Scale / Layer | Expression of the Law |
|---|---|
| U0 — Substrate | Justice requires material, embodied, ecological, and physical capacity to support harmed nodes and repair effects. |
| U1 — Energy / capacity | Justice consumes energy, time, money, attention, staff, and slack. |
| U2 — Boundary / interface | Justice pathways require accessible, safe, scoped, and consent-respecting interfaces. |
| U3 — Process / execution | Justice becomes intake, triage, investigation, audit, repair, appeal, enforcement, and prevention workflows. |
| U4 — Classification / claim | Justice load must be classified accurately without flattening distinct harms. |
| U5 — Time / delay | Delay creates debt; backlog is a temporal justice failure. |
| U6 — Field effect | Field outcomes reveal whether justice logistics actually repair harm and prevent recurrence. |
| U7 — Recurrence / memory | Logistics must encode recurrence prevention and remember unresolved justice debt. |
| U8 — Environment / forcing | Institutions, markets, platforms, media, security systems, and AI systems shape justice load and pathway capacity. |
11. Examples
Example A — Complaint System Without Repair Capacity
Scenario:
An institution opens a complaint channel but does not staff investigation, harmed-node support, repair design, or recurrence prevention.
Law expression:
intake↑ + R_eff flat ⇒ backlog↑ + L↓Interpretation:
The pathway increases visibility but cannot carry justice.
Example B — AI Appeals at Scale
Scenario:
An AI platform moderates millions of decisions but provides slow, opaque, or unusable appeals.
Law expression:
decision_scale↑ + appeal_throughput↓ ⇒ mechanical injusticeInterpretation:
AI governance cannot be legitimate if appeal, audit, and repair logistics do not scale with decisions.
Example C — Courts Under Load
Scenario:
A legal system has formal rights and procedures, but backlog, cost, delay, and complexity make resolution inaccessible to many harmed nodes.
Law expression:
formal rights + pathway_capacity↓ ⇒ justice access failureInterpretation:
Rights require logistics to become justice.
Example D — Exposure Without Pathway Capacity
Scenario:
A reform effort encourages people to report harm, but the system has no capacity to process testimony, protect reporters, repair harm, or prevent recurrence.
Law expression:
exposure↑ + pathway_throughput insufficient ⇒ harm amplificationInterpretation:
Visibility must be paired with restoration logistics.
Example E — Security Detection Without Restoration
Scenario:
A security program detects more incidents but lacks clearance, remediation, user support, root-cause repair, and recurrence prevention capacity.
Law expression:
detection↑ + repair_logistics↓ ⇒ security justice debtInterpretation:
Detection increases justice load unless restoration pathways scale.
Example F — Coherent Justice Logistics
Scenario:
A governance system scales intake, audit, harmed-node support, repair capacity, transparent triage, prevention architecture, and follow-up together.
Law expression:
justice_capacity ≥ justice_load ⇒ H↓ + L↑ + recurrence↓Interpretation:
Justice becomes stable when logistics can carry the load.
12. Relationship to Nearby Laws
| Related Law | Relationship |
|---|---|
| LAW-001 — Coherence Priority Law | Justice logistics are valid when coherence rises |
| LAW-002 — Coherence Trajectory Law | Justice logistics must improve trajectory, not merely process cases |
| LAW-004 — Stability-Coherence Separation Law | A stable backlog may hide incoherence |
| LAW-006 — Time Validation Law | Logistics are validated across delay and recurrence |
| LAW-010 — Hidden Debt Accumulation Law | Unprocessed justice load accumulates hidden debt |
| LAW-011 — Hidden Debt Return Law | Backlog and unresolved harm return as destabilization |
| LAW-012 — Error Lag Law | Visible justice collapse often appears late |
| LAW-013 — Auditability-Debt Law | Audit bottlenecks create debt |
| LAW-014 — Constraint Complexity Debt Law | Too many procedural constraints can exceed auditability |
| LAW-020 — Bandwidth Threshold Law | Justice pathways fail when bandwidth is exceeded |
| LAW-021 — Coherence-Preserving Scaling Law | Justice must scale capacity faster than load |
| LAW-022 — Integration Capacity Law | Justice requires integration of evidence, testimony, repair, and prevention |
| LAW-023 — Restoration Capacity Load Law | LAW-104 specializes restoration capacity load into justice systems |
| LAW-029 — Integration Cost Law | Justice integration has real cost |
| LAW-030 — Slack Sovereignty Law | Operator and harmed-node slack are necessary for justice |
| LAW-031 — Observability Collapse Law | Overload can reduce visibility into justice effects |
| LAW-035 — Delayed Transition Cost Law | Delayed justice increases transition cost |
| LAW-048 — Feedback Integrity Law | Justice logistics must process affected feedback |
| LAW-049 — Feedback Without Slack Becomes Extraction Law | Asking for testimony without support extracts from harmed nodes |
| LAW-050 — Control-Restoration Separation Law | Enforcement logistics cannot substitute for restoration logistics |
| LAW-052 — Stability Proof Law | Justice logistics must survive load and perturbation |
| LAW-061 — Restoration Sequencing Law | Justice logistics require sequence design |
| LAW-064 — Restoration Debt Reduction Law | Justice logistics must reduce restoration debt |
| LAW-065 — Pseudo-Restoration Law | Procedures without logistics become pseudo-restoration |
| LAW-066 — Restoration Capacity Sufficiency Law | Justice requires sufficient restoration capacity |
| LAW-067 — Temporal Proof Law | Justice logistics require proof over time |
| LAW-068 — Boundary-First Restoration Law | Pathways must first protect safety and boundaries |
| LAW-073 — Restoration Before Scaling Law | Justice exposure and enforcement should not scale before restoration |
| LAW-075 — Capacity Before Demand Law | Justice pathways must not demand more than nodes can carry |
| LAW-102 — Legitimacy Audit Law | Legitimacy decays when justice logistics fail |
| LAW-103 — Justice Stability Law | LAW-104 defines the substrate limits of justice stability |
| LAW-105 — Repair Before Enforcement Law | Enforcement without repair capacity creates debt |
| LAW-106 — Exposure Legibility Law | Exposure increases visible justice load |
| LAW-107 — Exposure Without Restoration Law | Transparency without logistics destabilizes |
| LAW-108 — Victim Pathway Capacity Law | Justice logistics must fit harmed-node capacity |
| LAW-109 — High-Φ Legitimacy Scaling Law | High-influence systems require proportionally scaled justice logistics |
| LAW-110 — Governance Sequencing Law | Governance must sequence logistics under load |
| LAW-111 — Meaning Audit Law | Justice claims are not audit-exempt from capacity reality |
| LAW-112 — Security as Sustained Coherence Law | Security justice requires restoration logistics |
| LAW-115 — Surveillance–Restoration Law | Detection without restoration increases justice load |
| LAW-120 — Security Legibility Law | Security claims require traceability logistics |
| LAW-131 — Cognitive Infrastructure Scaling Law | Cognitive infrastructure requires governance and justice capacity proportional to influence |
| LAW-132 — AI Legitimacy Function Law | AI legitimacy requires repair and audit logistics |
| LAW-133 — Error Scale Law | Large scale converts small error rates into large justice load |
| LAW-134 — Layered Interception Law | Distributed safeguards reduce justice load before central pathways saturate |
Aliases folded into this law:
- Justice Logistics Law
- Justice Cannot Exceed Logistics Law
- Justice Substrate Law
- Repair Capacity Justice Law
- Justice Load Law
- Mechanical Injustice Law
- Justice Capacity Sufficiency Law
Deduplication note:
This law should remain the root justice-logistics law. LAW-103 defines justice as a stability variable. LAW-104 defines the substrate and logistics limits of that stability. LAW-105 explains why enforcement without repair creates debt. LAW-107 defines the instability caused by exposure without restoration. LAW-108 specializes pathway design around harmed-node capacity.
13. Operator Mapping
| Operator | Role in this law |
|---|---|
Γ | Classifies justice load, case complexity, harm type, pathway need, triage priority, and repair requirement |
Π | Operationalizes justice logistics through intake, triage, audit, repair, appeal, staffing, and prevention systems |
Ξ | Captures inversion when justice language hides backlog, compression, or mechanical injustice |
⊗ | Justice pathways are couplings that must not overload harmed nodes or operators |
ℛ | Performs repair and increases restoration capacity |
Τ | Validates whether logistics reduce backlog, recurrence, hidden debt, and legitimacy shock over time |
Θ | Prevents overpromising, moral theater, and denial of capacity limits |
Σ | Defines scope of justice promises, pathway coverage, and triage domain |
Ψ | Field and affected-node feedback reveals whether pathways actually work |
Λ | Tests compatibility between justice load, logistics, and whole-system coherence |
Coherent operator sequence:
justice demand appears
→ Θ admit capacity limits
→ Γ classify load / complexity / harmed-node needs
→ Σ define scope and triage domain
→ measure R_eff + Au_eff + pathway_throughput
→ Π allocate logistics and sequence pathways
→ ℛ perform repair and increase capacity
→ Ψ validate affected-node effects
→ Τ validate backlog / recurrence / L over timeInverted operator sequence:
justice demand rises
→ logistics remain flat
→ Γ flattens complexity
→ Π processes for closure metrics
→ harmed-node burden↑
→ repair insufficient
→ backlog and recurrence persist
→ H↑
→ Ξ / ι↑
→ L↓14. Machine-Readable Summary
id: "LAW-104"
name: "Justice Logistics Law"
type: "law"
status: "draft"
family:
- "Justice, Governance, and Legitimacy Laws"
summary: "Justice cannot exceed the substrate and logistics supporting it; a justice system without sufficient repair capacity cannot produce coherent justice at scale."
canonical_statement: "Justice cannot exceed the substrate and logistics supporting it."
core_form: "justice cannot exceed the substrate and logistics supporting it"
canonical_load_form: "R_eff < Load × Gain ⇒ injustice becomes mechanical"
capacity_form: "justice_capacity = f(R_eff, Au_eff, pathway_throughput, operator_slack, repair_logistics, feedback_throughput)"
compression_form: "justice_load > justice_capacity ⇒ procedural compression + H↑ + L↓"
failure_form: "justice demand without logistics ⇒ backlog + flattening + repair failure + recurrence"
restoration_valid_contrast: "justice valid at scale when logistics capacity ≥ justice load and repair remains proportional over Τ"
variables:
primary:
- "justice_capacity"
- "justice_load"
- "R_eff"
- "Au_eff"
- "pathway_throughput"
- "repair_logistics"
- "feedback_throughput"
- "operator_slack"
- "audit_load"
- "case_backlog"
- "delay_cost"
- "harmed_node_capacity"
- "recurrence_risk"
- "L"
- "H"
secondary:
- "O"
- "ε"
- "ι"
- "Au"
- "µᵢ"
- "BΣ"
- "K"
- "σ"
- "R"
- "𝓑"
- "𝓓"
- "Φ"
- "Λ"
- "⊗"
- "Γ"
- "Π"
- "Ξ"
- "ℛ"
- "Θ"
- "Σ"
- "Ψ"
- "Τ"
- "FI"
- "MS"
diagnostics:
- "Justice Logistics"
- "Restoration Capacity"
- "Effective Restoration Capacity"
- "Justice Load"
- "Pathway Throughput"
- "Case Backlog"
- "Repair Sufficiency"
- "Victim Pathway Capacity"
- "Staff / Operator Load"
- "Auditability Capacity"
- "Feedback Throughput"
- "Legitimacy Shock Risk"
- "Mechanical Injustice"
- "Temporal Proof"
failure_modes:
- "Mechanical Injustice"
- "Justice Backlog"
- "Repair Capacity Failure"
- "Pathway Saturation"
- "Procedural Compression"
- "Case Flattening"
- "Victim Pathway Collapse"
- "Audit Bottleneck"
- "Feedback Queue Failure"
- "Enforcement Substitution"
- "Justice Theater"
- "Legitimacy Debt"
- "Burnout Cascade"
- "Delayed Repair Debt"
- "Recurrence Persistence"
restoration_arcs:
- "Justice Logistics Repair"
- "Restoration Capacity Increase"
- "Pathway Throughput Repair"
- "Victim Pathway Redesign"
- "Auditability Capacity Increase"
- "Feedback Throughput Restoration"
- "Triage Re-Sequencing"
- "Repair Sufficiency Increase"
- "Backlog Debt Reduction"
- "Operator Slack Regeneration"
- "Governance Re-Sequencing"
- "Temporal Validation"
related_laws:
- "LAW-001"
- "LAW-002"
- "LAW-004"
- "LAW-006"
- "LAW-010"
- "LAW-011"
- "LAW-012"
- "LAW-013"
- "LAW-014"
- "LAW-020"
- "LAW-021"
- "LAW-022"
- "LAW-023"
- "LAW-029"
- "LAW-030"
- "LAW-031"
- "LAW-035"
- "LAW-048"
- "LAW-049"
- "LAW-050"
- "LAW-052"
- "LAW-061"
- "LAW-064"
- "LAW-065"
- "LAW-066"
- "LAW-067"
- "LAW-068"
- "LAW-073"
- "LAW-075"
- "LAW-102"
- "LAW-103"
- "LAW-105"
- "LAW-106"
- "LAW-107"
- "LAW-108"
- "LAW-109"
- "LAW-110"
- "LAW-111"
- "LAW-112"
- "LAW-115"
- "LAW-120"
- "LAW-131"
- "LAW-132"
- "LAW-133"
- "LAW-134"
related_invariants:
- "INV-001"
- "INV-002"
- "INV-006"
- "INV-073"
- "INV-080"
operator_sequence:
coherent:
- "justice demand appears"
- "Θ admit capacity limits"
- "Γ classify load / complexity / harmed-node needs"
- "Σ define scope and triage domain"
- "measure R_eff + Au_eff + pathway_throughput"
- "Π allocate logistics and sequence pathways"
- "ℛ perform repair and increase capacity"
- "Ψ validate affected-node effects"
- "Τ validate backlog / recurrence / L over time"
inverted:
- "justice demand rises"
- "logistics remain flat"
- "Γ flattens complexity"
- "Π processes for closure metrics"
- "harmed-node burden↑"
- "repair insufficient"
- "backlog and recurrence persist"
- "H↑"
- "Ξ / ι↑"
- "L↓"
aliases:
- "Justice Logistics Law"
- "Justice Cannot Exceed Logistics Law"
- "Justice Substrate Law"
- "Repair Capacity Justice Law"
- "Justice Load Law"
- "Mechanical Injustice Law"
- "Justice Capacity Sufficiency Law"
deduplication_note: "Root justice-logistics law. LAW-103 defines justice as a stability variable. LAW-104 defines the substrate and logistics limits of that stability. LAW-105 explains why enforcement without repair creates debt. LAW-107 defines the instability caused by exposure without restoration. LAW-108 specializes pathway design around harmed-node capacity."
source: "content/archive/laws/technical.md"15. Compact Card Version
LAW-104 — Justice Logistics Law
Justice cannot exceed the substrate and logistics supporting it.
Core form:
justice cannot exceed the substrate and logistics supporting itCanonical load form:
R_eff < Load × Gain ⇒ injustice becomes mechanicalPlain meaning:
A justice system cannot produce coherent justice at scale if it lacks sufficient repair capacity, audit capacity, pathway throughput, operator slack, harmed-node support, evidence handling, feedback processing, and recurrence-prevention infrastructure.
Capacity form:
justice_capacity = f(R_eff, Au_eff, pathway_throughput, operator_slack, repair_logistics, feedback_throughput)Failure form:
justice demand without logistics ⇒ backlog + flattening + repair failure + recurrencePrimary variables:
justice_capacity, justice_load, R_eff, Au_eff, pathway_throughput, repair_logistics, feedback_throughput, operator_slack, audit_load, case_backlog, delay_cost, harmed_node_capacity, recurrence_risk, L, H, O, BΣ, FI, MS, Γ, Π, ℛ, Θ, Σ, Ψ, Τ
Diagnostic signature:
Justice demand rises, case backlog grows, operator slack falls, audit load increases, repair capacity remains flat, pathway throughput saturates, and affected-node burden rises. This indicates mechanical injustice.
Failure risk:
Mechanical injustice, justice backlog, repair capacity failure, pathway saturation, procedural compression, case flattening, victim pathway collapse, audit bottleneck, feedback queue failure, enforcement substitution, justice theater, legitimacy debt, burnout cascade, delayed repair debt, recurrence persistence.
Restoration priority:
Measure justice load, restoration capacity, auditability, and pathway throughput; identify bottlenecks; protect harmed-node capacity; increase repair logistics and operator slack; triage transparently; reduce backlog and recurrence; and validate legitimacy and coherence over time.