INV-052 — Restoration Requires Capacity Before Demand

1. Definition

A system cannot coherently demand participation, disclosure, performance, forgiveness, testimony, repair, endurance, or reintegration from a node whose capacity has been collapsed.

Restoration requires capacity before demand.

A harmed, overloaded, under-supported, depleted, misclassified, excluded, or burden-bearing node must not be required to provide the coherence that the system failed to preserve.

This invariant blocks victim-burden inversion.

It prevents restoration processes from shifting responsibility onto the node already carrying the hidden debt.

Therefore:

Restoration requires capacity before demand.

The affected node may eventually participate in restoration.

But participation becomes coherent only when the system first restores enough capacity, boundary integrity, safety of exit, auditability, and support for participation to be real rather than extracted.

2. Purpose

This invariant prevents restoration from becoming another form of extraction.

Systems often demand that affected nodes:

• explain the harm
• prove the harm
• remain calm
• forgive
• move on
• perform normally
• return to work
• restore trust
• educate the system
• supply testimony
• participate in review
• accept reintegration
• repair the relationship
• absorb the cost
• comply with process
• provide legitimacy
• prove worthiness
• continue functioning

These demands may be framed as part of restoration.

But if the affected node’s capacity has already been damaged, the demand can become a second burden.

The false assumption is:

The harmed or affected node must participate immediately for restoration to proceed.

The UTS correction is:

The system must restore enough capacity before making restoration demands.

The core purpose:

Do not require the depleted node to supply the system’s missing restoration capacity.

3. Constraint Statement

Canonical Form

Restoration requires capacity before demand.

Expanded Form

A restoration process is invalid when it requires a harmed, depleted,
under-supported, misclassified, overloaded, excluded, or affected node to
supply disclosure, testimony, forgiveness, performance, coherence,
legitimacy, repair, or reintegration before the system has restored enough
capacity, boundary integrity, auditability, support, and safe participation
conditions.

Minimal Expression

No demand before capacity.

Restoration Form

Do not demand repair from the node still carrying unrepaired debt.

Governance Form

Affected-node participation must be supported before it is required.

Security Form

Do not require compromised or harmed users to repair the incident response system.

AI Form

Do not require users harmed by model error, misclassification, or memory distortion to supply all correction labor without restoration support.

Biological Form

Do not demand performance from a system whose adaptive reserve has collapsed.

CMS / Symbolic Form

Do not demand forgiveness, meaning, or reconciliation before capacity and boundary restoration.

4. Structural Logic

Demand consumes capacity.

Restoration is already capacity-intensive.

If a node’s capacity has been collapsed by harm, overload, deprivation, misclassification, exclusion, coercion, biological burden, economic extraction, institutional opacity, or symbolic distortion, then demanding further output from that node may increase hidden debt.

The system creates inversion when it says:

You must help us restore the system that failed to protect your capacity.

This is victim-burden inversion.

The incoherent sequence:

node is harmed or depleted
        ↓
capacity collapses
        ↓
system demands testimony, performance, forgiveness, or participation
        ↓
node bears additional burden
        ↓
system receives legitimacy or process completion
        ↓
hidden debt remains displaced into affected node
        ↓
restoration claim becomes inversion

The coherent sequence:

node is harmed or depleted
        ↓
system stabilizes conditions
        ↓
capacity is restored or supported
        ↓
boundaries and exit are clarified
        ↓
truth pathway is made safe and auditable
        ↓
participation becomes voluntary and resourced
        ↓
repair proceeds without burden inversion

Core insight:

A node cannot be required to restore a system while still carrying the system’s unrepaired debt.

Capacity must precede demand.

5. State-Vector Impact

Protected State Variables

O   — coherence
R   — restoration capacity
BΣ  — boundary integrity
µᵢ  — meaning / agent integrity
Au  — auditability
K   — compatibility of participation conditions
H   — hidden debt

Primary Risk Variables

ι   — inversion when burden-bearing nodes are framed as responsible for restoration
ε   — visible distress, refusal, breakdown, nonparticipation, conflict, or recurrence
Φ   — process completion, participation, compliance, forgiveness, testimony, productivity, or closure proxy

Healthy Capacity-First Pattern

affected burden recognized
capacity assessed
support provided
BΣ restored
Au restored
R increased
participation becomes viable
H↓
O↑

Violation Pattern

affected node capacity↓
system demand↑
support insufficient
BΣ↓
µᵢ↓
H exported
ι↑
O↓

Victim-Burden Inversion Pattern

system debt exists
affected node carries burden
system demands affected node participation
system claims restoration
H remains exported
ι↑

Demand Threshold

A restoration demand becomes incoherent when:

Demand Load > affected node’s available capacity + support + boundary protection

If demand exceeds capacity, the demand becomes extraction.

6. U-Layer Localization

Primary Layer

U1 — Power / Budgets

Capacity before demand is fundamentally a budget constraint: time, energy, attention, money, safety, biological reserve, social support, legal support, interpretive support, and restoration support must exist before demand is coherent.

Boundary Layer

U2 — Configuration / Boundaries

Participation must occur through valid boundaries: consent, scope, exit, protection, role clarity, and non-retaliation.

Execution Layer

U3 — Execution

Demands occur through execution: testimony requests, work demands, participation requirements, deadlines, reintegration steps, performance expectations, or process obligations.

Classification Layer

U4 — Classification / Metrics

Affected nodes are often misclassified as uncooperative, resistant, irrational, unproductive, difficult, or noncompliant when the real issue is capacity collapse.

Coordination Layer

U5 — Coordination / Time

Demand timing matters. Even a valid request can be incoherent if made before capacity is restored.

Coherence Field Layer

U6 — Coherence Field

Meaning, legitimacy, trust, and participation degrade when affected nodes are asked to carry system debt.

Memory Layer

U7 — Memory / Recurrence

If capacity collapse is not repaired, the pattern recurs: the same nodes repeatedly carry restoration burden.

Environment Layer

U8 — Environment / Forcing

External pressure often pushes systems to demand rapid participation, testimony, forgiveness, or productivity before capacity exists.

Common Failure Pattern

U8 pressure for closure
        ↓
U4 affected node labeled noncooperative
        ↓
U3 participation demand issued
        ↓
U1 capacity absent
        ↓
U2 boundaries remain unsafe
        ↓
U6 legitimacy declines
        ↓
U7 recurrence continues
        ↓
H remains exported

Common Misdiagnosis

Violation of this invariant is often misdiagnosed as:

• unwillingness to participate
• poor attitude
• lack of forgiveness
• noncompliance
• low resilience
• communication failure
• obstruction
• lack of professionalism
• refusal to heal
• lack of trust
• poor motivation
• disengagement
• failure to cooperate
• instability

The deeper issue may be:

The system demanded output before restoring capacity.

7. Violation Signatures

7.1 Testimony Demand Before Support

The affected node is required to explain, document, prove, or relive the harm without sufficient support.

testimony demand↑
support capacity↓
H burden↑

Truth reception becomes extraction.

7.2 Forgiveness Demand Before Repair

The system asks for forgiveness, reconciliation, peace, unity, or closure before boundary repair and material repair occur.

forgiveness demand↑
BΣ unrepaired
H remains

Forgiveness becomes pseudo-restoration.

7.3 Performance Demand After Capacity Collapse

The node is expected to return to normal function before restoration.

performance demand↑
capacity↓
ε↑

The system treats depletion as nonperformance.

7.4 Participation as Legitimacy Extraction

The system uses the affected node’s participation to legitimize a process that has not materially repaired the affected burden.

participation↑
system legitimacy claim↑
affected burden unchanged

Participation becomes symbolic capture.

7.5 Appeal Process Too Burdensome to Use

The system technically provides appeal, but the process requires more capacity than affected nodes possess.

formal appeal exists
usable appeal↓
Au_eff↓

The pathway exists at U4 but fails at U1/U2.

7.6 User Correction Labor Without AI Restoration Support

Users harmed by AI error must repeatedly correct the system, explain context, repair memory, or navigate unclear appeals without adequate support.

user correction labor↑
platform R↓
H exported to user

The user becomes the restoration system.

7.7 Economic Burden After Extraction

A worker, household, supplier, or community is asked to adapt, retrain, reskill, relocate, or absorb transition cost after capacity was depleted by the same system.

adaptation demand↑
economic slack↓
burden inversion↑

7.8 Biological Demand Beyond Reserve

A living system is asked to train harder, recover faster, perform normally, or tolerate more inputs before adaptive reserve returns.

biological demand↑
reserve↓
ring-down worsens

7.9 Relationship Repair Labor Imbalance

One party is expected to explain, soothe, forgive, rebuild trust, and maintain the relationship after boundary violation without receiving repair.

repair labor displaced
BΣ unrepaired
H exported

7.10 Institutional Review Depends on Harmed Node Endurance

A review process can only function if the affected node repeatedly persists through complexity, delay, documentation, skepticism, and cost.

review burden↑
affected capacity↓
truth pathway fails

The review process becomes structurally inaccessible.

8. Related Failure Modes

Primary related failure modes:

• Victim-Burden Inversion
• Capacity-Before-Demand Failure
• Affected-Node Burden Export
• Testimony Extraction
• Forgiveness Demand
• Performance Demand After Harm
• Participation Capture
• Formal Appeal / Unusable Appeal
• Restoration Labor Displacement
• User Correction Burden
• AI Support Burden Export
• Economic Adaptation Burden
• Biological Over-Demand
• Relational Repair Labor Imbalance
• Institutional Review Inaccessibility
• Boundary Repair Failure
• Pseudo-Restoration
• Restoration Bypass
• Legitimacy Extraction
• Hidden Debt Accumulation
• Meaning Collapse
• Trust Demand Before Repair
• Premature Reintegration
• Coercive Closure

9. Related Restoration Arcs

Primary restoration arcs:

• Capacity Restoration
• Affected-Node Burden Relief
• Stabilization First
• Support Before Testimony
• Boundary Reconstitution
• Appeal Accessibility Restoration
• Participation Support Design
• Restoration Capacity Rebuild
• Truth Pathway Protection
• Non-Retaliation Assurance
• Material Burden Repair
• Demand Reduction
• Scope Reduction
• Temporal Re-Sequencing
• User Correction Burden Reduction
• AI Support Pathway Repair
• Economic Slack Restoration
• Biological Reserve Rebuild
• Relational Repair Rebalancing
• Legitimacy Restoration

Restoration Requirement

Before demanding participation, determine whether the affected node has capacity.

Minimal sequence:

Identify affected-node burden
        ↓
Assess capacity and support needs
        ↓
Stabilize conditions
        ↓
Restore boundaries and safe exit
        ↓
Provide material / procedural support
        ↓
Reduce unnecessary demand
        ↓
Make participation optional, scoped, and supported
        ↓
Proceed only within capacity
        ↓
Validate that burden is decreasing

10. Domain Expressions

AI

AI systems often export restoration labor to users.

Examples:

users must repeatedly correct memory
users must explain misclassification
users must navigate unclear appeals
users must debug model behavior
users must preserve context manually
users must absorb hallucination cost
users must prove they were harmed

This violates INV-052 when the system caused the burden and then requires the user to provide the correction capacity.

A coherent AI restoration path provides:

• usable correction tools
• memory inspection and repair
• clear appeal routes
• low-friction reporting
• explanation where appropriate
• burden-aware support
• recurrence reduction
• rollback where needed

The user can participate, but should not become the restoration infrastructure.

AI Governance

AI governance must not depend on affected users having extraordinary capacity.

Appeal, correction, reporting, and redress pathways must be usable by those already harmed or burdened.

Failure pattern:

public-impact AI harms user
        ↓
appeal requires time, expertise, emotional labor, documentation, persistence
        ↓
most affected users cannot complete appeal
        ↓
system claims low appeal volume
        ↓
Au_eff collapses

Low appeal volume may indicate inaccessible appeal, not low harm.

Governance must scale support before demanding participation.

Security

Security processes often demand users participate in incident response.

This can be valid only when users are supported.

Violation examples:

• compromised users must diagnose the attack themselves
• harmed users must prove breach consequences without access to logs
• users must repeatedly re-secure accounts without root-cause repair
• employees are blamed for phishing without training and system support
• reporting security issues is costly or punished

Security restoration requires that affected users are not made responsible for repairing the security architecture that failed.

Governance / JGL

Justice and governance systems must not require harmed nodes to carry the entire burden of truth production.

Common failure:

harmed node must report
harmed node must prove
harmed node must endure delay
harmed node must appeal
harmed node must remain composed
harmed node must accept closure

A legitimate process must provide:

• accessible reporting
• evidence support
• protection from retaliation
• material support
• clear process
• appeal capacity
• responsibility tracing
• repair pathways

No system can claim legitimacy while making truth reception depend on harmed-node endurance alone.

Economy

Economic systems violate INV-052 when they demand adaptation from nodes whose slack they have already consumed.

Examples:

workers must reskill after extraction without support
communities must absorb plant closures without transition repair
households must adapt to inflation without wage or support repair
suppliers must absorb platform rule changes without capacity
borrowers must navigate complex relief processes while financially depleted

Coherent economic restoration requires:

• slack restoration
• transition support
• material repair
• accessible processes
• burden-aware timing
• circulation repair

Adaptation demand without capacity becomes extraction.

Biology / Medicine

Living systems cannot be restored through demand alone.

Violation examples:

train harder while recovery reserve is depleted
eat perfectly while digestion and resources are unstable
perform normally while sleep and repair capacity are damaged
tolerate new interventions before stabilization
increase challenge exposure before adaptive reserve returns

Biological restoration requires capacity restoration before increased demand.

A coherent biological sequence:

reduce overload
restore reserve
stabilize regulation
then increase adaptive challenge gradually

Demand must follow capacity.

CMS / Meaning

Meaning restoration violates INV-052 when the burdened node is asked to provide forgiveness, meaning, unity, spiritual maturity, or symbolic reconciliation before truth and repair exist.

Examples:

forgive before repair
find meaning before burden relief
reconcile before boundaries
hold compassion before safety
return to unity before differentiation

Meaning can emerge after repair, but should not be extracted to cover unrepaired debt.

Sacred language cannot be used to demand capacity from a depleted node.

Principles / Archetypes

Principles can invert when used to demand capacity prematurely.

Examples:

truth used to force disclosure before stabilization
love used to demand forgiveness before repair
justice used to demand testimony without support
sovereignty used to blame unsupported nodes for non-participation
wisdom used to demand calm under unresolved burden
service used to demand overextension

Archetypal inversion examples:

Healer expected to heal while depleted
Protector expected to protect without support
Witness expected to testify without safety
Teacher expected to explain while burdened
Sovereign expected to choose without viable options

Principles must not become extraction channels.

Relationships / Couplings

Relational repair requires capacity before demand.

Violation examples:

one party must explain harm immediately
one party must forgive before repair
one party must restore closeness before trust returns
one party must regulate the whole field
one party must maintain contact to prove goodwill
one party must accept apology as closure

A coherent relational sequence:

stop harm
restore boundary
reduce immediate burden
support truth reception
repair materially / behaviorally
change recurrence
rebuild trust over time

Participation must be possible, not coerced by dependency or exhaustion.

Project / Knowledge Systems

Knowledge systems also need capacity before demand.

A project cannot demand:

more output
more integration
more review
more canon precision
more cross-linking
more publication

from an archive, team, or cognitive workflow already overloaded by hidden debt.

For UTS-style work, if the registry has accumulated drift, the project must restore:

template capacity
review capacity
deduplication capacity
cross-link capacity
versioning capacity

before demanding further expansion.

Otherwise new work becomes hidden-debt amplification.

11. Scaling Behavior

As systems scale, the risk of capacity-before-demand violation rises.

Scale increases:

affected-node count
process complexity
documentation burden
appeal burden
participation burden
truth-production burden
distance from decision makers
difficulty of individualized support

Therefore:

Scale↑ ⇒ support capacity must scale before demand capacity

Scaling Risk Pattern

scale↑
harm or burden occurs
process demand↑
affected-node capacity↓
support insufficient
truth pathway fails
H exported

Valid Scaling Pattern

scale↑
affected-node support↑
appeal accessibility↑
burden relief↑
participation scaffolding↑
R↑

Capacity Infrastructure

At scale, capacity before demand requires:

• accessible appeal
• support staff
• documentation assistance
• translation / interpretation where needed
• non-retaliation protection
• material support
• procedural simplification
• time allowances
• user correction tooling
• affected-node advocates
• public repair capacity
• low-friction feedback channels

Relation to INV-051

INV-051 states:

Restoration is sequenced.

INV-052 specifies a critical sequence rule:

Capacity must precede demand.

Together:

Do not place restoration demands on nodes before restoring the capacity required to meet them.

12. Canonical Examples

Example 1 — Appeal System Too Hard to Use

A platform offers an appeal process, but users must submit complex documentation, repeat context, wait weeks, and navigate unclear rules.

formal appeal exists
usable appeal↓
affected-node capacity insufficient

The appeal pathway is nominal, not restorative.

Example 2 — Workplace Harm Review

An employee harmed by a workplace process is asked to repeatedly explain the issue, keep working normally, maintain professionalism, and help design the fix without support.

testimony demand↑
performance demand↑
support↓
H exported to employee

The review process becomes extraction.

Example 3 — AI Memory Error

An AI system stores or applies user context incorrectly.

The user must repeatedly correct it, clarify the same point, and manage downstream errors without memory audit tools.

user correction labor↑
system R↓
µᵢ burden↑

The user becomes the repair layer.

Example 4 — Economic Transition Without Slack

A community loses a major source of livelihood and is told to retrain or relocate without financial support, timing support, or transition infrastructure.

adaptation demand↑
capacity↓
economic H↑

Demand precedes capacity.

Example 5 — Biological Over-Demand

A body under depleted reserve is asked to train harder, detox faster, tolerate more inputs, or return to normal output.

performance demand↑
reserve↓
recurrence risk↑

Recovery requires reserve first.

Example 6 — Forgiveness Before Repair

A person or group is asked to forgive, reconcile, or move on before boundaries, truth, and material repair are restored.

forgiveness demand↑
BΣ unrepaired
pseudo-restoration↑

The demand protects closure, not coherence.

Example 7 — UTS Registry Expansion Under Drift

A project continues demanding new spec sheets while prior naming drift, template ambiguity, or cross-link debt remains unresolved.

output demand↑
canon repair capacity↓
H↑

The coherent move is to pause and restore project capacity.

13. Anti-Patterns

Anti-Pattern 1 — “They Need to Participate for Us to Help Them”

Participation may be useful, but only after support makes it viable.

Anti-Pattern 2 — “They Must Prove the Harm”

Truth pathways should not depend entirely on harmed-node endurance.

Anti-Pattern 3 — “Forgiveness Is Required for Closure”

Forgiveness cannot be demanded as restoration infrastructure.

Anti-Pattern 4 — “Return to Normal Shows Recovery”

Returning to normal can be coerced performance under unrepaired burden.

Anti-Pattern 5 — “The Appeal Exists, So the System Is Fair”

Formal appeal is not usable appeal.

Anti-Pattern 6 — “Users Can Correct the System”

User correction is valid only when supported and not used to offload system repair.

Anti-Pattern 7 — “Adaptation Is Their Responsibility”

Adaptation demand is incoherent when the system consumed the slack needed to adapt.

Anti-Pattern 8 — “If They Care, They Will Keep Showing Up”

Endurance is not proof of capacity or consent.

Anti-Pattern 9 — “Capacity Is a Personal Issue”

Capacity is structural: budgets, boundaries, support, timing, safety, and repair pathways.

Anti-Pattern 10 — “Demand Builds Strength”

Demand beyond capacity creates debt, not strength.

14. Related Laws

This invariant connects strongly to:

• Capacity Before Demand Law
• Victim-Burden Inversion Law
• Hidden Debt Export Law
• Restoration Bypass Law
• Affected-Node Truth Law
• Appeal Accessibility Law
• Slack Sovereignty Law
• Boundary Repair Law
• Restoration Sequencing Law
• Meaning Collapse Law
• Compliance Without Participation Law
• Temporal Compression Law
• User Correction Burden Law
• Economic Adaptation Burden Law
• Biological Reserve Law

15. Related Scaling Rules

Related scaling rules:

• Support Must Scale Before Demand
• Appeal Usability Must Scale With Harm Burden
• Affected-Node Capacity Must Be Restored Before Testimony Demand
• Participation Burden Must Scale Down as Harm Burden Scales Up
• Material Support Must Scale With Process Demand
• User Correction Burden Must Decrease as AI Scale Increases
• Economic Transition Support Must Scale With Disruption
• Biological Challenge Must Scale With Reserve
• Restoration Demand Must Not Exceed Node Capacity
• Process Complexity Must Decrease for Collapsed-Capacity Nodes
• Non-Retaliation Protection Must Scale With Power Asymmetry
• Truth Pathways Must Not Depend on Endurance Alone

16. Related Gates

Relevant gates:

• Affected-Node Capacity Gate
• Capacity Before Demand Gate
• Restoration Sequencing Gate
• Material Support Gate
• Boundary Integrity Gate
• Consent Validity Gate
• Appeal Accessibility Gate
• Truth Pathway Gate
• Non-Retaliation Gate
• Participation Legitimacy Gate
• Forgiveness Demand Gate
• Performance Demand Gate
• AI User Correction Burden Gate
• Economic Transition Support Gate
• Biological Reserve Gate
• Reintegration Gate
• Temporal Validation Gate
• High Risk Gate
• Interface Legitimacy Gate
• Restoration Capacity Gate

Gate Logic

A restoration demand fails when:

affected-node capacity is collapsed

or when:

support is insufficient for the requested participation

or when:

appeal exists formally but is unusable under actual burden

or when:

truth production depends on harmed-node endurance

or when:

forgiveness or reconciliation is demanded before repair

or when:

performance is demanded before reserve restoration

or when:

users are required to perform system correction labor without support

Gate failure returns:

∅

Meaning:

not admissible under current capacity-before-demand conditions

The coherent response may be:

reduce demand
restore capacity
provide support
repair boundaries
simplify process
protect participation
make appeal usable
delay reintegration
validate over time

17. Related Operators

18. Machine-Readable Summary

id: UTS-INV-052
name: Restoration Requires Capacity Before Demand
registry: UTS Invariants Registry
category: Restoration Invariant / Capacity Invariant / Affected-Node Invariant / Justice Invariant
status: Draft-Integrated
version: 0.1

definition: >
  A system cannot coherently demand participation, disclosure, performance,
  forgiveness, testimony, repair, endurance, or reintegration from a node
  whose capacity has been collapsed. Restoration requires capacity before
  demand and blocks victim-burden inversion.

constraint: >
  A restoration process is invalid when it requires a harmed, depleted,
  under-supported, misclassified, overloaded, excluded, or affected node to
  supply disclosure, testimony, forgiveness, performance, coherence,
  legitimacy, repair, or reintegration before the system has restored enough
  capacity, boundary integrity, auditability, support, and safe participation
  conditions.

canonical_form:
  - "Restoration requires capacity before demand"
  - "No demand before capacity"
  - "Do not demand repair from the node still carrying unrepaired debt"
  - "Affected-node participation must be supported before it is required"
  - "The user must not become the restoration infrastructure"
  - "Forgiveness cannot be demanded as repair"

protects:
  - affected_node_capacity
  - restoration_integrity
  - boundary_integrity
  - consent_validity
  - truth_pathway_access
  - appeal_accessibility
  - material_support
  - agency_integrity
  - burden_relief
  - legitimacy_restoration

state_vector_effects_when_preserved:
  O: "increases_or_stabilizes_through_supported_participation"
  H: "decreases_because_burden_is_repaired_not_exported"
  ε: "visible_distress_or_nonparticipation_is_not_misclassified_as_failure"
  ι: "decreases_because_affected_node_burden_is_not_framed_as_responsibility"
  Au: "increases_through_usable_truth_and_appeal_pathways"
  µᵢ: "preserved_by_not_extracting_meaning_coherence_or_legitimacy_from_depleted_nodes"
  BΣ: "restored_before_participation_or_reintegration_demand"
  K: "validated_for_participation_conditions"
  R: "increases_through_system_provided_support_and_repair_capacity"
  Φ: "process_completion_compliance_forgiveness_or_participation_not_misread_as_restoration"

state_vector_effects_when_violated:
  O: "decreases_as_restoration_becomes_extraction"
  H: "increases_or_remains_exported_to_affected_node"
  ε: "appears_as_refusal_breakdown_nonparticipation_conflict_or_recurrence"
  ι: "increases_through_victim_burden_inversion"
  Au: "decreases_if_appeal_or_truth_pathway_is_formal_but_unusable"
  µᵢ: "decreases_as_agent_integrity_is_overburdened_or_misclassified"
  BΣ: "decreases_when_participation_is_demanded_without_safe_boundaries"
  K: "unvalidated_or_degraded_for_reintegration"
  R: "outsourced_to_affected_node_instead_of_built_systemically"
  Φ: "may_rise_through_participation_closure_compliance_or_return_to_performance"

primary_u_layer: U1
boundary_layer: U2
execution_layer: U3
classification_layer: U4
coordination_layer: U5
field_layer: U6
memory_layer: U7
environment_layer: U8

violation_signatures:
  - testimony_demand_before_support
  - forgiveness_demand_before_repair
  - performance_demand_after_capacity_collapse
  - participation_as_legitimacy_extraction
  - appeal_process_too_burdensome_to_use
  - user_correction_labor_without_ai_restoration_support
  - economic_burden_after_extraction
  - biological_demand_beyond_reserve
  - relationship_repair_labor_imbalance
  - institutional_review_depends_on_harmed_node_endurance

related_failure_modes:
  - Victim Burden Inversion
  - Capacity Before Demand Failure
  - Affected Node Burden Export
  - Testimony Extraction
  - Forgiveness Demand
  - Performance Demand After Harm
  - Participation Capture
  - Formal Appeal Unusable Appeal
  - Restoration Labor Displacement
  - User Correction Burden
  - AI Support Burden Export
  - Economic Adaptation Burden
  - Biological Over Demand
  - Relational Repair Labor Imbalance
  - Institutional Review Inaccessibility
  - Boundary Repair Failure
  - Pseudo Restoration
  - Restoration Bypass
  - Legitimacy Extraction
  - Hidden Debt Accumulation
  - Meaning Collapse
  - Trust Demand Before Repair
  - Premature Reintegration
  - Coercive Closure

related_restoration_arcs:
  - Capacity Restoration
  - Affected Node Burden Relief
  - Stabilization First
  - Support Before Testimony
  - Boundary Reconstitution
  - Appeal Accessibility Restoration
  - Participation Support Design
  - Restoration Capacity Rebuild
  - Truth Pathway Protection
  - Non Retaliation Assurance
  - Material Burden Repair
  - Demand Reduction
  - Scope Reduction
  - Temporal Re Sequencing
  - User Correction Burden Reduction
  - AI Support Pathway Repair
  - Economic Slack Restoration
  - Biological Reserve Rebuild
  - Relational Repair Rebalancing
  - Legitimacy Restoration

related_laws:
  - Capacity Before Demand Law
  - Victim Burden Inversion Law
  - Hidden Debt Export Law
  - Restoration Bypass Law
  - Affected Node Truth Law
  - Appeal Accessibility Law
  - Slack Sovereignty Law
  - Boundary Repair Law
  - Restoration Sequencing Law
  - Meaning Collapse Law
  - Compliance Without Participation Law
  - Temporal Compression Law
  - User Correction Burden Law
  - Economic Adaptation Burden Law
  - Biological Reserve Law

related_scaling_rules:
  - Support Must Scale Before Demand
  - Appeal Usability Must Scale With Harm Burden
  - Affected Node Capacity Must Be Restored Before Testimony Demand
  - Participation Burden Must Scale Down As Harm Burden Scales Up
  - Material Support Must Scale With Process Demand
  - User Correction Burden Must Decrease As AI Scale Increases
  - Economic Transition Support Must Scale With Disruption
  - Biological Challenge Must Scale With Reserve
  - Restoration Demand Must Not Exceed Node Capacity
  - Process Complexity Must Decrease For Collapsed Capacity Nodes
  - Non Retaliation Protection Must Scale With Power Asymmetry
  - Truth Pathways Must Not Depend On Endurance Alone

related_gates:
  - Affected Node Capacity Gate
  - Capacity Before Demand Gate
  - Restoration Sequencing Gate
  - Material Support Gate
  - Boundary Integrity Gate
  - Consent Validity Gate
  - Appeal Accessibility Gate
  - Truth Pathway Gate
  - Non Retaliation Gate
  - Participation Legitimacy Gate
  - Forgiveness Demand Gate
  - Performance Demand Gate
  - AI User Correction Burden Gate
  - Economic Transition Support Gate
  - Biological Reserve Gate
  - Reintegration Gate
  - Temporal Validation Gate
  - High Risk Gate
  - Interface Legitimacy Gate
  - Restoration Capacity Gate

19. Compact Canon Statement

UTS-INV-052 states that restoration requires capacity before demand. A system cannot coherently demand participation, testimony, disclosure, forgiveness, performance, endurance, reintegration, or repair from a node whose capacity has been collapsed. Restoration becomes inversion when the harmed, depleted, misclassified, or under-supported node is required to supply the coherence, legitimacy, truth production, or repair labor that the system failed to provide. Capacity, support, boundary integrity, and usable pathways must precede demand.

20. Short Reference Version

UTS-INV-052 — Restoration Requires Capacity Before Demand

No demand before capacity.

A system cannot coherently demand:

testimony
participation
forgiveness
performance
reintegration
repair labor
truth production
endurance
legitimacy

from a node whose capacity has been collapsed.

Affected-node participation must be supported before it is required.

Violation pattern:

system debt exists
affected node carries burden
system demands affected-node participation
system claims restoration
H remains exported
ι↑

Core rule:

Do not require the depleted node to supply
the system’s missing restoration capacity.