Archive registry entry

LAW-108 — Victim Pathway Capacity Law

Archive registry entry

LAW-108 — Victim Pathway Capacity Law

Systems fail victims when resolution pathways require high coherence, auditability, and endurance from nodes whose coherence, auditability, and endurance were damaged.

draftid: LAW-108version: 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-107 — Exposure Without Restoration Law

Registry

LAW-109 — High-Φ Legitimacy Scaling Law

0. Plain Statement

Systems fail victims when they require high coherence, auditability, and endurance from those whose coherence, auditability, and endurance were damaged.

Plain-language version:

A harmed node should not be required to carry the hardest part of the justice pathway alone.

If a resolution system requires the harmed node to repeatedly explain, prove, organize, persist, escalate, navigate complexity, tolerate delay, absorb retaliation risk, and remain perfectly coherent after harm, the pathway is structurally misdesigned.

Justice pathways must fit harmed-node capacity.

1. Formal Definition

The Victim Pathway Capacity Law states that victim-resolution, harmed-node reporting, testimony, intake, investigation, appeal, repair, and restoration pathways fail when pathway demands exceed the capacity of the harmed node.

Canonical form:

textScroll

pathway demand > harmed-node capacity ⇒ resolution failure

This law governs:

intake;
testimony;
reporting;
evidence submission;
complaint pathways;
appeals;
harmed-node support;
restoration pathways;
repair claims;
victim services;
platform reporting;
institutional grievance systems;
medical harm reporting;
security incident reporting;
workplace complaint systems;
legal and governance pathways;
AI-mediated support and representation.

A harmed node may have reduced capacity because the harm damaged:

coherence;
agency;
confidence;
boundary integrity;
resources;
memory access;
communication bandwidth;
endurance;
trust;
auditability;
social support;
material stability;
legitimacy access;
safety;
time;
attention;
ability to repeat testimony;
ability to navigate systems.

Therefore, a pathway that demands high capacity from the harmed node reproduces injustice even when formally available.

A pathway is not accessible because it exists.

A pathway is accessible only if the harmed node can actually use it without disproportionate additional debt.

2. Canonical Form

Core form:

textScroll

pathway demand > harmed-node capacity ⇒ resolution failure

Capacity-fit form:

textScroll

resolution_pathway valid when pathway_demand ≤ harmed_node_capacity + support_capacity

Burden inversion form:

textScroll

harm damages capacity; bad pathways demand the damaged capacity back

Failure form:

textScroll

testimony_load + delay + friction + proof_burden > harmed_node_capacity ⇒ pathway collapse

Restoration-valid contrast:

textScroll

victim pathway valid when support lowers demand, protects agency, and increases harmed-node O over Τ

Related variables:

textScroll

O, H, ε, ι, Au, Au_eff, µᵢ, BΣ, K, σ, R, R_eff, 𝓑, 𝓓, Φ, Λ, ⊗, Γ, Π, Ξ, ℛ, Θ, Σ, Ψ, Τ, FI, MS, L, harmed_node_capacity, pathway_demand, support_capacity, testimony_load, reporting_load, intake_friction, proof_burden, delay_cost, retaliation_risk, resolution_probability, agency, harmed_node_O

Where:

TableScroll

Variable	Meaning in this law
`harmed_node_capacity`	Capacity available to affected nodes after harm
`pathway_demand`	Total load imposed by the resolution pathway
`support_capacity`	Capacity supplied to help the harmed node navigate the pathway
`testimony_load`	Demand created by telling, retelling, documenting, or defending the account
`reporting_load`	Demand created by forms, portals, calls, escalation, evidence, and follow-up
`intake_friction`	Barriers at the first point of access
`proof_burden`	Burden placed on the harmed node to establish harm, causality, responsibility, or eligibility
`delay_cost`	Additional debt created by time between harm and resolution
`retaliation_risk`	Risk of punishment, backlash, disbelief, exposure, exclusion, or further harm
`resolution_probability`	Likelihood that the pathway produces coherent repair
`agency`	Harmed-node ability to choose, refuse, participate, pause, exit, and influence repair
`harmed_node_O`	Coherence of the harmed node across the pathway
`R / R_eff`	Restoration capacity of the pathway and supporting system
`𝓑`	Bandwidth headroom required for processing and participation
`𝓓`	Damping needed so pathway participation does not destabilize the harmed node
`BΣ`	Boundary integrity, safety, privacy, consent, and scope protections
`Au / Au_eff`	Auditability of the pathway without overloading the harmed node
`FI`	Feedback integrity; harmed-node feedback must actually change pathway behavior
`MS`	Moral / meaning symmetry; standards and burden must not invert against harmed nodes
`L`	Legitimacy of the pathway and justice system
`H`	Hidden debt accumulated when harmed nodes cannot access resolution
`ι / Ξ`	Inversion when the pathway treats harmed-node capacity damage as noncompliance or weakness
`Φ`	Existence of a formal pathway or closure metric; not sufficient proof of accessibility
`Γ`	Classifies harmed-node capacity, pathway demand, support need, proof burden, and repair obligation
`Π`	Operationalizes intake, reporting, testimony, support, triage, review, appeal, and repair
`ℛ`	Restoration that reduces harmed-node debt and increases coherence
`Θ`	Humility preventing pathway designers from assuming capacity they have not measured
`Σ`	Scope of pathway, eligibility, burden, and repair obligation
`Ψ`	Affected-node feedback validating pathway usability
`Τ`	Time validation of resolution and harmed-node coherence

3. Core Mechanism

The law unfolds because harm often reduces the exact capacities that systems demand for resolution.

Coherent victim pathway

textScroll

harm occurs
→ harmed-node capacity is assessed
→ pathway demand is reduced
→ support capacity is supplied
→ testimony and proof burden are minimized
→ safety and boundaries are protected
→ repair proceeds
→ harmed-node coherence rises over time

Pathway collapse pathway

textScroll

harm occurs
→ harmed-node capacity decreases
→ pathway requires high endurance / proof / repetition
→ delay and friction accumulate
→ harmed node exits or fails pathway
→ harm remains unresolved
→ hidden debt and legitimacy debt rise

The core mechanism is:

textScroll

a pathway fails when it demands the capacity the harm damaged

Detailed mechanism:

A harmed node experiences coherence damage.

Harm may reduce agency, clarity, energy, resources, social support, trust, boundary integrity, or ability to participate.

The system offers a pathway.

The pathway may include reporting, testimony, documentation, investigation, appeal, repair, enforcement, or restoration.

The pathway imposes load.

The harmed node may be required to initiate, explain, prove, repeat, escalate, withstand delay, and tolerate uncertainty.

If pathway demand exceeds capacity, resolution fails.

The harmed node may withdraw, be disbelieved, miss deadlines, lose coherence, lose access, or accept false closure.

Failure becomes hidden debt.

The system may mark the pathway as available while harmed nodes cannot use it coherently.

Coherent design supplies capacity and lowers demand.

The pathway becomes usable when support, pacing, advocacy, protection, clear interfaces, evidence assistance, and repair logistics reduce the burden.

Time validates the pathway.

A victim pathway works when harmed-node coherence improves and recurrence decreases over time.

4. When This Law Applies

This law applies whenever a harmed node must access a pathway to receive repair, justice, support, correction, appeal, representation, protection, compensation, restoration, or recurrence prevention.

It is especially important when:

reporting is difficult;
testimony must be repeated;
proof burden is high;
forms and portals are complex;
deadlines are strict;
harmed nodes must self-advocate;
resolution requires persistence;
retaliation risk exists;
evidence is hard to preserve;
pathway language is unclear;
appeals are burdensome;
support is absent;
staff are overloaded;
outcomes depend on perfect documentation;
harmed-node feedback is treated as noise;
complaint systems exist but are rarely usable;
AI, platform, medical, workplace, school, legal, institutional, or governance systems claim accessible resolution.

The law applies strongly when:

textScroll

resolution requires more capacity than the harmed node has after harm

or when:

textScroll

formal pathway existence is mistaken for actual pathway accessibility

Typical domains:

TableScroll

Domain	Victim Pathway Capacity Expression
AI systems	Users harmed by AI decisions need appeal, correction, explanation, rollback, and repair pathways that do not require expert-level persistence.
Security	Incident victims need support, recovery, identity repair, account recovery, evidence handling, and clear remediation without excessive burden.
Institutions	Complaint and grievance systems must reduce harmed-node burden rather than demand endurance.
Medicine / biology	Harm reporting and care correction must account for reduced capacity, pain, fatigue, uncertainty, and access barriers.
Economy	Contract, debt, labor, fraud, and consumer harm pathways fail when access requires resources the harmed node lacks.
Governance	Legal and administrative pathways must not require harmed nodes to carry impossible proof, time, or cost burdens.
Culture	Community repair pathways must preserve dignity, agency, boundary, and voice without forcing repeated exposure.
Restoration	Restoration must protect harmed-node capacity while repairing debt and preventing recurrence.

5. When This Law Does Not Apply

This law should not be used to remove all responsibility, evidence, process, or discernment from justice pathways.

A pathway still requires truth, auditability, fairness, and coherent classification.

The law says the system must not offload excessive burden onto the damaged node.

False-positive cases:

TableScroll

Case	Why pathway demand may still be needed
Some evidence is required	Evidence can be necessary, but the system should assist collection and avoid excessive burden
Multiple accounts conflict	Careful classification is needed without punishing harmed-node limitations
Safety requires review	Review can be valid if support and pacing are provided
False claims are possible	Audit remains necessary, but proof burden should not invert into harmed-node overcapacity
The harmed node cannot participate fully	Supported representation, pacing, or alternate pathways may be needed
Confidentiality limits disclosure	Limits can be coherent if explained and paired with audit
Pathway must prioritize urgent cases	Triage is valid if transparent and capacity-aware

Important distinction:

Capacity-aware pathways preserve auditability; they do not erase auditability.

6. Diagnostic Signature

Canonical diagnostic:

textScroll

pathway demand > harmed-node capacity ⇒ resolution failure

Warning signature:

textScroll

reporting friction↑
testimony repetition↑
proof burden↑
delay↑
support↓
retaliation risk↑
harmed-node capacity↓
⇒ victim pathway collapse

Common indicators:

TableScroll

Diagnostic	Expected movement	Interpretation
`harmed_node_capacity`	assessed, protected	Pathway must fit available capacity
`pathway_demand`	should decrease	Pathway demand should not exceed harmed-node ability
`support_capacity`	should increase	System supplies capacity rather than extracting it
`testimony_load`	should decrease	Repetition and burden should be minimized
`reporting_load`	should decrease	Access and documentation should be simplified
`intake_friction`	should decrease	First contact should be usable
`proof_burden`	should be balanced	Auditability must not become burden inversion
`delay_cost`	should decrease	Delay creates additional debt
`retaliation_risk`	should decrease	Pathways must protect participants
`resolution_probability`	should increase	Usable pathways produce actual resolution
`agency`	should increase	Harmed node gains choice and influence
`harmed_node_O`	should increase	Pathway supports coherence
`L`	↑ if valid	Legitimacy rises when pathways are usable
`H`	↑ if invalid	Hidden debt rises when pathways exist but fail
`Φ`	not sufficient	A hotline, form, portal, or policy is not proof of access
`Τ`	required	Time validates usability and repair

Additional diagnostics:

TableScroll

Diagnostic	Use
Victim Pathway Capacity	Tests whether resolution pathway fits harmed-node capacity
Harmed-Node Capacity	Measures available coherence, bandwidth, resources, and endurance
Pathway Demand	Measures total load imposed by resolution
Resolution Burden	Tracks burden placed on harmed nodes
Testimony Load	Detects repeated exposure or explanation burden
Reporting Load	Detects access and documentation burden
Intake Friction	Detects failure at first contact
Auditability Burden	Detects proof burden shifted to harmed node
Endurance Demand	Detects delay and persistence requirements
Support Sufficiency	Tests whether system supplies capacity
Temporal Proof	Validates resolution over time

7. Failure Pattern

If ignored, this law lets systems claim pathways exist while harmed nodes cannot use them.

General failure pathway:

textScroll

harm occurs
→ capacity decreases
→ pathway demands high coherence / proof / endurance
→ harmed node cannot carry demand
→ pathway exits, stalls, or closes
→ system records non-completion as user failure
→ hidden debt persists
→ legitimacy decays

Common failure modes:

Victim Pathway Collapse — harmed nodes cannot complete resolution pathway.
Harmed-Node Overload — pathway demands exceed damaged capacity.
Resolution Burden Shift — system shifts repair labor onto the harmed node.
Testimony Extraction — harmed node repeatedly supplies experience without receiving repair.
Reporting Exhaustion — forms, portals, calls, and escalation consume capacity.
Intake Friction Failure — harmed nodes fail before the pathway begins.
Proof Burden Inversion — harmed node must prove what system audit should help establish.
Auditability Burden Transfer — audit responsibility is displaced onto the affected node.
Procedural Retraumatization — pathway participation compounds coherence damage.
Pathway Abandonment — harmed node exits due to overload, delay, or disbelief.
Silencing by Complexity — procedural complexity suppresses feedback.
False Closure — unresolved harm is recorded as completed, declined, or unsupported.
Legitimacy Debt — trust decays because pathways fail under actual harmed-node capacity.
Recurrence Persistence — harm repeats because resolution pathway never repairs origin conditions.
Restoration Failure — support, repair, and prevention do not activate.

Compact failure signature:

textScroll

pathway_demand↑ + harmed_node_capacity↓ + support↓ ⇒ H↑ + L↓

8. Restoration Implications

Restoration requires redesigning pathways around harmed-node capacity.

The first restoration question is not:

textScroll

Is there a pathway?

The first restoration question is:

textScroll

Can the harmed node actually use this pathway without carrying more demand than their damaged capacity can support?

Restoration priorities:

Assess harmed-node capacity.
Measure pathway demand.
Reduce intake friction.
Reduce testimony repetition.
Rebalance proof burden.
Provide support capacity.
Protect boundaries and privacy.
Reduce retaliation risk.
Preserve agency and choice.
Improve pathway throughput and follow-through.
Validate harmed-node coherence over time.

Relevant restoration arcs:

TableScroll

Restoration Arc	Why it applies
Victim Pathway Redesign	Rebuilds pathways around actual harmed-node capacity
Harmed-Node Capacity Protection	Prevents resolution from consuming damaged capacity
Pathway Demand Reduction	Lowers burden to usable levels
Testimony Load Reduction	Reduces repetition and extraction
Intake Friction Repair	Makes first access point usable
Support Sufficiency Increase	Supplies capacity to navigate resolution
Audit Burden Rebalancing	Prevents proof burden inversion
Agency Restoration	Restores harmed-node choice and participation
Boundary Reconstitution	Protects privacy, consent, safety, and scope
Repair Sufficiency Increase	Ensures pathway leads to actual repair
Feedback Integrity Restoration	Makes harmed-node feedback actionable
Temporal Validation	Confirms pathway improves coherence over time

Minimal restoration sequence:

textScroll

assess harmed_node_capacity
→ measure pathway_demand
→ reduce friction / testimony / proof burden
→ add support_capacity
→ protect BΣ + agency
→ perform ℛ
→ validate harmed_node_O and L over Τ

Temporal validation requirement:

textScroll

pathway demand decreases
support capacity increases
harmed-node agency improves
testimony load decreases
retaliation risk decreases
repair proceeds
harmed-node coherence rises
pathway abandonment decreases
recurrence decreases
legitimacy stabilizes over time

9. Design Rule

Design victim pathways so harmed-node capacity is protected, not consumed.

Operational design requirements:

Measure harmed-node capacity.
Measure pathway demand.
Design intake for low friction.
Minimize repeated testimony.
Avoid requiring perfect coherence from harmed nodes.
Provide advocacy, translation, technical support, and navigation support where needed.
Preserve choice, consent, privacy, and pacing.
Rebalance proof burden toward system audit where possible.
Protect against retaliation.
Provide status visibility.
Provide appeal and correction pathways.
Provide repair, not just case handling.
Track pathway abandonment as failure signal.
Track harmed-node coherence over time.
Validate recurrence prevention.

Avoid:

forms as access theater;
hotlines without follow-through;
portals that require expert navigation;
repeated retelling without repair;
long delays without support;
proof demands that exceed damaged capacity;
treating non-completion as lack of harm;
treating silence as resolution;
requiring harmed nodes to become investigators;
requiring harmed nodes to remain perfectly composed;
exposing harmed nodes without boundary protection;
AI appeal systems that require users to reverse-engineer the model;
institutional pathways that protect the institution from feedback;
justice systems that convert harmed-node exhaustion into closure metrics.

10. Cross-Scale Expressions

TableScroll

Scale / Layer	Expression of the Law
U0 — Substrate	Harmed-node body, material condition, and basic capacity must be protected during resolution.
U1 — Energy / capacity	Reporting, testimony, travel, cost, time, and persistence consume energy and slack.
U2 — Boundary / interface	Pathways must protect privacy, consent, access, safety, pacing, and exit.
U3 — Process / execution	Intake, reporting, investigation, support, repair, and appeal must be usable under damaged capacity.
U4 — Classification / claim	Systems must not misclassify capacity damage as noncompliance or unreliability.
U5 — Time / delay	Delay increases burden and can convert pathways into hidden denial.
U6 — Field effect	Harmed-node outcomes reveal whether the pathway works beyond formal existence.
U7 — Recurrence / memory	Pathways must encode lessons so harmed nodes do not need to repeat the same burden.
U8 — Environment / forcing	Institutions, markets, platforms, AI systems, media, and legal systems shape harmed-node access to repair.

11. Examples

Example A — Reporting Portal That Fails Users

Scenario:

A platform provides a reporting portal, but users must submit extensive evidence, navigate unclear categories, repeat the issue across tickets, and wait without status visibility.

Law expression:

textScroll

formal pathway + pathway_demand > user_capacity ⇒ resolution failure

Interpretation:

The pathway exists, but its demand exceeds the harmed node’s usable capacity.

Example B — Workplace Complaint System

Scenario:

A harmed employee must document every event, confront retaliation risk, repeat testimony to multiple parties, and keep working under the same conditions while waiting for resolution.

Law expression:

textScroll

testimony_load + retaliation_risk + delay_cost > harmed_node_capacity

Interpretation:

The pathway shifts resolution burden onto the harmed node.

Example C — AI Appeal Burden

Scenario:

An AI system denies access, flags content, changes ranking, or makes an automated decision. The user must infer the reason, collect evidence, appeal through opaque forms, and repeat the case without explanation.

Law expression:

textScroll

AI decision + opaque appeal ⇒ auditability burden transfer

Interpretation:

AI appeal pathways fail when users must reverse-engineer the system to seek repair.

Example D — Medical Harm Reporting

Scenario:

A patient harmed by a care process must navigate complex forms, medical language, fragmented offices, long delays, and unclear responsibility while still needing care.

Law expression:

textScroll

care harm + pathway friction↑ ⇒ harmed-node O↓

Interpretation:

Resolution must account for the reduced capacity created by the harm itself.

Example E — Legal Pathway With Cost Barrier

Scenario:

A person has a formal legal right but cannot afford counsel, time off, filing costs, evidence gathering, or procedural navigation.

Law expression:

textScroll

formal right + capacity barrier ⇒ inaccessible justice

Interpretation:

Formal availability is not pathway accessibility.

Example F — Coherent Harmed-Node Pathway

Scenario:

A system provides simple intake, supported documentation, privacy protections, clear status, one-account testimony, advocate support, bounded timelines, repair options, appeal, and recurrence prevention.

Law expression:

textScroll

support_capacity↑ + pathway_demand↓ ⇒ harmed_node_O↑ + L↑

Interpretation:

The pathway protects capacity and improves resolution.

12. Relationship to Nearby Laws

TableScroll

Related Law	Relationship
LAW-001 — Coherence Priority Law	Victim pathways are valid when harmed-node coherence improves
LAW-002 — Coherence Trajectory Law	Pathways must improve trajectory over time
LAW-004 — Stability-Coherence Separation Law	A closed case may not indicate coherence
LAW-006 — Time Validation Law	Pathway success requires temporal validation
LAW-010 — Hidden Debt Accumulation Law	Failed pathways accumulate hidden justice debt
LAW-011 — Hidden Debt Return Law	Unresolved harm returns through recurrence
LAW-012 — Error Lag Law	Pathway collapse often appears after delayed burden accumulation
LAW-013 — Auditability-Debt Law	Auditability must not be offloaded entirely to harmed nodes
LAW-015 — Suppressed Auditability Debt Law	Suppressed audit creates burden for harmed nodes to prove the system’s debt
LAW-017 — Silent Extraction Law	Testimony extraction can become silent extraction
LAW-020 — Bandwidth Threshold Law	Harmed-node bandwidth may be below pathway demand
LAW-023 — Restoration Capacity Load Law	Pathways require restoration capacity proportional to load
LAW-029 — Integration Cost Law	Participating in resolution has real cost
LAW-030 — Slack Sovereignty Law	Harmed nodes need slack to participate without further debt
LAW-041 — Boundary Membrane Law	Pathways must protect boundary integrity
LAW-042 — Consent Structurality Law	Participation must preserve meaningful choice and consent
LAW-048 — Feedback Integrity Law	Harmed-node feedback must change the pathway
LAW-049 — Feedback Without Slack Becomes Extraction Law	Asking for testimony without support extracts from damaged capacity
LAW-052 — Stability Proof Law	Pathways must remain usable under stress
LAW-061 — Restoration Sequencing Law	Pathway steps must be sequenced around capacity
LAW-064 — Restoration Debt Reduction Law	Pathways must reduce debt, not merely process claims
LAW-065 — Pseudo-Restoration Law	Formal support without repair becomes pseudo-restoration
LAW-066 — Restoration Capacity Sufficiency Law	Support capacity must be sufficient for harmed-node need
LAW-067 — Temporal Proof Law	Pathway success must hold over time
LAW-068 — Boundary-First Restoration Law	Safety and privacy often precede testimony and repair
LAW-071 — No Forced Forgiveness Law	Pathways must not demand closure or forgiveness before repair
LAW-072 — Quiet Minimization Debt Law	Minimizing harmed-node burden creates debt
LAW-075 — Capacity Before Demand Law	LAW-108 specializes capacity-before-demand for harmed-node pathways
LAW-102 — Legitimacy Audit Law	Legitimacy depends on usable pathways for affected observers
LAW-103 — Justice Stability Law	Justice fails when victim pathways collapse
LAW-104 — Justice Logistics Law	Victim pathway capacity is a core justice logistics requirement
LAW-105 — Repair Before Enforcement Law	Enforcement must not replace harmed-node repair pathways
LAW-106 — Exposure Legibility Law	Exposure often depends on harmed-node reporting
LAW-107 — Exposure Without Restoration Law	Exposure can overburden harmed nodes without support
LAW-109 — High-Φ Legitimacy Scaling Law	High-influence actors require stronger harmed-node pathways
LAW-110 — Governance Sequencing Law	Governance must sequence intake, support, audit, repair, and prevention
LAW-111 — Meaning Audit Law	Victim-pathway narratives are not audit-exempt
LAW-115 — Surveillance–Restoration Law	Detection must route into harmed-node support and repair
LAW-120 — Security Legibility Law	Harmed-node security claims require traceable pathways
LAW-128 — AI Representation Law	AI representing harmed nodes requires continuous auditability and scope clarity
LAW-132 — AI Legitimacy Function Law	AI legitimacy depends on usable affected-user repair pathways
LAW-133 — Error Scale Law	Large-scale systems generate many harmed nodes even at low error rates
LAW-134 — Layered Interception Law	Layered safeguards reduce harmed-node pathway overload
LAW-147 — Economic Contract State-Space Law	Formal consent or contract may fail if harmed-node pathway capacity is absent

Aliases folded into this law:

Victim Pathway Capacity Law
Harmed-Node Capacity Law
Pathway Demand Capacity Law
Resolution Pathway Capacity Law
Victim Resolution Capacity Law
Harmed-Node Overload Law
Pathway Demand Exceeds Capacity Law

Deduplication note:

This law should remain the root harmed-node pathway capacity law. LAW-075 states the broader capacity-before-demand rule. LAW-104 defines justice logistics generally. LAW-107 governs exposure without restoration. LAW-108 specializes those constraints for victim-resolution pathways, intake, testimony, reporting, and repair.

13. Operator Mapping

TableScroll

Operator	Role in this law
`Γ`	Classifies harmed-node capacity, pathway demand, support need, proof burden, risk, and repair obligation
`Π`	Operationalizes intake, testimony, reporting, support, triage, audit, appeal, repair, and prevention
`Ξ`	Captures inversion when pathways treat harmed-node capacity damage as failure, noncompliance, or unreliability
`⊗`	Pathway creates coupling between harmed node, institution, evidence, authority, and repair system
`ℛ`	Performs repair and reduces harmed-node burden, hidden debt, and recurrence risk
`Τ`	Validates whether the pathway improves harmed-node coherence over time
`Θ`	Prevents designers from assuming capacity, blaming withdrawal, or mistaking formal access for usability
`Σ`	Defines pathway scope, eligibility, burden, privacy, and repair obligation
`Ψ`	Harmed-node and field feedback validates pathway usability
`Λ`	Tests compatibility between pathway design and harmed-node coherence

Coherent operator sequence:

textScroll

harm occurs
→ Θ prevent capacity assumptions
→ Γ assess harmed_node_capacity + pathway_demand
→ Σ define pathway scope and protections
→ Π reduce friction / testimony / proof burden
→ add support_capacity
→ Au/FI preserve audit and feedback
→ ℛ perform repair
→ Ψ validate harmed-node effects
→ Τ validate harmed_node_O and L over time

Inverted operator sequence:

textScroll

harm occurs
→ capacity decreases
→ pathway demand remains high
→ Γ misreads overload as noncompliance
→ Π requires repetition / proof / delay endurance
→ harmed node exits or collapses
→ ℛ fails
→ H↑
→ Ξ / ι↑
→ L↓

14. Machine-Readable Summary

yamlScroll

id: "LAW-108"
name: "Victim Pathway Capacity Law"
type: "law"
status: "draft"
family:
  - "Justice, Governance, and Legitimacy Laws"
summary: "Systems fail victims when resolution pathways require high coherence, auditability, and endurance from nodes whose coherence, auditability, and endurance were damaged."
canonical_statement: "Systems fail victims when they require high coherence, auditability, and endurance from those whose coherence, auditability, and endurance were damaged."
core_form: "pathway demand > harmed-node capacity ⇒ resolution failure"
capacity_fit_form: "resolution_pathway valid when pathway_demand ≤ harmed_node_capacity + support_capacity"
burden_inversion_form: "harm damages capacity; bad pathways demand the damaged capacity back"
failure_form: "testimony_load + delay + friction + proof_burden > harmed_node_capacity ⇒ pathway collapse"
restoration_valid_contrast: "victim pathway valid when support lowers demand, protects agency, and increases harmed-node O over Τ"
variables:
  primary:
    - "harmed_node_capacity"
    - "pathway_demand"
    - "support_capacity"
    - "testimony_load"
    - "reporting_load"
    - "intake_friction"
    - "proof_burden"
    - "delay_cost"
    - "retaliation_risk"
    - "resolution_probability"
    - "agency"
    - "harmed_node_O"
    - "R"
    - "R_eff"
    - "BΣ"
    - "Au"
    - "Au_eff"
    - "FI"
    - "L"
    - "H"
  secondary:
    - "O"
    - "ε"
    - "ι"
    - "µᵢ"
    - "K"
    - "σ"
    - "𝓑"
    - "𝓓"
    - "Φ"
    - "Λ"
    - "⊗"
    - "Γ"
    - "Π"
    - "Ξ"
    - "ℛ"
    - "Θ"
    - "Σ"
    - "Ψ"
    - "Τ"
    - "MS"
diagnostics:
  - "Victim Pathway Capacity"
  - "Harmed-Node Capacity"
  - "Pathway Demand"
  - "Resolution Burden"
  - "Testimony Load"
  - "Reporting Load"
  - "Intake Friction"
  - "Auditability Burden"
  - "Endurance Demand"
  - "Support Sufficiency"
  - "Repair Sufficiency"
  - "Feedback Integrity"
  - "Legitimacy"
  - "Temporal Proof"
failure_modes:
  - "Victim Pathway Collapse"
  - "Harmed-Node Overload"
  - "Resolution Burden Shift"
  - "Testimony Extraction"
  - "Reporting Exhaustion"
  - "Intake Friction Failure"
  - "Proof Burden Inversion"
  - "Auditability Burden Transfer"
  - "Procedural Retraumatization"
  - "Pathway Abandonment"
  - "Silencing by Complexity"
  - "False Closure"
  - "Legitimacy Debt"
  - "Recurrence Persistence"
  - "Restoration Failure"
restoration_arcs:
  - "Victim Pathway Redesign"
  - "Harmed-Node Capacity Protection"
  - "Pathway Demand Reduction"
  - "Testimony Load Reduction"
  - "Intake Friction Repair"
  - "Support Sufficiency Increase"
  - "Audit Burden Rebalancing"
  - "Agency Restoration"
  - "Boundary Reconstitution"
  - "Repair Sufficiency Increase"
  - "Feedback Integrity Restoration"
  - "Temporal Validation"
related_laws:
  - "LAW-001"
  - "LAW-002"
  - "LAW-004"
  - "LAW-006"
  - "LAW-010"
  - "LAW-011"
  - "LAW-012"
  - "LAW-013"
  - "LAW-015"
  - "LAW-017"
  - "LAW-020"
  - "LAW-023"
  - "LAW-029"
  - "LAW-030"
  - "LAW-041"
  - "LAW-042"
  - "LAW-048"
  - "LAW-049"
  - "LAW-052"
  - "LAW-061"
  - "LAW-064"
  - "LAW-065"
  - "LAW-066"
  - "LAW-067"
  - "LAW-068"
  - "LAW-071"
  - "LAW-072"
  - "LAW-075"
  - "LAW-102"
  - "LAW-103"
  - "LAW-104"
  - "LAW-105"
  - "LAW-106"
  - "LAW-107"
  - "LAW-109"
  - "LAW-110"
  - "LAW-111"
  - "LAW-115"
  - "LAW-120"
  - "LAW-128"
  - "LAW-132"
  - "LAW-133"
  - "LAW-134"
  - "LAW-147"
related_invariants:
  - "INV-001"
  - "INV-002"
  - "INV-006"
  - "INV-073"
  - "INV-080"
operator_sequence:
  coherent:
    - "harm occurs"
    - "Θ prevent capacity assumptions"
    - "Γ assess harmed_node_capacity + pathway_demand"
    - "Σ define pathway scope and protections"
    - "Π reduce friction / testimony / proof burden"
    - "add support_capacity"
    - "Au/FI preserve audit and feedback"
    - "ℛ perform repair"
    - "Ψ validate harmed-node effects"
    - "Τ validate harmed_node_O and L over time"
  inverted:
    - "harm occurs"
    - "capacity decreases"
    - "pathway demand remains high"
    - "Γ misreads overload as noncompliance"
    - "Π requires repetition / proof / delay endurance"
    - "harmed node exits or collapses"
    - "ℛ fails"
    - "H↑"
    - "Ξ / ι↑"
    - "L↓"
aliases:
  - "Victim Pathway Capacity Law"
  - "Harmed-Node Capacity Law"
  - "Pathway Demand Capacity Law"
  - "Resolution Pathway Capacity Law"
  - "Victim Resolution Capacity Law"
  - "Harmed-Node Overload Law"
  - "Pathway Demand Exceeds Capacity Law"
deduplication_note: "Root harmed-node pathway capacity law. LAW-075 states the broader capacity-before-demand rule. LAW-104 defines justice logistics generally. LAW-107 governs exposure without restoration. LAW-108 specializes those constraints for victim-resolution pathways, intake, testimony, reporting, and repair."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-108 — Victim Pathway Capacity Law

Systems fail victims when they require high coherence, auditability, and endurance from those whose coherence, auditability, and endurance were damaged.

Core form:

textScroll

pathway demand > harmed-node capacity ⇒ resolution failure

Capacity-fit form:

textScroll

resolution_pathway valid when pathway_demand ≤ harmed_node_capacity + support_capacity

Plain meaning:

A harmed node should not be required to carry the hardest part of the justice pathway alone. If a system requires repeated testimony, high proof burden, persistence, complex navigation, delay endurance, and retaliation risk from a damaged node, the pathway is structurally misdesigned.

Burden inversion form:

textScroll

harm damages capacity; bad pathways demand the damaged capacity back

Failure form:

textScroll

testimony_load + delay + friction + proof_burden > harmed_node_capacity ⇒ pathway collapse

Primary variables:

harmed_node_capacity, pathway_demand, support_capacity, testimony_load, reporting_load, intake_friction, proof_burden, delay_cost, retaliation_risk, resolution_probability, agency, harmed_node_O, R, R_eff, BΣ, Au, Au_eff, FI, L, H, Γ, Π, ℛ, Θ, Σ, Ψ, Τ

Diagnostic signature:

Reporting friction rises, testimony repetition rises, proof burden rises, delay increases, support decreases, retaliation risk rises, and harmed-node capacity falls. This indicates victim pathway collapse.

Failure risk:

Victim pathway collapse, harmed-node overload, resolution burden shift, testimony extraction, reporting exhaustion, intake friction failure, proof burden inversion, auditability burden transfer, procedural retraumatization, pathway abandonment, silencing by complexity, false closure, legitimacy debt, recurrence persistence, restoration failure.

Restoration priority:

Assess harmed-node capacity, measure pathway demand, reduce intake friction, reduce testimony repetition, rebalance proof burden, provide support capacity, protect boundaries and privacy, reduce retaliation risk, preserve agency, perform repair, and validate harmed-node coherence over time.

LAW-107 — Exposure Without Restoration Law

Registry

LAW-109 — High-Φ Legitimacy Scaling Law