0. Justice Scope Note

This entry is conceptual and systems-oriented.

It does not treat every delay, backlog, resource limit, triage process, prioritization choice, simplified process, or capacity-aware enforcement decision as inherently failed.

Justice systems operate under constraints.

Review systems may face large volumes.

Appeals require time.

Investigations require evidence.

Remedies require infrastructure.

Restoration requires people, attention, authority, and resources.

A coherent justice system may triage and prioritize when resources are finite, but it must be honest about capacity limits and must not present under-capacity process as fully functioning justice.

The failure begins when a system claims to provide justice while withholding or lacking the resources required for justice to be real.

Under-Resourced Justice occurs when the system has the form of review, appeal, accountability, remedy, protection, or restoration but not the capacity to deliver it.

The problem is not scarcity.

The problem is justice being promised or legitimized through structures that cannot carry the load assigned to them.

1. Definition

Under-Resourced Justice occurs when a justice, governance, institutional, contractual, platform, security, compliance, legal, or restoration system is formally tasked with review, accountability, enforcement, remedy, repair, appeal, protection, or legitimacy restoration but lacks the capacity, funding, staffing, time, authority, evidence access, independence, remedy power, or restoration infrastructure required to produce actual justice.

The missing resource may include:

• funding
• staffing
• review time
• case-handling capacity
• investigative authority
• enforcement authority
• remedy authority
• independence
• evidence access
• audit access
• technical tooling
• legal support
• translation support
• accessibility support
• user support
• affected-node advocacy
• restoration funding
• repair infrastructure
• compensation budget
• monitoring capacity
• escalation capacity
• appeal reviewers
• safety reviewers
• domain expertise
• implementation capacity
• recurrence-prevention infrastructure

The justice function may include:

• appeal
• investigation
• due process
• enforcement
• moderation review
• contract remedy
• grievance process
• complaint pathway
• affected-state repair
• safety correction
• restitution
• accountability
• compensation
• non-retaliation protection
• recurrence prevention
• boundary correction
• legitimacy repair
• public review
• independent oversight
• compliance enforcement

The core failure is:

justice function is promised
→ mandate exceeds resources
→ review, remedy, or repair cannot carry load
→ backlog, delay, triage, denial, or burden transfer emerges
→ affected nodes absorb the resource gap
→ hidden justice debt accumulates

Under-Resourced Justice is not merely slow justice.

It is justice whose mandate and capacity are structurally mismatched.

2. Core Pattern

The core pattern is:

1. A system creates or advertises a justice, review, appeal, remedy, or restoration pathway.
2. The pathway receives more load than it can process coherently.
3. The system lacks enough staff, authority, time, funding, evidence access, or remedy power.
4. Cases queue, delay, compress, fragment, or receive shallow review.
5. Affected nodes must wait, repeat, escalate, self-advocate, or abandon repair.
6. The system continues claiming that justice is available.
7. Process existence substitutes for effective remedy.
8. Resource scarcity shifts burden onto affected nodes.
9. The most depleted nodes are least able to access justice.
10. Hidden justice debt accumulates beneath formal availability.

A healthy system says:

justice mandate must be matched by justice capacity

An under-resourced system says:

justice is available because the process exists

The failure often hides behind good intentions.

A review team may care.

An appeal pathway may be sincere.

A grievance process may be designed for repair.

A governance body may want accountability.

A platform may want redress.

But without sufficient resources, the system cannot carry the mandate.

The result is often a justice bottleneck that converts rights into waiting rooms.

3. Failure Signature

Typical signature:

justice mandate↑
resource capacity↓
case load↑
review latency↑
appeal backlog↑
remedy delivery↓
affected-node burden↑
hidden justice debt↑
legitimacy claim↑
O↓

Extended signature:

right exists,
capacity absent

appeal exists,
review unavailable

remedy promised,
infrastructure missing

case accepted,
repair delayed

justice named,
burden transferred

Common verbal signatures include:

we are experiencing high volume
please be patient
your case is in queue
we cannot provide individual review at this time
we have limited resources
we are prioritizing severe cases
please resubmit documentation
we are working through backlog
the process is available
we are committed to accountability
we do not have capacity for deeper review
your case has been closed due to inactivity

Common system signatures include:

a platform appeal process receives too many cases for meaningful review
an institution has a grievance office without enforcement authority
a contract remedy exists but the weaker party cannot afford access
a compliance team is responsible for safety but lacks audit access
a justice process has forms and deadlines but no staff to investigate
a security review board exists but cannot compel evidence disclosure
an AI redress process exists but has no technical access to model or data causes
a government or organization creates oversight without funding it
a restorative process asks affected nodes to wait while repair capacity is absent

The defining condition is not that resources are limited.

The defining condition is that the system claims justice capacity it does not actually possess.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: justice capacity is underfunded, authority-starved, or deliberately kept weak.
• U2 — Configuration / Boundaries: review pathways are designed without enough access, authority, or remedy channels.
• U3 — Execution / Runtime: staff, reviewers, investigators, or systems cannot process load.
• U4 — Information / Truth: process existence is narrated as justice availability.
• U5 — Coordination / Time: delay becomes the main operating mode.
• U6 — Coherence Field: legitimacy is preserved through justice language despite low capacity.
• U7 — Memory / Recurrence: backlogs and failed remedies normalize as standard process.
• U8 — Environment / Field: external incentives reward creating formal justice pathways without funding them.

Common manifestation layers:

• U1 — Power: resources and authority are withheld.
• U2 — Boundaries: remedy pathways lack access to causes.
• U3 — Execution: cases bottleneck.
• U4 — Truth: availability is overstated.
• U5 — Time: delay accumulates as debt.

Under-Resourced Justice is primarily an R / Φ / K / H failure.

Restoration capacity is insufficient.

Resource flow does not match the justice mandate.

Load accumulates and becomes hidden debt.

5. Typical Development Sequence

A common development sequence is:

1. Justice, review, remedy, or restoration demand appears.
2. A formal process is created or referenced.
3. Case load grows.
4. Resources do not scale with load.
5. Review quality declines.
6. Delays grow.
7. Affected nodes must repeatedly follow up or self-advocate.
8. The system triages harshly or closes cases prematurely.
9. The most urgent or depleted cases may be least able to persist.
10. Justice debt accumulates.
11. The system cites the existence of the process as legitimacy.
12. Trust declines as lived access diverges from formal access.

The loop often looks like:

justice demand → process created → load rises → resources lag → delay → affected burden

Another common loop is:

backlog grows → review compresses → errors increase → appeals increase → backlog grows

Under-Resourced Justice becomes durable when the system treats capacity failure as user burden, claimant burden, or case-management difficulty rather than structural justice debt.

6. Diagnostic Markers

Diagnostic markers include:

• Mandates exceed staffing, funding, authority, or time.
• Case load grows faster than review capacity.
• Appeals exist but remain backlogged.
• Review quality declines under volume.
• Affected nodes must repeatedly follow up.
• Cases close because affected nodes cannot sustain participation.
• Remedy pathways lack authority to implement remedies.
• Oversight exists without enforcement power.
• Investigation exists without evidence access.
• Support exists but is unreachable.
• Deadlines bind affected nodes more than the system.
• Triage rules exclude many legitimate cases.
• Delay becomes a hidden denial mechanism.
• The system claims justice availability through process existence.

Useful diagnostics:

• Justice Capacity Adequacy: Measures whether resources match mandate.
• Resource-Mandate Match: Compares assigned justice function to available capacity.
• Case Load Saturation: Measures load relative to processing capacity.
• Appeal Backlog: Tracks unresolved appeals over time.
• Review Latency: Measures time from claim to meaningful review.
• Remedy Delivery Capacity: Tests whether remedies can actually be delivered.
• Restoration Infrastructure: Measures repair resources, authority, and implementation capacity.
• Delay Debt: Tracks burden created by waiting.
• Burden Transfer Index: Measures burden shifted to affected nodes due to resource gaps.
• Under-Resourced Legitimacy Gap: Measures gap between justice claims and justice capacity.

7. Related Gates

Relevant gates include:

• Justice Capacity Gate: Fails when the system lacks capacity to deliver justice.
• Resource-Mandate Match Gate: Fails when responsibility exceeds resources.
• Remedy Access Gate: Fails when remedies exist formally but cannot be accessed.
• Appeal Capacity Gate: Fails when appeal volume exceeds review capacity.
• Review Load Gate: Fails when load compresses review below coherence threshold.
• Restoration Capacity Gate: Fails when repair infrastructure is insufficient.
• Delay Debt Gate: Fails when delay is not counted as harm or debt.
• Burden Transfer Gate: Fails when resource gaps are shifted to affected nodes.
• Independence Gate: Fails when resource dependence compromises justice.
• Hidden Debt Gate: Fails when unresolved justice load is not counted.

The first common gate failure is usually the Resource-Mandate Match Gate.

Once a system accepts a justice mandate without sufficient resources, every later process can become a capacity illusion.

8. Related Operators

Relevant operators include:

• R — Restoration Capacity: Primary operator; justice cannot restore without capacity.
• Φ — Flow / Resource Movement: Determines whether resources reach justice functions.
• K — Constraint / Load: Case load exceeds system capacity and shifts to affected nodes.
• H — Hidden Debt: Backlog, delay, and unrepaired burden accumulate.
• O — Coherence: Declines when justice claims exceed justice capacity.
• Au — Auditability: Needed to expose capacity gaps and backlog debt.
• Τ — Trajectory / Time: Delay transforms resource scarcity into justice debt.
• Γ — Selection: Triage selects which cases survive scarcity.
• E — Exit: Affected nodes may be trapped between waiting and abandoning remedy.
• BΣ — Boundary Integrity: Resource gaps may leave violations uncorrected.
• M — Meaning: Commitment, fairness, accountability, or support language can mask under-capacity.
• Ψ — Observation / Interface: Displays available process while hiding capacity limits.
• D — Damping: Can prioritize, pace, or suppress demand.
• Λ — Compatibility: Tests whether the mandate is compatible with available resources.

Common operator pattern:

R mandate↑
Φ resources↓
K load↑
Τ delay↑
H↑
O↓

The core operator inversion is:

formal justice exists without justice capacity

instead of:

justice capacity scales with justice mandate and load

Under-Resourced Justice converts rights, remedies, and review into formal promises that cannot carry real burden.

9. Related Laws and Invariants

Related Laws

• Justice Requires Capacity: justice cannot function without resources, authority, time, and infrastructure.
• Mandates Without Resources Create Justice Debt: unfunded responsibility accumulates hidden debt.
• Remedy Must Be Resourced to Be Real: remedy without delivery capacity is theater.
• Accountability Requires Operational Capacity: accountability needs investigation, evidence, consequence, and repair channels.
• Appeal Rights Require Review Capacity: appeal exists only if review can occur.
• Justice Access Must Survive Load: justice cannot disappear at scale.
• Restoration Requires Infrastructure: repair needs more than intention.
• Under-Resourced Justice Converts Rights Into Theater: formal rights fail without operational backing.
• Procedural Theater: process can substitute for justice when capacity is absent.
• Capacity-Inverting Restoration: under-resourced systems shift capacity burden to affected nodes.
• Victim Burden Inversion: affected nodes carry proof, follow-up, and coordination when justice is underpowered.
• Restoration Starvation: restoration fails when repair capacity is withheld.

Related Invariants

• Justice Mandates Must Be Resource-Matched: duties require sufficient capacity.
• Review Capacity Must Scale With Case Load: review cannot remain coherent under overload.
• Remedy Access Must Have Operational Backing: access means usable remedy.
• Appeal Must Have Human or System Capacity to Change Outcomes: appeal without review is theater.
• Restoration Capacity Must Be Funded: repair infrastructure must exist.
• Justice Delay Must Be Counted as Debt: delay harms and must be tracked.
• Resource Gaps Must Not Be Shifted to Affected Nodes: scarcity cannot become claimant burden.
• Justice Infrastructure Must Match Enforcement Power: systems that can harm at scale need repair capacity at scale.

10. Common False Positives

Not every resource limit is Under-Resourced Justice.

Common false positives include:

• Transparent triage with repair-preserving prioritization.
• Temporary backlog with adequate surge plan.
• Limited review capacity paired with clear escalation and interim relief.
• Resource-aware justice that honestly narrows scope without overclaiming.
• Phased remedy delivery with affected-state protection during delay.
• Appeal queue with meaningful timelines and updates.
• Low-resource system that does not claim more justice than it can provide.
• Scarce resources allocated according to coherent risk and burden criteria.
• Simplified process that still repairs affected-state burden.
• Capacity limits paired with debt accounting and resource expansion plan.

Clarifying rule:

This is not Under-Resourced Justice unless a system claims or carries a justice, review, accountability, remedy, protection, or restoration mandate without the resources, authority, time, access, or infrastructure required to fulfill it.

Scarcity can be honest.

It fails when scarcity is hidden beneath justice claims.

11. Common False Repairs

Common false repairs include:

• adding more forms
• adding a portal without staffing it
• publishing response-time goals without capacity
• creating a new oversight office without authority
• creating appeal rights without reviewers
• adding escalation channels that lead to the same bottleneck
• using automation to close cases faster without repair
• triaging more harshly without debt accounting
• asking affected nodes to resubmit information
• creating dashboards that track closure rather than repair
• adding public commitment language
• outsourcing review without power to remedy
• creating advisory bodies without enforcement
• requiring patience without interim relief
• closing cases due to backlog

False repair often produces the loop:

under-resourcing exposed
→ new process announced
→ resources remain insufficient
→ backlog and burden continue

Another common loop is:

case load overwhelms review
→ review is compressed
→ errors increase
→ appeals increase
→ capacity collapses further

The repair fails because it adds process or optics without increasing justice capacity.

12. Restoration Direction

Restoration requires matching justice mandates to capacity, funding remedy infrastructure, reducing backlog debt, scaling review with load, protecting affected nodes during delay, and refusing to claim justice availability where operational capacity is absent.

Primary restoration direction:

resource justice at the level of its mandate

A fuller restoration path includes:

1. Name the justice mandate. Identify what the system claims to provide: appeal, remedy, review, enforcement, protection, accountability, or restoration.
2. Measure current load. Count cases, appeals, repair requests, investigations, unresolved harms, and recurrence risks.
3. Measure current capacity. Count staff, time, authority, funding, tooling, evidence access, and remedy infrastructure.
4. Compare mandate to capacity. Determine the resource-mandate gap.
5. Count delay debt. Treat backlog and waiting burden as justice debt.
6. Protect affected nodes during delay. Provide interim relief, safety, access, or support.
7. Reduce affected-node burden. Do not require repeated follow-up to compensate for system scarcity.
8. Increase review capacity. Add staff, authority, automation with audit, domain expertise, or independent reviewers.
9. Increase remedy capacity. Fund compensation, repair, correction, enforcement, and implementation.
10. Preserve review quality. Do not solve backlog by shallow review alone.
11. Make capacity limits explicit. Do not overclaim justice availability.
12. Prioritize by burden and risk. Triage transparently where capacity remains limited.
13. Audit recurrence from under-capacity. Track harms caused by delay or non-remedy.
14. Revalidate legitimacy. Justice claims become valid only after capacity can carry the mandate.

A valid restoration path should reduce:

resource-mandate gap
review latency
appeal backlog
remedy delivery failure
delay debt
affected-node follow-up burden
case-load saturation
under-resourced legitimacy gap
post-delay recurrence

Under-Resourced Justice is not repaired by claiming commitment.

It is repaired by giving justice the capacity to become real.

13. Cross-Module Links

• Justice: Primary family; justice fails when mandates exceed capacity.
• Contracts: Contract remedies fail when weaker parties cannot access enforcement, counsel, review, or correction.
• Restoration: Restoration requires capacity, infrastructure, time, and resources.
• False Repair: Under-resourced justice often produces procedural theater, process inflation, premature closure, and capacity-inverting restoration.
• Governance: Governance bodies may create mandates without funding or authority.
• Institutions: Institutions may advertise grievance, appeal, or accountability pathways without enough operational support.
• Platforms: Platform appeals and trust-and-safety systems can collapse under case volume.
• Security: Security redress fails when affected nodes cannot access review or boundary repair.
• AI Governance: AI harm reporting and redress require technical audit access, reviewer capacity, remedy authority, and model/data visibility.
• Compliance: Compliance mandates fail when teams lack authority or resources.
• Economy: Resource starvation converts formal rights into unusable rights.
• Coherence: Coherence requires capacity to match claims, load, and obligation.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry / Canon-Aligned

This mode maps upward to:

• FM-JC-001 — Procedural Theater
• FM-R-012 — Capacity-Inverting Restoration
• FM-R-013 — Victim Burden Inversion
• FM-S-006 — Restoration Starvation
• FM-CORE-002 — Hidden Debt Accumulation

Sibling or related Justice & Contract modes include:

• FM-JC-001 — Procedural Theater
• FM-JC-002 — Selective Enforcement
• FM-JC-003 — Punitive Drift
• FM-JC-005 — Amnesty Without Repair
• FM-JC-006 — Emergency Normalization
• FM-JC-007 — Manufactured Consent
• FM-JC-008 — Post-Signing Environmental Incoherence
• FM-JC-009 — Enforcement Capture
• FM-JC-010 — Proxy-Relay Obfuscation
• FM-JC-011 — Locked-In Renegotiation Failure
• FM-JC-012 — Parasitic Contracting

Related Restoration modes include:

• FM-R-002 — Process Inflation
• FM-R-004 — Repair Burden Externalization
• FM-R-007 — Repair Suppression via Efficiency
• FM-R-010 — Infinite Repair Loop
• FM-R-012 — Capacity-Inverting Restoration
• FM-R-013 — Victim Burden Inversion
• FM-R-019 — Premature Closure

Related cross-family modes include:

• FM-CORE-002 — Hidden Debt Accumulation
• FM-CORE-004 — Auditability Collapse
• FM-S-006 — Restoration Starvation
• FM-S-015 — Bandwidth Saturation
• FM-C-011 — Zero-Slack Collapse
• FM-C-013 — Capacity Collapse / Control Impossibility
• FM-C-027 — Drift After Recovery
• FM-ECOX-025 — Repair Starvation
• FM-AIX-023 — Civic Feedback Distortion
• FM-SEC-012 — Exit Failure / Recapture

Aliases preserved from source material:

• Under-Resourced Justice
• Justice Resource Starvation
• Justice Capacity Failure
• Unfunded Justice Mandate
• Under-Capacity Justice
• Remedy Starvation
• Accountability Capacity Failure
• Justice Without Infrastructure
• Formal Justice Without Capacity
• Justice Bottleneck Collapse
• Resource-Starved Accountability
• Underpowered Remedy System

15. Minimal Entry Version

Definition: Under-Resourced Justice occurs when a justice, governance, institutional, contractual, platform, security, compliance, legal, or restoration system is formally tasked with review, accountability, enforcement, remedy, repair, appeal, protection, or legitimacy restoration but lacks the capacity, funding, staffing, time, authority, evidence access, independence, remedy power, or restoration infrastructure required to produce actual justice.

Signature:

justice mandate↑
resource capacity↓
case load↑
review latency↑
appeal backlog↑
remedy delivery↓
affected-node burden↑
hidden justice debt↑
legitimacy claim↑
O↓

Restoration direction:

• name the justice mandate
• measure current load
• measure current capacity
• compare mandate to capacity
• count delay debt
• protect affected nodes during delay
• reduce affected-node burden
• increase review capacity
• increase remedy capacity
• preserve review quality
• make capacity limits explicit
• prioritize by burden and risk
• audit recurrence from under-capacity
• revalidate legitimacy

16. Machine-Readable Summary

failure_mode:
  id: "FM-JC-004"
  name: "Under-Resourced Justice"
  family: "Justice & Contracts"
  production_treatment: "Standalone Entry / Canon-Aligned"
  source_lineage:
    - "Justice & Contracts"
    - "JGL Extended"
    - "Restoration / Justice / Contracts Family"
  parent_modes:
    - "FM-JC-001 — Procedural Theater"
    - "FM-R-012 — Capacity-Inverting Restoration"
    - "FM-R-013 — Victim Burden Inversion"
    - "FM-S-006 — Restoration Starvation"
    - "FM-CORE-002 — Hidden Debt Accumulation"
  primary_failure: "A justice, governance, institutional, contractual, platform, security, compliance, legal, or restoration system is formally tasked with review, accountability, enforcement, remedy, repair, appeal, protection, or legitimacy restoration but lacks the capacity, funding, staffing, time, authority, evidence access, independence, remedy power, or restoration infrastructure required to produce actual justice."
  scope_note: "Conceptual and systems-oriented; does not treat every delay, backlog, resource limit, triage process, prioritization choice, simplified process, or capacity-aware enforcement decision as inherently failed."
  aliases:
    - "Under-Resourced Justice"
    - "Justice Resource Starvation"
    - "Justice Capacity Failure"
    - "Unfunded Justice Mandate"
    - "Under-Capacity Justice"
    - "Remedy Starvation"
    - "Accountability Capacity Failure"
    - "Justice Without Infrastructure"
    - "Formal Justice Without Capacity"
    - "Justice Bottleneck Collapse"
    - "Resource-Starved Accountability"
    - "Underpowered Remedy System"
  signature:
    - "justice mandate↑"
    - "resource capacity↓"
    - "case load↑"
    - "review latency↑"
    - "appeal backlog↑"
    - "remedy delivery↓"
    - "affected-node burden↑"
    - "hidden justice debt↑"
    - "legitimacy claim↑"
    - "O↓"
  primary_layers:
    origin:
      - "U1 — Power / Budgets"
      - "U2 — Configuration / Boundaries"
      - "U3 — Execution / Runtime"
      - "U4 — Information / Truth"
      - "U5 — Coordination / Time"
      - "U6 — Coherence Field"
      - "U7 — Memory / Recurrence"
      - "U8 — Environment / Field"
    manifestation:
      - "U1 — Power"
      - "U2 — Boundaries"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U5 — Time"
  state_variables:
    - "R"
    - "Φ"
    - "K"
    - "H"
    - "O"
    - "Au"
    - "Τ"
    - "Γ"
    - "E"
    - "BΣ"
    - "M"
    - "Ψ"
    - "D"
    - "Λ"
  first_gate_failure: "Resource-Mandate Match Gate"
  restoration:
    - "Justice Capacity Audit"
    - "Resource-Mandate Rebalancing"
    - "Remedy Infrastructure Buildout"
    - "Appeal Capacity Restoration"
    - "Review Load Reduction"
    - "Delay Debt Accounting"
    - "Affected-Node Burden Relief"
    - "Restoration Capacity Funding"
    - "Justice Backlog Repair"
    - "Post-Resource Justice Verification"