1) Diagnostic Identity

Diagnostic Name: Resource Asymmetry

Short Name / Symbol: resource_asymmetry

Diagnostic Class: Resource Distribution / Coupling Burden / Power-Budget Imbalance / Dependency Risk

Primary Function: Estimate the imbalance in available resources, capacity, leverage, access, repair capability, time, energy, money, compute, attention, authority, or operational support between coupled nodes, roles, institutions, systems, or subfields.

Primary Use: Determine whether one node has disproportionate ability to absorb stress, impose cost, exit, repair, negotiate, delay, scale, or survive failure compared to another.

Core Risk if Ignored: The system may treat an interaction as symmetrical, voluntary, compatible, or fair while unequal resources silently shape dependency, consent, exit cost, repair burden, attribution, and boundary strain.

Core Risk if Overtrusted: Any resource difference may be treated as coercive or incoherent, causing the system to miss healthy specialization, role differentiation, stewardship, mutual support, or proportional contribution.

2) Mechanical Definition

resource_asymmetry measures the imbalance between nodes in the resources required to act, refuse, repair, sustain, exit, contest, absorb stress, or influence outcomes.

resource_asymmetry answers:

Who has more capacity, and what does that difference allow or prevent?

Resources may include:

money
time
energy
labor
attention
compute
information
authority
legal access
technical access
social credibility
institutional support
mobility
fallback options
repair capacity
audit access
expression access
coordination capacity
memory control

Resource asymmetry is not automatically incoherent. Many systems require differentiated roles, uneven specialization, or stewardship structures.

It becomes dangerous when unequal resources create unequal ability to:

say no
leave
repair
challenge
be heard
survive delay
absorb harm
shape narrative
define standards
access exceptions
recover from failure

A simple form:

resource_asymmetry becomes coherence-relevant when it changes boundary, repair, exit, feedback, or consequence conditions.

3) What the Diagnostic Measures

Direct Measurement Target

resource_asymmetry measures:

• resource imbalance
• capacity imbalance
• power-budget imbalance
• repair-resource imbalance
• time and attention asymmetry
• financial asymmetry
• compute or infrastructure asymmetry
• information access asymmetry
• authority asymmetry
• audit access asymmetry
• legal or procedural access asymmetry
• fallback asymmetry
• exit capacity asymmetry
• expression capacity asymmetry
• resilience asymmetry
• negotiation asymmetry
• consequence absorption asymmetry
• ability to impose or resist cost

Indirect / Proxy Signals

resource_asymmetry can be estimated from:

• one node can wait longer than another
• one node can absorb loss more easily
• one node controls access to essential resources
• one node has more fallback options
• one node can appeal or litigate while another cannot
• one node can delay without equivalent cost
• one node can repair faster
• one node can hire, automate, scale, or replace
• one node controls shared infrastructure
• one node controls the narrative channel
• one node carries more unpaid labor
• one node’s mistakes are survivable while another’s are catastrophic
• one node can exit with less cost
• one node can impose terms through scarcity
• one node’s feedback has greater force
• one node receives more restoration support after failure

What It Does Not Measure

resource_asymmetry does not directly measure:

• whether one node is wrong
• whether all asymmetry is coercive
• whether resources should be equalized mechanically
• whether hierarchy is always incoherent
• whether specialization is exploitative
• whether support is domination
• whether stewardship is impossible
• whether different roles should have identical resources
• whether a resource-rich node is acting incoherently
• whether a resource-poor node is automatically correct
• whether all imbalances require removal

High resource_asymmetry means one side has significantly more usable capacity or leverage.

It does not automatically mean the interaction is unhealthy.

Low resource_asymmetry means resource conditions are more balanced.

It does not automatically mean the system is coherent, legitimate, or safe.

4) Canonical State Variables Involved

Canonical state vector:

S = {O, H, ε, ι, Au, µᵢ, BΣ, K, R, Φ}

Primary Variables

• R: restoration capacity often differs sharply across nodes
• BΣ: boundary integrity is affected when resource asymmetry changes refusal, access, consent, or exit conditions
• K: compatibility depends on whether asymmetry increases mutual coherence or dependency burden
• H: hidden debt rises when resource burden is exported or unacknowledged
• O: coherence depends on whether resource distribution supports system function and repair
• Au: asymmetry must be visible enough to audit its effects

Secondary Variables

• ε: visible errors may concentrate where resources are lowest
• ι: pseudo-coherence may arise when resource-rich nodes export debt to resource-poor nodes
• µᵢ: integrity can degrade when capacity, responsibility, and consequence are misaligned
• Φ: performance metrics may improve because under-resourced nodes absorb cost invisibly

Variables Commonly Confused With resource_asymmetry

5) Localization Signature

Primary Legibility Layers

• U1 — Power / Budgets: primary layer for money, labor, energy, time, compute, material support, and slack
• U2 — Configuration / Boundaries: where resources alter access, permissions, refusal, and constraints
• U3 — Execution: where resource differences affect what can actually be done
• U4 — Classification / Metrics / Narratives: where resource differences are interpreted, justified, hidden, or misclassified
• U5 — Coordination / Time: where resource asymmetry changes waiting capacity, delay cost, and escalation power
• U6 — Coherence Field: where asymmetry affects trust, legitimacy, compatibility, and whole-system coherence
• U7 — Memory / Recurrence: where resource imbalance becomes precedent, dependency, learned helplessness, or institutionalized burden

Primary Leverage Layers

• U1: rebalance resources, buffers, staffing, compute, money, or time
• U2: redesign access, refusal, appeal, repair, and exit conditions
• U3: improve execution support for lower-resource nodes
• U4: correct narratives that hide or distort asymmetry
• U5: adjust timing, escalation, and response windows to account for unequal capacity
• U7: update memory so resource burden is not erased

Verification Layers

• U1: who has what resources?
• U2: do resources change boundary or access conditions?
• U3: does resource difference affect execution?
• U5: does resource difference affect timing or delay burden?
• U6: does asymmetry improve or degrade coherence?
• U7: is asymmetry becoming structural memory?

Common Mislocalizations

• Treating resource difference as moral difference
• Treating formal equality as practical equality
• Treating underperformance as low integrity when resources differ
• Treating delay as unwillingness when capacity differs
• Treating compliance as consent when alternatives differ
• Treating exit as equally available when resources differ
• Treating repair failure as refusal when repair capacity differs
• Treating support as generosity while hidden obligation forms
• Treating resource-rich perspective as neutral
• Treating resource-poor signal as less credible
• Treating asymmetric burden as natural role fit
• Treating survival under unequal load as compatibility

6) Input Requirements

Required Inputs

To estimate resource_asymmetry, the system needs:

• nodes or systems being compared
• resource types involved
• resource quantities or relative capacities
• affected variables in S
• dependency_load
• exit_cost
• repair burden
• fallback options
• authority / influence distribution
• time and attention constraints
• access to information and audit
• access to appeal or review
• capacity to absorb harm
• capacity to impose cost
• affected-node feedback
• whether asymmetry is acknowledged or hidden

Optional Inputs

These improve precision:

• budget data
• staffing data
• compute / infrastructure access
• legal or procedural access
• time-to-response by node
• repair capacity by node
• appeal success by resource level
• exception access by resource level
• fallback maps
• switching-cost estimates
• resource flow maps
• contribution records
• unpaid labor or hidden work reports
• stress-test outcomes
• trust and legitimacy indicators
• public/private narrative comparison
• external support availability
• historical resource asymmetry trends

Missing Input Behavior

If resource_asymmetry inputs are missing:

• If resource type is unspecified, asymmetry may be misread
• If fallback options are unknown, practical power may be underestimated
• If repair capacity is unknown, restoration asymmetry may be hidden
• If time/attention capacity is unknown, delay burden may be misclassified
• If appeal access is unknown, formal rights may be overtrusted
• If affected-node feedback is missing, hidden burden may be invisible
• If resource flows are unknown, dependency and extraction may be undercounted
• If narrative around asymmetry is strong, audit whether it hides burden

Default missing-input posture:

map resources by type → compare practical capacities → trace effects on repair, exit, feedback, and boundaries → adjust interpretation

7) Diagnostic States / Ranges

These ranges are qualitative and should be domain-calibrated.

Healthy / Coherence-Supporting Range

Resource differences are known, role-appropriate, repairable, and do not distort consent, feedback, boundaries, or consequence.

Signals:

• asymmetry is acknowledged
• roles match capacity
• lower-resource nodes retain voice and refusal
• repair burden is not exported unfairly
• exit remains meaningful
• support does not become control
• feedback can challenge resource-rich nodes
• resource-rich nodes carry proportional responsibility
• resource-poor nodes receive needed support
• asymmetry improves K_real rather than degrading BΣ

Recommended posture:

maintain support structure
monitor dependency and exit cost
preserve MS symmetry
track repair burden over time

Watch Range

Resource asymmetry is beginning to affect participation, timing, repair, or boundary conditions.

Signals:

• one node can wait longer
• one node carries more hidden work
• one node depends on support for basic function
• feedback force differs
• exit becomes harder for lower-resource node
• repair access differs
• burden is acknowledged but not yet corrected
• resource-rich node sets pace or terms
• lower-resource node shows boundary strain

Recommended posture:

increase resource visibility
review repair burden
adjust timing expectations
protect feedback/exit pathways
rebalance support where needed

Degraded Range

Resource asymmetry distorts compatibility, repair, consent, attribution, or consequence.

Signals:

• continued participation reflects lack of alternatives
• one node absorbs damage it cannot repair
• resource-rich node can impose delay or terms
• lower-resource node cannot appeal effectively
• feedback from under-resourced node is discounted
• repair burden falls on those with least capacity
• exit cost is unequal
• asymmetry is denied or moralized
• performance depends on hidden burden
• boundary strain accumulates in the lower-resource node

Recommended posture:

activate MS review
rebalance repair support
restore exit/fallback
reduce dependency
correct narrative around burden
repair BΣ

Contraindicated:

declaring equal consent
deepening coupling
using formal equality as proof
scaling dependency
punishing lower-capacity failure without resource audit

Critical / Collapse-Prone Range

Resource asymmetry becomes coercive, extractive, or structurally destabilizing.

Signals:

• lower-resource node cannot refuse, leave, appeal, or repair
• resource-rich node controls essential access
• dependency becomes coercive
• repair burden is exported downward
• affected nodes carry chronic hidden cost
• legitimacy shock is likely if asymmetry is exposed
• system survival depends on invisible under-resourced labor
• boundary integrity collapses under resource pressure
• formal rules hide practical inequality
• exit or remedy requires external support

Recommended posture:

stop asymmetry-dependent expansion
restore minimum resources / fallback / exit
protect affected-node signal
redistribute repair burden
audit authority/resource linkage
repair hidden debt and memory

False Positive Risk

resource_asymmetry may appear dangerous when:

• unequal resources are appropriate to role
• stewardship includes stronger repair obligation
• specialization creates efficient mutual support
• temporary support is freely chosen and scoped
• resource-rich node is accountable and repair-capable
• asymmetry improves coherence without increasing exit cost
• lower-resource node retains meaningful voice, refusal, and repair access
• resource difference is visible and intentionally balanced by safeguards

False Negative Risk

resource_asymmetry may appear harmless when:

• formal rights are equal but practical capacity differs
• support hides dependency
• lower-resource nodes stop reporting burden
• resource-rich node controls narrative
• exit has never been tested
• unpaid labor is normalized
• time scarcity is invisible
• repair capacity differs but is not measured
• asymmetry only appears under stress
• performance metrics omit resource burden

8) Leading Indicators

resource_asymmetry degradation appears early as:

• one node waits while the other sets pace
• lower-resource node becomes quieter
• fallback options decay
• hidden labor increases
• repair tasks concentrate downward
• support creates obligation language
• resource-rich node interprets delay as neutrality
• exit becomes harder for one side
• feedback from lower-resource node has less effect
• exceptions are easier for resource-rich nodes
• boundary strain appears around access or time
• formal equality is repeated often
• resource constraints are framed as attitude
• under-resourced failure becomes identity label
• one node’s recovery depends on another’s depletion

9) Lagging Indicators

resource_asymmetry failure has already accumulated debt when:

• lower-resource node exits, collapses, or disengages
• hidden labor becomes visible after failure
• legitimacy shock follows burden exposure
• support/control inversion becomes clear
• repair burden must be redistributed externally
• dependency becomes coercive
• formal equality is no longer believed
• repeated failures trace to resource mismatch
• affected nodes cannot recover without new resources
• boundary rupture occurs from accumulated strain
• official memory omitted resource burden
• system must restructure around resource imbalance

10) Interpretation Rules

How to Read resource_asymmetry

resource_asymmetry should be read as:

context-specific imbalance in capacity that affects action, repair, feedback, exit, boundary, or consequence

It is not a general claim that unequal resources are incoherent.

A system may have:

• high asymmetry and high coherence if responsibility, repair, and safeguards scale with resources
• high asymmetry and low coherence if burden and dependency flow downward
• low asymmetry and low coherence if resources are equally insufficient
• high formal equality and high practical asymmetry
• resource asymmetry in one domain but symmetry in another
• high financial symmetry but low time, authority, or information symmetry
• asymmetry that becomes visible only under stress

What Changes Its Meaning

resource_asymmetry changes meaning under:

• high dependency_load
• high exit_cost
• low R_eff
• low EB
• weak FI_integrity
• low Au_eff
• high boundary_strain
• high repair_burden_asymmetry
• high AP(t)
• high Φ pressure
• low MS_symmetry_index
• high immunity_index
• high stress_divergence
• low affected-node access
• strong narrative protection

Context Modifiers

High dependency_load: asymmetry can become lock-in.

High exit_cost: continued participation becomes weak consent evidence.

Low R_eff: lower-resource nodes may not recover.

Low EB: resource burden may not be expressible.

Weak FI: feedback from lower-resource nodes may not change the system.

Low Au_eff: hidden labor and cost may disappear from record.

High boundary_strain: asymmetry may be damaging BΣ.

Low MS: asymmetry may become unequal standards.

High immunity: resource-rich nodes may become correction-resistant.

Domain Calibration Notes

resource_asymmetry should be calibrated by domain:

• in engineering: team capacity, ownership burden, infrastructure access, tooling, on-call load, technical debt
• in AI: compute access, data access, model access, tooling, memory control, user/system asymmetry
• in institutions: staffing, funding, authority, legal access, time, appeal capacity, service access
• in governance: public/private capacity, legal representation, resource access, enforcement leverage, remedy access
• in relationships: time, money, housing, support, emotional labor, mobility, social access, repair capacity
• in archives: source access, editing capacity, cross-link maintenance, canon authority, tool/platform resources

11) Operator Sequencing Implications

If resource_asymmetry Is Healthy / Accounted For

Allowed with ordinary gate checks:

• ⊗ coupling can proceed with safeguards
• Λ can evaluate compatibility realistically
• Π can define proportional responsibilities
• ℛ can route support to capacity gaps
• Γ can select roles based on capacity and repair obligations
• MS-Gate can pass with monitoring
• U7 memory can store resource assumptions

Recommended:

resource map → role/burden alignment → MS review → Π responsibility terms → ℛ support pathway → U7 update

If resource_asymmetry Is High or Degraded

Recommended:

pause symmetry claims → map resource differences → adjust burden/repair/exit conditions → restore feedback and appeal access

Or:

attenuate dependency → redistribute resources → repair BΣ → retest K_real

Avoid or delay:

• declaring equal consent
• deep coupling
• irreversible composition
• punitive consequence without resource audit
• scaling dependency
• interpreting silence as alignment
• treating formal equality as practical equality
• assigning repair burden to lower-capacity nodes

Operators Recommended Under High resource_asymmetry

• Au: reveal hidden resource flows and burdens
• MS-Gate: check whether standards and burdens are symmetrical
• Π: redesign responsibilities, access, and boundaries
• ℛ: provide repair support and rebalance capacity
• Λ: retest compatibility under real resource conditions
• Θ: damp overconfidence from resource-rich perspective
• Ξ: detect pseudo-coherence funded by hidden burden
• Γ: select dependency reduction or support allocation

Operators Contraindicated Under High resource_asymmetry

• Γ hard selection: may punish low-capacity symptoms
• Π equal formal constraint: may create practical asymmetry
• ⊗ deep coupling: may increase dependency and burden
• ⊕ composition: may erase asymmetry into shared identity
• Τ acceleration: may outrun under-resourced nodes
• Σ escalation: may sacralize unequal burdens
• ✕ force: leverages asymmetry into coercion

12) Gate Implications

Gates Strengthened By Reliable resource_asymmetry Reading

• MS-Gate: checks whether treatment accounts for unequal capacity
• Au-Actuation: resource flows and burdens are traceable
• FI-Gate: feedback from lower-resource nodes can correct the system
• High Risk Gate: prevents high-risk binding from resource-distorted signals
• ☷ᵢ: protects boundary and dignity principles under resource imbalance

Gates Weakened If resource_asymmetry Is Poorly Known

If resource asymmetry is unknown:

• MS may falsely pass formal equality
• Au may miss hidden labor and burden
• FI may not hear low-resource feedback
• High Risk Gate may allow identity/status binding from capacity-constrained behavior
• ☷ᵢ may apply principles without material conditions
• Π may impose equal rules on unequal capacity
• Γ may select from distorted performance evidence
• ℛ may fail to reach under-resourced nodes

Gate Outcomes Affected

High resource_asymmetry should push gates toward:

• Pause formal-symmetry claims
• Require resource map
• Require burden distribution review
• Require affected-node feedback
• Require exit/fallback review
• Require repair support
• Deny punitive classification from resource-limited behavior
• Deny equal-consent claims without exit capacity
• ∅ for high-impact coupling where resource asymmetry distorts consent, repair, or consequence

13) Scaling Behavior

resource_asymmetry becomes more consequential under scale because small imbalances compound across dependency, access, memory, and consequence systems.

As systems scale:

• resource-rich nodes gain more optionality
• resource-poor nodes absorb more friction
• hidden labor becomes infrastructure
• repair burden concentrates
• appeal access diverges
• exit cost diverges
• feedback force diverges
• narrative control concentrates
• technical or legal complexity favors resourced nodes
• low-resource failures become visible while high-resource causes remain hidden
• resource asymmetry becomes institutionalized
• formal equality hides practical inequality
• dependency deepens around resource access

Scaling Risks

• structural dependency
• extraction regime
• burden export
• appeal inequality
• repair inequality
• rank immunity
• hidden labor collapse
• under-resourced failure
• legitimacy shock
• formal equality / practical asymmetry split
• coercive dependency
• narrative capture
• boundary erosion
• resource lock-in
• pseudo-coherence through subsidized burden

Scaling Requirements

To scale resource asymmetry safely, systems need:

• resource maps
• hidden labor tracking
• burden distribution review
• repair support pathways
• appeal access support
• fallback support
• exit cost review
• time/attention accounting
• resource-to-responsibility alignment
• authority-to-accountability alignment
• affected-node feedback
• asymmetry-aware MS review
• stress testing under scarcity
• public/private burden comparison
• resource redistribution triggers
• role-specific capacity thresholds

Scaling Rule

Resource asymmetry must be matched by proportional responsibility, repair support, feedback access, and boundary protection.

Sanity constraint:

resource_asymmetry ↑ + exit_cost ↑ ⇒ coercive dependency risk ↑

If one node has fewer resources and higher exit cost, dependency can become coercive.

Second constraint:

resource_asymmetry ↑ + repair_burden_on_lower_resource_node ↑ ⇒ extraction risk ↑

If the lower-resource node carries repair burden, extraction risk rises.

Third constraint:

formal_symmetry + practical_resource_asymmetry ⇒ hidden debt risk ↑

If rules treat nodes equally while capacities differ sharply, hidden debt may accumulate.

14) Interaction / Coupling Behavior

resource_asymmetry reveals whether a relation, institution, AI system, archive, or interface is operating from real mutuality or hidden capacity imbalance.

What It Reveals About Coupling

• whether one node can shape terms more easily
• whether support creates obligation
• whether feedback has equal force
• whether refusal is equally available
• whether exit is equally possible
• whether repair burden is proportional
• whether one node absorbs hidden load
• whether performance depends on unequal capacity
• whether compatibility is real or resource-maintained

What It Reveals About Boundary Integrity

Resource asymmetry changes boundary conditions.

When resource_asymmetry is high:

• refusal may be harder for the lower-resource node
• exit may be more costly
• support can become leverage
• boundary strain may be under-expressed
• permission may be shaped by scarcity
• BΣ can erode without obvious force
• formal consent may not reflect practical freedom

What It Reveals About Compatibility

Compatibility requires resource-aware interpretation.

A coupling may be unsafe if:

one node’s coherence depends on the other absorbing under-resourced burden

or:

the lower-resource node cannot refuse, exit, repair, or contest without disproportionate cost

Healthy compatibility does not require identical resources, but it does require proportional responsibility, visible burden, and repair support.

Relevant Interface Acts

• ↺ Reflection: name capacity differences and hidden burden
• ⇩ Relaxation: reduce pressure on lower-resource nodes
• ⊘ Attenuation: reduce coupling when asymmetry is distorting consent
• ⊙ Alignment: calibrate one’s requests to real capacity
• →? Invitation: offer support without obligation capture
• ⚕︎ Restorative Override: requires post-action burden review
• ✕ Force: highly risky under resource asymmetry

15) Failure Modes Detected

Primary Failure Modes

resource_asymmetry detects or predicts:

• dependency trap
• coercive dependency
• burden export
• hidden labor collapse
• repair burden asymmetry
• appeal inequality
• feedback inequality
• exit-cost asymmetry
• boundary erosion
• under-resourced failure
• formal equality / practical inequality
• resource capture
• narrative capture
• rank immunity
• support/control inversion
• extraction regime
• pseudo-coherence funded by lower-resource nodes

Composite Regimes Where resource_asymmetry Matters

• Extraction Regime: resource-rich nodes gain while lower-resource nodes carry cost
• Coercive Fusion: lower-resource node cannot refuse or exit
• Goodhart Collapse: metrics improve through hidden burden
• Pseudo-Coherent Basin: stability depends on invisible under-resourced labor
• LOS: latent resource flows govern actual operation
• Crisis Loop: under-resourced repair causes recurrence
• Mission Lock: trajectory imposes burden on lower-capacity nodes
• Repair Theater: repair is promised without resource transfer
• Compression Collapse: scarcity narrows options for lower-resource nodes

16) Accountability & Reintegration Implications

If resource_asymmetry Was Ignored

Likely consequences:

• formal equality hid practical inequality
• lower-resource nodes carried hidden burden
• repair failed due to capacity mismatch
• exit was less available than assumed
• consent was overinterpreted
• dependency deepened
• feedback from lower-resource nodes had less force
• underperformance was misclassified
• resource-rich nodes avoided proportional responsibility
• hidden debt accumulated around unacknowledged capacity gaps

Accountability questions:

• Who had which resources?
• Who lacked which resources?
• Who carried burden?
• Who had fallback options?
• Who could exit?
• Who could appeal?
• Who could wait?
• Who could repair?
• Who could shape the narrative?
• Did responsibility scale with resources?
• Did support become control?
• Did formal equality create hidden asymmetry?

If resource_asymmetry Was Misread

Possible misread forms:

• healthy support mistaken for domination
• specialization mistaken for coercion
• unequal role capacity mistaken for unfairness by default
• resource-poor node treated as automatically correct
• resource-rich node treated as automatically incoherent
• equal treatment mistaken for fairness
• resource transfer mistaken for repair completion
• temporary support mistaken for dependency
• stewardship mistaken for control
• low resources mistaken for low integrity

Required Restoration

When resource_asymmetry failure is found:

map resource distribution
→ identify practical effects on feedback, repair, boundary, and exit
→ redistribute support or reduce demand
→ repair hidden burden
→ restore fallback and appeal access
→ correct narratives that erased asymmetry
→ update U7 memory

If resource asymmetry distorted standards or consequences, MS-Gate should review classifications, repair burden, appeal access, and responsibility distribution.

17) Cross-Domain Examples

Technical / Engineering

One team owns a critical service but lacks staffing, tooling, and authority to fix architectural causes. Other teams depend on it and blame delays.

Diagnostic implication: resource asymmetry is misread as execution failure.

Operator sequence: resource map → ownership/capacity repair → dependency review → R_eff allocation → U7 incident memory update.

Institutional / Governance

Two parties have the same formal appeal right, but one can afford legal support, time, and documentation while the other cannot.

Diagnostic implication: formal symmetry hides practical resource asymmetry.

Operator sequence: appeal access audit → support provision → MS review → repair procedural burden.

AI / Algorithmic

A user is expected to correct AI memory errors manually, while the system has far greater memory reach and classification persistence.

Diagnostic implication: correction burden is asymmetric between user and system.

Operator sequence: memory correction tools → user-facing audit access → HR gate tightening → U7 correction trace.

Interaction / Relational

One person has more time, money, housing stability, or social support. The other cannot refuse or renegotiate without major cost.

Diagnostic implication: participation is shaped by resource asymmetry and cannot be read as simple agreement.

Operator sequence: name capacity differences → restore exit/refusal support → rebalance repair burden → reassess K_real.

Archive / Framework Design

One module has many cross-links and maintenance resources, while another carries conceptual weight but lacks glossary support, causing drift.

Diagnostic implication: archive coherence depends on uneven maintenance capacity.

Operator sequence: module resource audit → cross-link support → glossary maintenance → U7 dependency update.

18) Test Protocols

1. Resource Map Test

Who has what resources, and who lacks them?

Failure signal: resource conditions are assumed rather than mapped.

2. Capacity-to-Burden Test

Does each node’s burden match its capacity?

Failure signal: lower-capacity nodes carry higher burden.

3. Repair Capacity Test

Who can repair damage?

Failure signal: harmed or lower-resource nodes must supply restoration.

4. Exit Capacity Test

Can each node leave or renegotiate?

Failure signal: exit is unequal because resources differ.

5. Feedback Force Test

Does feedback from each node have comparable effect?

Failure signal: resource-rich feedback changes the system more easily.

6. Appeal Access Test

Can each node challenge outcomes practically?

Failure signal: formal appeal exists but resource barriers differ.

7. Waiting Capacity Test

Who can afford delay?

Failure signal: one node can wait, the other degrades.

8. Hidden Labor Test

Is one node supplying invisible work?

Failure signal: performance depends on unacknowledged labor.

9. Stress Test

Does asymmetry widen under stress?

Failure signal: lower-resource nodes collapse first while metrics blame them.

10. Narrative Test

Does the system’s story acknowledge resource asymmetry?

Failure signal: narrative treats unequal capacity as equal choice.

19) Anti-Patterns

• Formal equality as practical equality
• Resource-rich perspective as neutral
• Resource-poor failure as identity
• Support as control
• Hidden labor as natural role
• Equal rules on unequal capacity
• Consent without exit capacity
• Appeal without resources
• Feedback without force
• Underperformance without capacity audit
• Waiting as neutral
• Time scarcity ignored
• Repair burden on the depleted node
• Resource transfer as full repair
• Dependency as gratitude
• Scarcity as attitude
• Stability funded by invisible burden
• Authority without proportional responsibility
• Lower-resource signal as less credible
• Performance metrics without burden accounting

20) Spec Validation Check

• Is this truly a diagnostic, not an operator? Yes.
• Does it measure state, capacity, risk, or response rather than act directly? Yes.
• Does it map to S? Yes.
• Are U-layers specified? Yes.
• Are leading and lagging indicators separated? Yes.
• Are interpretation risks defined? Yes.
• Are operator sequencing implications clear? Yes.
• Are gate implications clear? Yes.
• Are scaling risks included? Yes.
• Are interaction implications included? Yes.
• Does it avoid new primitives? Yes.

Condensed Archive Summary

resource_asymmetry is the diagnostic estimate of the imbalance in available resources, capacity, leverage, access, repair capability, time, energy, money, compute, attention, authority, fallback options, or operational support between coupled nodes, roles, systems, or subfields. It does not treat unequal resources as automatically incoherent; asymmetry can be healthy when role-appropriate, visible, repairable, and matched by proportional responsibility. High resource_asymmetry indicates risk of dependency traps, exit-cost asymmetry, repair-burden export, feedback inequality, appeal inequality, boundary erosion, support/control inversion, hidden labor collapse, formal equality hiding practical inequality, and pseudo-coherence funded by under-resourced nodes. Under high resource_asymmetry, the system should map capacities, adjust burden and repair obligations, protect feedback and exit pathways, restore fallback options, and run MS-Gate review before equal-consent claims, punitive classification, deep coupling, or scaling dependency.