Jump Through This Page
1. Purpose
The Victim Resolution Pathway System maps whether a harmed or burdened node can reach safety, truth, recognition, repair, and restoration without the pathway itself becoming another burden.
VRPS exists because many resolution systems formally provide a path, but the path may be too costly, unsafe, opaque, slow, retaliatory, or inaccessible for the harmed node to use coherently.
A pathway can exist on paper while failing in state-space reality.
VRPS asks:
textScroll
Can the harmed node reach safety, truth, repair, and restoration
without being re-burdened by the resolution pathway?The Constructs & Operating Systems Registry identifies VRPS as a justice / restoration framework that formalizes how individuals harmed under power asymmetry attempt to reach safety, justice, and repair, and why existing systems often fail them.
2. Core Question
Can a harmed or burdened node reach safety, recognition, truth, repair, and restoration without the resolution process transferring additional burden back onto that node?
Secondary questions:
- Is the harmed node currently safe?
- Is truth accessible?
- Is recognition available before excessive proof burden?
- What must the node disclose to be believed?
- What evidence burden does the pathway impose?
- Can the harmed node access repair without retaliation?
- Does the process protect the institution more than the harmed node?
- Is the pathway asking for capacities the harm already damaged?
- Does the process reduce recurrence?
- Is resolution being claimed without restoration?
- Does the pathway preserve dignity, boundaries, and agency?
- Is ∅ more coherent than forcing a harmful pathway?
3. Construct Class
TableScroll
| Field | Value |
|---|---|
| Construct Class | Justice / Restoration Workflow |
| Secondary Class | Harm Resolution / Pathway Viability / Burden Mapping System |
| Operating System | No |
| Primary Module | Justice · Governance · Legitimacy / Restoration |
| Related Modules | Coherence, Security, Principles, AI Governance, ISC |
VRPS is a workflow because it maps the sequence by which a harmed node attempts to move from harm toward resolution.
It is also a justice construct because it evaluates whether the pathway distributes burden, truth, safety, and responsibility coherently.
4. When to Use
Use the Victim Resolution Pathway System when a harmed, burdened, misclassified, exploited, or affected node is expected to navigate a reporting, appeal, complaint, justice, repair, or restoration process.
Use VRPS when:
- a harmed node must disclose harm to receive help
- a reporting pathway may be unsafe
- evidence burden is high
- institutional response may protect itself first
- retaliation risk exists
- appeal or repair requires too much capacity from the affected node
- harmed nodes repeatedly abandon the pathway
- the process claims resolution without burden reduction
- a complaint process produces procedural closure but not repair
- the pathway makes the harmed node responsible for making the harm legible
- safety, recognition, truth, repair, and restoration are not sequenced correctly
- recurrence continues after formal resolution
- power asymmetry distorts access to justice
Do not use VRPS as the primary construct when the central question is:
TableScroll
| If the question is... | Prefer... |
|---|---|
| What is the affected node experiencing? | Empathy Interface |
| How should a repair interaction be sequenced? | Restorative Interaction Template |
| Is an institution drifting over time? | ICTE |
| Is accountability symmetrical? | Equality-Conserving Accountability |
| Can a role or node be reintegrated safely? | Reintegration Membrane |
| What restoration arc applies? | RAM |
| What failure mode is active? | FMM |
VRPS focuses specifically on the viability of the resolution pathway.
5. Derivation
VRPS is derived from a recurring UTS pattern:
textScroll
harm occurs
+ harmed node must seek resolution
+ resolution pathway requires high disclosure, evidence, time, risk, or capacity
+ pathway burden exceeds harmed-node capacity
= pathway collapseA second pattern:
textScroll
institution offers formal process
+ process protects institutional legitimacy
+ harmed node remains unsafe or unrepaired
= resolution theaterA third pattern:
textScroll
repair requires the harmed node to prove, explain, stabilize, and persist
+ the harm itself reduced those capacities
= burden inversionVRPS exists because access to a pathway is not the same as access to resolution.
Its core distinction is:
textScroll
formal pathway is not restorative pathway6. UTS Basis
VRPS assembles the following UTS mechanics.
6.1 State Variables
TableScroll
| Variable | Role in VRPS |
|---|---|
| O | Measures whether the pathway restores or degrades coherence. |
| H | Tracks hidden burden created by disclosure, evidence, delay, retaliation, or procedural exhaustion. |
| ε | Tracks uncertainty, ambiguity, missing evidence, or unresolved truth access. |
| ι | Detects inversion where a resolution pathway protects the harming structure. |
| Au | Measures traceability of harm, response, responsibility, and repair. |
| µᵢ | Preserves affected-node meaning, dignity, identity, and standing. |
| BΣ | Maintains safety, role, privacy, consent, and pathway boundaries. |
| K | Tracks compatibility between pathway demands and harmed-node capacity. |
| R | Measures restoration capacity available to the harmed node. |
| Φ | Tracks power asymmetry, institutional force, retaliation risk, and authority pressure. |
6.2 Primary U-Layer Pattern
VRPS most commonly localizes through:
textScroll
U1 → U2 → U3 → U6 → U5 → U7Meaning:
textScroll
power asymmetry
→ pathway boundaries
→ reporting / process execution
→ recognition and legitimacy
→ timing and burden
→ recurrence and non-repair memoryVictim pathway failures often begin in power asymmetry, become encoded into process boundaries, appear during reporting, affect recognition, compound through delay, and repeat through institutional memory.
7. Inputs
7.1 Core Observational Inputs
TableScroll
| Input | Description |
|---|---|
| Harmed node | The person, group, class, user, patient, student, worker, community, or subsystem affected by harm. |
| Harm or burden type | The kind of harm, burden, misclassification, exploitation, denial, coercion, or injury involved. |
| Power asymmetry | Difference in authority, resources, credibility, access, force, dependence, or consequence. |
| Current safety state | Whether the harmed node is safe enough to engage the pathway. |
| Truth access | Whether facts, records, logs, witnesses, or context can be accessed. |
| Available reporting pathway | What formal or informal process exists. |
| Disclosure requirements | What the harmed node must reveal or repeat to be heard. |
| Evidence requirements | What proof burden is placed on the harmed node. |
| Repair pathway | What actual repair, support, restitution, correction, or protection is available. |
| Institutional response | How the responsible system reacts to claim, harm, or evidence. |
| Retaliation risk | Risk of punishment, disbelief, exposure, exclusion, escalation, or loss. |
| Support availability | What support exists during the process. |
| Boundary condition | Privacy, role, consent, contact, access, and participation boundaries. |
| Recurrence pattern | Whether similar harms repeat. |
| Resolution outcome | What the process claims as closure or repair. |
7.2 Diagnostic Inputs
TableScroll
| Diagnostic | What It Measures | Why It Matters |
|---|---|---|
| Safety State | Whether the harmed node can engage without further exposure | Safety precedes resolution. |
| Affected Node Cost | Burden placed on the harmed node by the pathway | Core VRPS diagnostic. |
| Recognition Integrity | Whether the node’s standing and harm are acknowledged | Required before repair. |
| Truth Access | Whether necessary facts can be reached | No truth access means weak repair. |
| Repair Access | Whether repair is actually available | Formal process without repair is incomplete. |
| Restoration Capacity | Whether the pathway can restore coherence | Determines viability. |
| Disclosure Burden | Cost of telling, retelling, documenting, or exposing harm | High burden may invert repair. |
| Evidence Burden | Proof demands placed on the harmed node | Excessive burden blocks resolution. |
| Retaliation Risk | Risk from engaging the pathway | High risk may invalidate pathway. |
| Power Asymmetry | Difference in leverage or consequence | Raises pathway requirements. |
| Pathway Viability | Whether the pathway can realistically reach repair | Core outcome. |
| Boundary Integrity | Whether privacy, safety, contact, and participation limits hold | Boundary failure causes re-harm. |
| Feedback Integrity | Whether harmed-node feedback can alter the process | Prevents procedural theater. |
| Legitimacy Integrity | Whether the pathway is trusted because it restores, not because it exists | Distinguishes formal from lived legitimacy. |
| Recurrence Risk | Whether harm pattern is likely to repeat | Repair must reduce recurrence. |
8. Outputs
VRPS produces pathway assessments, burden maps, and restoration requirements.
8.1 Pathway Viability Assessment
Possible outputs:
textScroll
Pathway viable
Pathway viable with support
Pathway strained
Pathway unsafe
Pathway inaccessible
Pathway re-burdening
Pathway performative
Pathway invalid under current conditions8.2 Safety and Recognition Assessment
Possible outputs:
textScroll
Safety sufficient
Safety partial
Safety absent
Recognition intact
Recognition partial
Recognition absent
Recognition delayed
Recognition conditional on excessive proof8.3 Burden Assessment
Possible outputs:
textScroll
Burden proportionate
Burden high but supported
Burden excessive
Burden inverted
Disclosure burden unsafe
Evidence burden incoherent
Retaliation burden active
Support insufficient8.4 Decision Outputs
TableScroll
| Output | Meaning |
|---|---|
| Pathway viable | The harmed node can access safety, truth, repair, and restoration coherently. |
| Repair pathway before disclosure | Support and safety must exist before disclosure demands increase. |
| Reduce burden | Disclosure, evidence, timing, or procedural load must be lowered. |
| Increase safety | Safety must be restored before pathway use. |
| Increase support | The harmed node needs support to engage the process coherently. |
| Restore recognition | The harm or standing must be recognized before process continuation. |
| Repair boundaries | Privacy, contact, role, or participation boundaries must be restored. |
| Reroute pathway | Existing pathway is invalid; another route is required. |
| Pause process | Continuing now would re-burden or endanger the node. |
| Return ∅ | No coherent pathway exists under current conditions. |
9. Operating Logic
9.1 Basic Flow
textScroll
1. Identify harmed node.
2. Identify harm or burden type.
3. Assess power asymmetry.
4. Assess current safety state.
5. Assess truth access.
6. Map available reporting or resolution pathway.
7. Map disclosure and evidence burden.
8. Assess retaliation risk.
9. Assess recognition status.
10. Assess repair and restoration access.
11. Check support availability.
12. Check boundary integrity.
13. Assess recurrence risk.
14. Classify pathway viability.
15. Recommend safety, burden reduction, support, recognition repair, reroute, pause, or ∅.
16. Validate restoration over time.9.2 Burden Non-Inversion Rule
textScroll
IF the harmed node must perform excessive labor to become legible,
THEN the pathway is burden-inverting.
IF the pathway requires capacities the harm already damaged,
THEN the pathway is not coherence-valid without added support.
IF recognition depends on exhausting the harmed node,
THEN recognition restoration is required before continuing.
IF repair requires unsafe disclosure,
THEN safety must precede disclosure.9.3 Pathway Validity Rule
textScroll
A resolution pathway is valid only when it can provide:
- safety
- recognition
- truth access
- burden-proportionate process
- boundary protection
- non-retaliation
- repair access
- restoration capacity
- recurrence reduction
- time validationA pathway missing these may be formal, but it is not restorative.
10. Operators Used
TableScroll
| Operator | Role in VRPS |
|---|---|
| Ξ — Classification | Classifies pathway viability, harm state, burden class, and failure mode. |
| Δ — Differentiation | Separates formal access from actual access, process from repair, and closure from restoration. |
| Μ — Mapping | Maps safety, truth access, burden, retaliation, repair, and recurrence. |
| Π — Constraint / Scoping | Limits disclosure, contact, process load, or institutional demand. |
| Λ — Compatibility | Tests whether pathway demands fit harmed-node capacity and safety state. |
| ⊗ — Coupling | Evaluates whether the pathway forces harmful recoupling with institution, actor, or process. |
| ℛ — Restoration | Repairs safety, recognition, boundaries, truth access, and burden. |
| Σ — Integration / Coherence Binding | Integrates truth, repair, recognition, and non-recurrence into resolution. |
| Τ — Time Validation | Confirms repair holds and recurrence reduces over time. |
11. Gates Required
TableScroll
| Gate | Required Condition | Failure Result |
|---|---|---|
| Safety Gate | The harmed node can engage without further exposure or escalation. | Increase safety or pause pathway. |
| MS-Gate | Harmed-node standing and meaning are recognized. | Recognition restoration required. |
| FI-Gate | Feedback from harmed node can alter the process. | Feedback restoration required. |
| BΣ validity | Privacy, contact, role, consent, and pathway boundaries hold. | Boundary reconstitution required. |
| Au-Traceability | Harm, response, responsibility, and repair can be traced. | Auditability restoration required. |
| R sufficiency | Restoration capacity exists. | Increase repair capacity before proceeding. |
| Non-Retaliation Gate | Engaging the pathway does not create retaliation exposure. | Protect node or reroute pathway. |
| Burden Non-Inversion Gate | Process does not demand incoherent burden from the harmed node. | Reduce burden or increase support. |
| Repair Access Gate | Pathway can actually reach repair, not only reporting or closure. | Redesign or reroute pathway. |
| Τ validation | Resolution holds across recurrence and delayed effects. | Do not claim completion yet. |
12. Failure Modes Detected
TableScroll
| Failure Mode | Detection Signal |
|---|---|
| Victim Pathway Collapse | Pathway exists formally but cannot be navigated coherently. |
| Burden Inversion | Harmed node carries the burden of making harm legible and repair possible. |
| Disclosure Overload | Pathway requires repeated or unsafe disclosure. |
| Evidence Burden Trap | Proof requirements exceed harmed-node capacity or access. |
| Recognition Failure | Harm or standing is not acknowledged without excessive proof. |
| Retaliation Exposure | Pathway increases risk of punishment, exclusion, or escalation. |
| Safety Lockout | Node cannot safely enter the pathway. |
| Restoration Lockout | Pathway cannot reach actual repair. |
| Procedural Theater | Process exists but does not reduce burden or recurrence. |
| Institutional Self-Protection | Pathway protects the institution more than the harmed node. |
| Forced Recoupling | Node must re-engage with harmful actor, role, system, or institution prematurely. |
| Legitimacy Collapse | Pathway loses trust because it fails lived repair. |
| Resolution Theater | Closure is claimed without restoration. |
| Recurrence Without Repair | Same harm pattern repeats after resolution. |
13. Restoration Links
TableScroll
| Restoration Arc | When Activated |
|---|---|
| Safety Restoration | The harmed node cannot engage without risk. |
| Recognition Restoration | Harmed-node standing or burden is not recognized. |
| Justice-Aligned Repair | Harm under asymmetry requires truth, repair, and non-recurrence. |
| Boundary Reconstitution | Privacy, contact, role, consent, or process boundaries fail. |
| Auditability Restoration | Harm, response, responsibility, or repair cannot be traced. |
| Feedback Restoration | Harmed-node feedback cannot alter the process. |
| Slack Regeneration | Node lacks capacity to navigate the pathway. |
| Responsibility Gradient Mapping | Repair burden must move toward causal leverage. |
| Conditional Reintegration | Recoupling can occur only after staged repair and validation. |
| Recurrence Reduction | Repeated harm pattern must be interrupted. |
| Origin-Layer Repair | Pathway failure originates deeper than the visible process. |
14. U-Layer Localization
TableScroll
| U-Layer | Relevance |
|---|---|
| U0 — Substrate | Physical, legal, technical, biological, or record substrate needed for safety, evidence, and repair. |
| U1 — Power / Budgets | Authority, resources, credibility, money, staffing, support, and leverage shaping pathway access. |
| U2 — Configuration / Boundaries | Reporting structure, privacy, contact, consent, scope, role, and protection boundaries. |
| U3 — Execution / Runtime | Actual reporting, disclosure, review, appeal, repair, and resolution behavior. |
| U4 — Classification / Metrics | How harm, evidence, credibility, severity, and completion are classified. |
| U5 — Coordination / Time | Delays, deadlines, disclosure timing, appeal windows, safety timing, and recurrence windows. |
| U6 — Coherence Field | Recognition, dignity, trust, legitimacy, and harmed-node standing. |
| U7 — Memory / Recurrence | Prior harms, repeated pathway failures, institutional memory, and non-recurrence validation. |
| U8 — Environment / Forcing | Social pressure, retaliation pressure, institutional pressure, legal pressure, crisis, or cultural force. |
VRPS most commonly localizes through:
textScroll
U1 → U2 → U3 → U6 → U5 → U7This means resolution pathway failure often begins with power asymmetry, is encoded into process boundaries, manifests in pathway execution, affects recognition, compounds through time, and repeats through memory.
15. Example Use Case
Scenario
A worker reports repeated harassment from a higher-ranking manager.
The official pathway requires the worker to submit detailed documentation, meet with HR, continue working under the same manager during review, provide witnesses, and accept confidentiality limits. The manager has influence over scheduling, promotion, and future references.
The company says a pathway exists.
VRPS Evaluation
The construct checks:
- current safety state
- power asymmetry
- disclosure burden
- evidence burden
- retaliation risk
- boundary condition
- repair access
- support availability
- institutional response
- recurrence risk
Likely Findings
textScroll
Pathway viability: strained / unsafe
Power asymmetry: high
Retaliation risk: high
Disclosure burden: high
Safety state: insufficient
Recognition: conditional on excessive proof
Restoration access: unclearRecommended Output
textScroll
Do not treat formal reporting access as resolution.
Separate safety from disclosure.
Provide protected reporting channel.
Reduce repeated disclosure burden.
Protect against retaliation before proceeding.
Move repair burden toward causal leverage.
Define non-recurrence conditions.
Validate over time.Interpretation
The pathway exists, but it is not yet coherence-valid because it asks the harmed node to carry too much risk and burden before safety and recognition are secured.
16. Anti-Patterns
Do not use VRPS to:
- treat formal pathway existence as actual access
- require harmed nodes to exhaust themselves to be believed
- mistake disclosure for repair
- mistake process for restoration
- ignore retaliation risk
- ignore power asymmetry
- require unsafe evidence collection
- treat confidentiality as protection when it protects the institution more than the harmed node
- force recoupling before safety
- claim resolution without burden reduction
- treat apology or closure as recurrence reduction
- use neutrality to ignore asymmetry
- move repair burden away from causal leverage
- treat silence as restoration
17. Completion Criteria
A VRPS assessment is complete when:
- harmed node is identified
- harm or burden type is defined
- power asymmetry is assessed
- safety state is evaluated
- truth access is assessed
- reporting or resolution pathway is mapped
- disclosure and evidence burden are evaluated
- retaliation risk is assessed
- recognition status is checked
- repair access is evaluated
- restoration capacity is assessed
- support availability is identified
- boundary integrity is checked
- recurrence risk is assessed
- pathway viability is classified
- safety, burden reduction, support, recognition repair, reroute, pause, or ∅ is returned
- time validation is defined
18. Machine-Readable Summary
yamlScroll
construct_id: "CONSTRUCT-021"
title: "Victim Resolution Pathway System"
abbreviation: "VRPS"
type: "construct"
status: "draft-integrated"
construct_class: "Justice / Restoration Workflow"
operating_system: false
primary_module: "Justice · Governance · Legitimacy / Restoration"
related_modules:
- "Coherence"
- "Security"
- "Principles"
- "AI Governance"
- "Interactions · Signals · Couplings"
core_question: "Can a harmed or burdened node reach safety, recognition, truth, repair, and restoration without the resolution process transferring additional burden back onto that node?"
definition: "The Victim Resolution Pathway System maps whether a harmed or burdened node can access safety, truth, recognition, repair, and restoration through a pathway that does not re-burden, re-expose, silence, or procedurally exhaust the node."
inputs:
state_variables:
- "O"
- "H"
- "ε"
- "ι"
- "Au"
- "µᵢ"
- "BΣ"
- "K"
- "R"
- "Φ"
diagnostics:
- "Safety State"
- "Affected Node Cost"
- "Recognition Integrity"
- "Truth Access"
- "Repair Access"
- "Restoration Capacity"
- "Disclosure Burden"
- "Evidence Burden"
- "Retaliation Risk"
- "Power Asymmetry"
- "Pathway Viability"
- "Boundary Integrity"
- "Feedback Integrity"
- "Legitimacy Integrity"
- "Recurrence Risk"
gates:
- "Safety Gate"
- "MS-Gate"
- "FI-Gate"
- "BΣ validity"
- "Au-Traceability"
- "R sufficiency"
- "Non-Retaliation Gate"
- "Burden Non-Inversion Gate"
- "Repair Access Gate"
- "Τ validation"
observations:
- "harmed node"
- "harm or burden type"
- "power asymmetry"
- "current safety state"
- "truth access"
- "available reporting pathway"
- "disclosure requirements"
- "evidence requirements"
- "repair pathway"
- "institutional response"
- "retaliation risk"
- "support availability"
- "boundary condition"
- "recurrence pattern"
- "resolution outcome"
outputs:
assessments:
- "pathway viability"
- "safety adequacy"
- "truth access status"
- "recognition status"
- "repair access status"
- "burden transfer risk"
- "retaliation risk"
- "restoration sufficiency"
- "legitimacy status"
- "recurrence risk"
decisions:
- "pathway viable"
- "repair pathway before disclosure"
- "reduce burden"
- "increase safety"
- "increase support"
- "restore recognition"
- "repair boundaries"
- "reroute pathway"
- "pause process"
- "return ∅"
maps:
- "victim resolution pathway map"
- "safety pathway map"
- "truth access map"
- "burden transfer map"
- "disclosure burden map"
- "retaliation risk map"
- "repair access map"
- "restoration requirement map"
- "recurrence prevention map"
dependencies:
operators:
- "Ξ"
- "Δ"
- "Μ"
- "Π"
- "Λ"
- "⊗"
- "ℛ"
- "Σ"
- "Τ"
failure_modes:
- "Victim Pathway Collapse"
- "Burden Inversion"
- "Disclosure Overload"
- "Evidence Burden Trap"
- "Recognition Failure"
- "Retaliation Exposure"
- "Safety Lockout"
- "Restoration Lockout"
- "Procedural Theater"
- "Institutional Self-Protection"
- "Forced Recoupling"
- "Legitimacy Collapse"
- "Resolution Theater"
- "Recurrence Without Repair"
restoration_arcs:
- "Safety Restoration"
- "Recognition Restoration"
- "Justice-Aligned Repair"
- "Boundary Reconstitution"
- "Auditability Restoration"
- "Feedback Restoration"
- "Slack Regeneration"
- "Responsibility Gradient Mapping"
- "Conditional Reintegration"
- "Recurrence Reduction"
- "Origin-Layer Repair"
u_layers:
primary:
- "U1"
- "U2"
- "U3"
- "U5"
- "U6"
- "U7"
secondary:
- "U0"
- "U4"
- "U8"
null_outcome_allowed: true
formal_pathway_is_not_restorative_pathway: true19. Citation
Citation ID: construct-victim-resolution-pathway-system-v1-0
Recommended citation:
Universal Theory Stack. “CONSTRUCT-021 — Victim Resolution Pathway System.” UTS Constructs Registry, Version 1.0.0, 2026.
20. Summary
The Victim Resolution Pathway System evaluates whether a harmed node can actually reach safety, truth, recognition, repair, and restoration.
Its core distinction is:
textScroll
formal pathway is not restorative pathwayVRPS identifies when reporting, appeal, complaint, justice, or repair processes re-burden the harmed node through disclosure demands, evidence burden, retaliation risk, unsafe boundaries, procedural exhaustion, or inaccessible repair.
Its core logic is:
textScroll
A resolution pathway is coherent only if it reduces burden, protects safety, restores recognition, reaches truth, enables repair, and lowers recurrence.When the pathway requires the harmed node to carry incoherent burden, VRPS recommends safety restoration, burden reduction, support increase, recognition repair, pathway rerouting, process pause, or:
textScroll
∅VRPS gives UTS a justice-pathway map for distinguishing real restoration from formal process.