schema_version: "1.0"

id: "FM-ECO-023"

title: "FM-ECO-023 — Asymmetric Bandwidth"

slug: "fm-eco-023-asymmetric-bandwidth"

type: "failure_mode"

status: "draft"

version: "0.1.0"

last_updated: "2026-06-19"

summary: "Asymmetric Bandwidth occurs when one economic node, institution, platform, buyer, seller, employer, regulator, contractor, or interface possesses far greater capacity to send, process, negotiate, delay, document, contest, automate, or absorb signals than another, producing distorted exchange, coerced participation, hidden burden, and degraded local coherence."

canonical_url: "/archive/failure-modes/registry/economy/fm-eco-023-asymmetric-bandwidth"

citation_id: "FM-ECO-023-v0-1-0"

canon:

tier: "registry"

state: "draft"

source: "UTS — Failure Modes Registry"

source_id: "FM-ECO-023"

legacy_ids:

• "FM-ECOX-019"

classification:

family: "failure-modes"

module: "economy"

module_group: "economy"

density: "advanced-reference"

audience:

• "UTS readers"
• "economic systems researchers"
• "cybernetics researchers"
• "contract researchers"
• "justice researchers"
• "restoration researchers"
• "AI governance researchers"
• "platform researchers"
• "coherence researchers"
• "machine readers"

tags:

• "failure-modes"
• "economy"
• "asymmetric-bandwidth"
• "fm-eco-023-asymmetric-bandwidth"
• "fm-ecox-019-asymmetric-bandwidth"
• "bandwidth"
• "information-asymmetry"
• "negotiation"
• "contracts"
• "platforms"
• "capacity-asymmetry"
• "hidden-debt"
• "coherence"

aliases:

• "Asymmetric Bandwidth"
• "Economic Asymmetric Bandwidth"
• "Bandwidth Asymmetry"
• "Negotiation Bandwidth Asymmetry"
• "Processing Capacity Asymmetry"
• "Documentation Asymmetry"
• "Interface Bandwidth Asymmetry"
• "Institutional Bandwidth Advantage"
• "Attention Capacity Asymmetry"
• "Signal Processing Imbalance"

related:

laws:

• "Asymmetric Bandwidth Coupling"
• "Consent Drift"
• "Coercive Contract"
• "Conditional Coercive Delivery"
• "Forced Profit"
• "Suppression-by-Abstraction"
• "Auditability Collapse"
• "Success Proxy Substitution"
• "Parasitic Extraction"
• "Under-Delivery"
• "Hidden Debt Accumulation"
• "Victim Burden Inversion"

invariants:

• "Exchange Requires Sufficient Bidirectional Bandwidth"
• "Consent Requires Processing Capacity"
• "Negotiation Must Not Depend on Bandwidth Domination"
• "Documentation Must Not Become Burden Weapon"
• "Interface Load Must Remain Proportional"
• "High-Bandwidth Nodes Must Not Export Processing Burden"
• "Economic Signals Must Remain Receivable"

operators:

• "Ψ — Observation / Interface"
• "Φ — Flow / Resource Movement"
• "Γ — Selection"
• "BΣ — Boundary Integrity"
• "K — Constraint / Load"
• "H — Hidden Debt"
• "Au — Auditability"
• "Λ — Compatibility"
• "R — Restoration Capacity"
• "G — Gain"
• "D — Damping"
• "O — Coherence"
• "Τ — Trajectory / Time"

gates:

• "Bandwidth Symmetry Gate"
• "Consent Gate"
• "Interface Load Gate"
• "Negotiation Gate"
• "Documentation Gate"
• "Auditability Gate"
• "Capacity Gate"
• "Exit Gate"
• "Restoration Gate"

diagnostics:

• "Bandwidth Symmetry"
• "Processing Capacity"
• "Negotiation Capacity"
• "Documentation Burden"
• "Interface Load"
• "Signal Receivability"
• "Consent Validity"
• "Hidden Debt"
• "Auditability"
• "Local Coherence"

failure_modes:

• "FM-ISC-006 — Asymmetric Bandwidth Coupling"
• "FM-ECO-013 — Conditional Coercive Delivery"
• "FM-ECO-018 — Suppression-by-Abstraction"
• "FM-ECO-021 — “No Alternative” Framing"
• "FM-ECO-025 — Coercive Contract"
• "FM-ECO-026 — Dependency Lock-In"
• "FM-ECO-027 — Extraction Masking Instability"
• "FM-CORE-004 — Auditability Collapse"
• "FM-ISC-009 — Consent Drift"
• "FM-C-021 — Parasitic Extraction"
• "FM-JC-007 — Manufactured Consent"
• "FM-RX-005 — Victim Burden Inversion"

restoration_arcs:

• "Bandwidth Symmetry Audit"
• "Interface Load Reduction"
• "Negotiation Capacity Restoration"
• "Documentation Burden Reduction"
• "Consent Revalidation"
• "Signal Receivability Repair"
• "Processing Support Provision"
• "Auditability Restoration"
• "Asymmetry Debt Accounting"
• "Local Coherence Restoration"

modules:

• "Economy"
• "Interactions"
• "Cybernetics"
• "Contracts"
• "Justice"
• "Restoration"
• "AI Governance"
• "Security"
• "Interfaces"
• "Coherence"

navigation:

order: 1323

parent: "failure-modes"

visible: true

provenance:

created_from: "failure-mode-registry-production"

source_thread: "UTS Failure Modes Registry production"

source_file: "content/archive/failure-modes/registry/economy/fm-eco-023-asymmetric-bandwidth.md"

legacy_source_file: "content/archive/failure-modes/registry/economy/fm-ecox-019-asymmetric-bandwidth.md"

notes: "Unified from former FM-ECOX-019 into continuous Economy namespace. Standalone economy entry focused on asymmetric capacity to process, negotiate, document, contest, automate, delay, communicate, or absorb signals in economic exchange, contracts, platforms, institutions, labor systems, and interfaces."

entry:

failure_mode_id: "FM-ECO-023"

failure_family: "Economy"

production_treatment: "Standalone Entry"

legacy_ids:

• "FM-ECOX-019"

parent_modes:

• "FM-ISC-006 — Asymmetric Bandwidth Coupling"
• "FM-ISC-009 — Consent Drift"
• "FM-ECO-025 — Coercive Contract"
• "FM-CORE-004 — Auditability Collapse"
• "FM-C-021 — Parasitic Extraction"

first_gate_failure: "Bandwidth Symmetry Gate"

primary_hidden_debt: "Hidden debt accumulates when lower-bandwidth nodes must process excessive terms, signals, documents, interfaces, delays, claims, disputes, options, or obligations created by higher-bandwidth nodes, causing attention depletion, missed rights, coerced acceptance, under-contestation, and local degradation."

primary_inversion: "Capacity advantage becomes legitimacy; the system treats agreements, responses, defaults, or non-contestation as valid even when one side lacked sufficient bandwidth to understand, negotiate, contest, or respond."

primary_boundary_pattern: "The boundary between valid participation and overloaded participation collapses; the lower-bandwidth node appears to participate while actually carrying an unacknowledged processing burden."

primary_signature: "One node can generate, process, delay, document, automate, or contest far more than another; the lower-bandwidth node loses agency; formal exchange appears valid; hidden burden and consent debt accumulate."

FM-ECO-023 — Asymmetric Bandwidth

Status: Draft

Archive Type: Failure Mode

System: Universal Theory Stack

Parent: Failure Modes

Canon Tier: Registry

Registry: Failure Modes Registry

Entry ID: FM-ECO-023

Legacy ID: FM-ECOX-019

Family: Economy

Production Treatment: Standalone Entry

Parent Modes: FM-ISC-006 — Asymmetric Bandwidth Coupling; FM-ISC-009 — Consent Drift; FM-ECO-025 — Coercive Contract; FM-CORE-004 — Auditability Collapse; FM-C-021 — Parasitic Extraction

0. Economic Scope Note

This entry is conceptual and systems-oriented.

It does not treat unequal scale, specialization, expertise, automation, institutional capacity, documentation, negotiation, or advanced processing capability as inherently failed.

Some economic nodes naturally have more bandwidth than others.

Bandwidth advantage can be coherent when it is:

• transparent
• proportionate
• non-exploitative
• paired with support
• refusal-valid
• auditable
• not used to overload
• not used to obscure terms
• not used to delay weaker nodes
• not used to manufacture consent
• compatible with affected-node capacity
• balanced by explanation, simplification, appeal, representation, or assistance

The failure begins when bandwidth asymmetry becomes leverage.

The issue is not unequal capacity.

The issue is one node’s processing advantage becoming another node’s burden.

Asymmetric Bandwidth occurs when economic participation is formally available but practically shaped by unequal signal, documentation, negotiation, interface, or contestation capacity.

1. Definition

Asymmetric Bandwidth occurs when one economic node, institution, platform, buyer, seller, employer, regulator, contractor, or interface possesses far greater capacity to send, process, negotiate, delay, document, contest, automate, or absorb signals than another, producing distorted exchange, coerced participation, hidden burden, and degraded local coherence.

The asymmetry may involve:

• legal teams
• contract complexity
• pricing complexity
• documentation volume
• automated notices
• claim processes
• appeal processes
• delay capacity
• negotiation resources
• interface complexity
• customer support queues
• institutional memory
• audit capacity
• data access
• forecasting capacity
• financial modeling
• dispute handling
• compliance burden
• procurement requirements
• grant applications
• insurance claims
• loan terms
• platform rules
• AI-mediated support or enforcement
• algorithmic decision systems

The core failure is:

bandwidth asymmetry↑
lower-node processing capacity↓
valid participation↓
consent validity↓
H↑

Asymmetric Bandwidth is not merely information asymmetry.

It is capacity asymmetry across communication, processing, attention, documentation, timing, negotiation, and contestation.

2. Core Pattern

The core pattern is:

1. Two or more nodes enter an economic relation.
2. One node has much greater ability to generate, process, interpret, delay, automate, or contest signals.
3. The high-bandwidth node structures terms, interfaces, timelines, requirements, or dispute pathways.
4. The lower-bandwidth node must process more than it can coherently carry.
5. The lower-bandwidth node misses details, accepts defaults, fails to contest, loses timing windows, or cannot negotiate.
6. The system interprets acceptance, silence, delay, or incomplete response as valid participation.
7. The higher-bandwidth node records formal legitimacy.
8. Hidden debt accumulates in the lower-bandwidth node.
9. Restoration requires reducing the bandwidth gap or compensating for it structurally.

This failure often appears as:

the terms were available

while the hidden truth may be:

but not receivable at the affected node’s bandwidth

or:

they did not object

while the overlooked condition is:

they did not have the capacity to contest

The restorative question is:

could the lower-bandwidth node actually receive, process, and respond coherently?

Asymmetric Bandwidth turns overload into apparent agreement.

3. Failure Signature

Typical signature:

high-node bandwidth↑
low-node processing capacity↓
interface load↑
documentation burden↑
contestability↓
consent validity↓
H↑

Extended signature:

contracts are readable only to specialized counsel
appeal processes require more time than affected nodes have
platform rules change faster than users can track
institutions can delay longer than individuals can survive
automated notices exceed human response capacity
pricing structures require analysis the buyer cannot perform
claims systems demand documentation the claimant cannot assemble

Common forms include:

a corporation negotiates against an individual without representation
a platform updates terms more often than users can meaningfully review
an employer controls scheduling data while workers cannot audit hours
a lender presents complex terms to a borrower with no processing support
a government relief form requires documentation affected nodes cannot obtain
an insurer delays and requests repeated information until claimants lose capacity
an AI platform automates enforcement while human appeal capacity is slow
a procurement system excludes small providers through documentation load
a contractor uses change-order complexity to control payment timing

The defining condition is not that one side knows more.

The defining condition is that one side’s bandwidth advantage shapes the exchange in ways the other side cannot coherently process, contest, or exit.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: stronger nodes fund legal, technical, procedural, and delay capacity unavailable to weaker nodes.
• U2 — Configuration / Boundaries: interfaces, contracts, policies, and procedures encode the asymmetry.
• U3 — Execution / Runtime: lower-bandwidth nodes experience process overload during actual participation.
• U4 — Information / Truth: formal availability substitutes for receivability truth.
• U5 — Coordination / Time: deadlines, delays, and response windows favor high-bandwidth nodes.
• U6 — Coherence Field: formal process creates legitimacy aura.
• U7 — Memory / Recurrence: repeated asymmetry becomes standard practice.
• U8 — Environment / Field: institutional complexity raises baseline bandwidth requirements.

Common manifestation layers:

• U1 — Power: capacity advantage becomes leverage.
• U2 — Boundaries: terms and procedures encode load.
• U3 — Execution: lower-bandwidth nodes overload.
• U4 — Truth: silence or default is counted as participation.
• U5 — Time: timing favors the stronger node.
• U6 — Field: formality masks overload.
• U8 — Environment: complexity normalizes asymmetry.

Asymmetric Bandwidth is primarily a U2 interface / U5 timing / Ψ observation failure, anchored by U1 capacity asymmetry.

The system counts a signal as delivered even when it was not receivable.

5. Typical Development Sequence

A common development sequence is:

1. A relation forms between high-bandwidth and lower-bandwidth nodes.
2. The high-bandwidth node defines terms, processes, documentation, timelines, or interfaces.
3. The process appears formally neutral.
4. The lower-bandwidth node must interpret, respond, document, contest, or decide.
5. The load exceeds local capacity.
6. The lower-bandwidth node accepts defaults, misses deadlines, gives incomplete responses, or fails to contest.
7. The system treats this as agreement, noncompliance, waiver, or low priority.
8. The high-bandwidth node gains advantage.
9. The lower-bandwidth node accumulates hidden burden, lost rights, unpaid cost, or dependency.
10. Future asymmetry deepens because the lower-bandwidth node has less capacity after the first round.

The loop often looks like:

complex terms → lower-node overload → missed response → high-node advantage → more complex terms

Another common loop is:

delay by strong node → capacity depletion in weak node → weaker contestation → stronger node delays again

Asymmetric Bandwidth becomes self-reinforcing when overload reduces the already-limited capacity needed to resist future overload.

6. Diagnostic Markers

Diagnostic markers include:

• Terms are technically available but practically unreadable.
• One side can delay longer than the other can endure.
• Response windows are short for affected nodes but long for institutions.
• Documentation requirements exceed affected-node capacity.
• Non-response is treated as consent or waiver.
• Appeals require specialized knowledge, time, or representation.
• The high-bandwidth node can automate notices while the lower-bandwidth node must respond manually.
• Process complexity deters contestation.
• Default settings favor the higher-bandwidth node.
• Lower-bandwidth nodes repeatedly fail at the same procedural step.
• The system measures whether information was sent, not whether it was receivable.
• Affected nodes need intermediaries to participate at all.
• Hidden costs appear as time, attention, stress, missed deadlines, and lost claims.
• Restoration improves when interfaces, timelines, and documentation are simplified or supported.

Useful diagnostics:

• Bandwidth Symmetry: Compares capacity to send, receive, process, contest, and delay.
• Processing Capacity: Tests whether affected nodes can understand and act.
• Negotiation Capacity: Measures ability to bargain or amend terms.
• Documentation Burden: Measures proof, paperwork, and procedural load.
• Interface Load: Measures cognitive, temporal, technical, and logistical burden.
• Signal Receivability: Tests whether notice or information can be used by the recipient.
• Consent Validity: Tests whether agreement was bandwidth-valid.
• Hidden Debt: Tracks burden created by overload.
• Auditability: Determines whether asymmetry and its effects can be traced.
• Local Coherence: Tests whether exchange improves or degrades affected nodes.

7. Related Gates

Relevant gates include:

• Bandwidth Symmetry Gate: Fails when participation assumes capacity the receiving node does not have.
• Consent Gate: Fails when agreement is counted despite processing overload.
• Interface Load Gate: Fails when interfaces impose more burden than the node can carry.
• Negotiation Gate: Fails when bargaining capacity is too asymmetric for fair exchange.
• Documentation Gate: Fails when proof requirements block valid claims.
• Auditability Gate: Fails when bandwidth asymmetry cannot be inspected.
• Capacity Gate: Fails when local processing capacity is exceeded.
• Exit Gate: Fails when exit requires more bandwidth than the node has.
• Restoration Gate: Fails when repair processes overload the affected node.

The first common gate failure is usually the Bandwidth Symmetry Gate.

The system assumes both sides can participate in the same signal field.

8. Related Operators

Relevant operators include:

• Ψ — Observation / Interface: Primary operator; determines whether signals are receivable.
• Φ — Flow / Resource Movement: Moves documents, notices, terms, payments, claims, and responses.
• Γ — Selection: Selects process, defaults, timelines, and procedural burden.
• BΣ — Boundary Integrity: Protects or violates agency boundaries under overload.
• K — Constraint / Load: Rises through documentation, timing, and processing burden.
• H — Hidden Debt: Accumulates as attention debt, missed claims, and coerced defaults.
• Au — Auditability: Reveals asymmetry and burden pathways.
• Λ — Compatibility: Tests whether the interface fits the node’s bandwidth.
• R — Restoration Capacity: Must support lower-bandwidth nodes in repair.
• G — Gain: Incentivizes high-bandwidth nodes to exploit process advantage.
• D — Damping: Should slow or simplify exchanges when asymmetry is high.
• O — Coherence: May appear high because formal process is complete.
• Τ — Trajectory / Time: Governs deadlines, delays, response windows, and attrition.

Common operator pattern:

high-bandwidth node sets Ψ interface
Γ selects complex terms / deadlines
Φ sends signals
lower node cannot process
K rises
BΣ weakens through overload
silence or default is counted as agreement
Au fails to capture receivability gap
H accumulates

The core operator inversion is:

information sent → information received

instead of:

information sent + bandwidth fit + processing capacity + response viability → information received

Asymmetric Bandwidth turns transmission into false participation.

9. Related Laws and Invariants

Related Laws

• Asymmetric Bandwidth Coupling: parent interaction mechanism.
• Consent Drift: agreement degrades as bandwidth imbalance grows.
• Coercive Contract: terms exploit processing asymmetry.
• Conditional Coercive Delivery: support is gated through bandwidth-heavy processes.
• Forced Profit: bandwidth advantage can extract profit.
• Suppression-by-Abstraction: complexity hides concrete burden.
• Auditability Collapse: affected nodes cannot trace what happened.
• Success Proxy Substitution: formal completion replaces actual understanding.
• Parasitic Extraction: higher-bandwidth nodes draw value from lower-bandwidth burden.
• Under-Delivery: support exists but is not usable.
• Hidden Debt Accumulation: overload stores future cost.
• Victim Burden Inversion: affected nodes must carry proof, appeal, and repair load.

Related Invariants

• Exchange Requires Sufficient Bidirectional Bandwidth: participation must be receivable both ways.
• Consent Requires Processing Capacity: agreement is invalid if the node cannot understand or respond.
• Negotiation Must Not Depend on Bandwidth Domination: bargaining must not be won through overload.
• Documentation Must Not Become Burden Weapon: proof requirements must not erase valid claims.
• Interface Load Must Remain Proportional: process burden must fit receiving capacity.
• High-Bandwidth Nodes Must Not Export Processing Burden: capacity advantage must not become extraction.
• Economic Signals Must Remain Receivable: sent information is not enough.

10. Common False Positives

Not every bandwidth difference is Asymmetric Bandwidth.

Common false positives include:

• Complex terms paired with explanation and representation.
• Institutional capacity used to reduce burden for lower-bandwidth nodes.
• Automation that simplifies participation.
• Documentation requirements proportional to real need.
• Expert negotiation where both sides have adequate support.
• Longer timelines granted to lower-bandwidth nodes.
• Interfaces tested for actual receivability.
• High-volume communication with clear summaries and decision points.
• Legal or technical complexity paired with assistance and appeal.
• Defaults designed in favor of the lower-bandwidth node.
• Formal notice plus confirmation of understanding.
• Capacity asymmetry that does not affect consent, exchange, or repair.

Clarifying rule:

This is not Asymmetric Bandwidth unless unequal processing, communication, negotiation, documentation, delay, contestation, or interface capacity distorts participation, suppresses consent, exports burden, or degrades local coherence.

11. Common False Repairs

Common false repairs include:

• sending more information
• adding longer documents
• creating portals that are harder to use
• requiring confirmation checkboxes
• offering support only through overloaded channels
• adding appeal rights that require expert navigation
• simplifying language while preserving hidden complexity
• increasing notification frequency until attention collapses
• creating help pages instead of reducing burden
• offering representation after deadlines pass
• blaming lower-bandwidth nodes for non-response
• automating denial faster than humans can contest
• treating access to information as understanding
• giving equal deadlines to unequal nodes
• moving support to AI chat without real escalation

False repair often produces the loop:

bandwidth asymmetry exposed → more information provided → processing burden rises → asymmetry deepens

Another common loop is:

appeal path added → appeal path complex → lower-bandwidth node cannot use it → formal legitimacy preserved

The repair fails because it increases nominal access while leaving bandwidth fit unrepaired.

12. Restoration Direction

Restoration requires measuring bandwidth asymmetry, reducing interface and documentation burden, restoring processing support, extending response viability, revalidating consent, and repairing losses created by overloaded participation.

Primary restoration direction:

measure bandwidth fit,
reduce interface load,
restore contestability,
and repair asymmetry debt

A fuller restoration path includes:

1. Name the relation. Identify the economic exchange, contract, platform process, claim, negotiation, or interface.
2. Map bandwidth capacities. Compare each node’s ability to send, receive, process, delay, document, contest, and absorb signals.
3. Identify asymmetry leverage. Determine how the higher-bandwidth node benefits.
4. Measure interface load. Quantify documents, steps, deadlines, portals, terms, proof, and cognitive burden.
5. Test signal receivability. Confirm whether the lower-bandwidth node can actually understand and respond.
6. Reduce documentation burden. Remove unnecessary proof, repetition, or complexity.
7. Simplify decision points. Make obligations, choices, costs, and rights legible.
8. Provide processing support. Offer representation, explanation, translation, assistance, or human escalation.
9. Extend timing windows. Adjust deadlines to real processing capacity.
10. Restore contestability. Make objections, appeals, renegotiation, and correction usable.
11. Revalidate consent. Reassess agreements made under overload.
12. Repair asymmetry debt. Address missed claims, waived rights, delayed payments, or coerced defaults.
13. Install bandwidth gates. Require receivability checks before decisions are considered valid.
14. Preserve auditability. Track what was sent, received, understood, contested, and resolved.
15. Validate local coherence. Confirm participation becomes usable for lower-bandwidth nodes.

A valid restoration path should reduce:

interface overload
documentation burden
deadline asymmetry
processing depletion
missed claims
coerced defaults
consent debt
contestability loss
H

Asymmetric Bandwidth is not repaired by giving the lower-bandwidth node more to process.

It is repaired by making participation fit the bandwidth of the node expected to participate.

13. Cross-Module Links

• Economy: Core failure of economic participation, contracts, claims, pricing, platforms, procurement, employment, and institutional exchange.
• Interactions: Direct domain expression of asymmetric bandwidth coupling.
• Cybernetics: Signal transmission, processing capacity, latency, and feedback loops become asymmetric.
• Contracts: Complexity, timing, and documentation can create coerced acceptance.
• Justice: Remedy fails when affected nodes cannot carry proof, appeal, or contestation burden.
• Restoration: Repair pathways must not overload the harmed node.
• AI Governance: AI-mediated notices, moderation, appeals, pricing, consent, and terms can scale high-bandwidth enforcement against low-bandwidth users.
• Security: Security interfaces can impose excessive proof or response load on weaker nodes.
• Interfaces: Interface design determines whether participation is actually possible.
• Coherence: Coherent exchange requires receivable signals and usable response capacity.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry

This mode maps upward to:

• FM-ISC-006 — Asymmetric Bandwidth Coupling
• FM-ISC-009 — Consent Drift
• FM-ECO-025 — Coercive Contract
• FM-CORE-004 — Auditability Collapse
• FM-C-021 — Parasitic Extraction

Sibling or related Economy modes include:

• FM-ECO-013 — Conditional Coercive Delivery
• FM-ECO-018 — Suppression-by-Abstraction
• FM-ECO-021 — “No Alternative” Framing
• FM-ECO-025 — Coercive Contract
• FM-ECO-026 — Dependency Lock-In
• FM-ECO-027 — Extraction Masking Instability
• FM-ECO-028 — Repair Starvation

Related cross-family modes include:

• FM-ISC-006 — Asymmetric Bandwidth Coupling
• FM-ISC-009 — Consent Drift
• FM-ISC-011 — Invisible Intrusion
• FM-ISC-015 — Force Masked as Care
• FM-CORE-004 — Auditability Collapse
• FM-C-015 — Proxy-Relay Drift
• FM-C-021 — Parasitic Extraction
• FM-JC-007 — Manufactured Consent
• FM-JC-010 — Proxy-Relay Obfuscation
• FM-JC-011 — Locked-In Renegotiation Failure
• FM-RX-005 — Victim Burden Inversion
• FM-SEC-004 — Consent Theater / Invalid Authorization

Aliases preserved from source material:

• Asymmetric Bandwidth
• Economic Asymmetric Bandwidth
• Bandwidth Asymmetry
• Negotiation Bandwidth Asymmetry
• Processing Capacity Asymmetry
• Documentation Asymmetry
• Interface Bandwidth Asymmetry
• Institutional Bandwidth Advantage
• Attention Capacity Asymmetry
• Signal Processing Imbalance

Legacy source preserved:

legacy_ids:
  - "FM-ECOX-019"
deprecated_source_ids:
  - "FM-ECOX-019"
source_aliases:
  - "Economy Extended Entry 019"

15. Minimal Entry Version

Definition: Asymmetric Bandwidth occurs when one economic node, institution, platform, buyer, seller, employer, regulator, contractor, or interface possesses far greater capacity to send, process, negotiate, delay, document, contest, automate, or absorb signals than another, producing distorted exchange, coerced participation, hidden burden, and degraded local coherence.

Signature:

high-node bandwidth↑
low-node processing capacity↓
interface load↑
documentation burden↑
contestability↓
consent validity↓
H↑

Restoration direction:

• name the relation
• map bandwidth capacities
• identify asymmetry leverage
• measure interface load
• test signal receivability
• reduce documentation burden
• simplify decision points
• provide processing support
• extend timing windows
• restore contestability
• revalidate consent
• repair asymmetry debt
• install bandwidth gates
• preserve auditability
• validate local coherence

16. Machine-Readable Summary

failure_mode:
  id: "FM-ECO-023"
  name: "Asymmetric Bandwidth"
  family: "Economy"
  production_treatment: "Standalone Entry"
  legacy_ids:
    - "FM-ECOX-019"
  parent_modes:
    - "FM-ISC-006 — Asymmetric Bandwidth Coupling"
    - "FM-ISC-009 — Consent Drift"
    - "FM-ECO-025 — Coercive Contract"
    - "FM-CORE-004 — Auditability Collapse"
    - "FM-C-021 — Parasitic Extraction"
  primary_failure: "Unequal processing, communication, negotiation, documentation, delay, contestation, or interface capacity distorts participation, suppresses consent, exports burden, or degrades local coherence."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ECO-023"
  deprecated_source_ids:
    - "FM-ECOX-019"
  scope_note: "Conceptual and systems-oriented; does not treat unequal scale, specialization, expertise, automation, institutional capacity, documentation, negotiation, or advanced processing capability as inherently failed."
  aliases:
    - "Asymmetric Bandwidth"
    - "Economic Asymmetric Bandwidth"
    - "Bandwidth Asymmetry"
    - "Negotiation Bandwidth Asymmetry"
    - "Processing Capacity Asymmetry"
    - "Documentation Asymmetry"
    - "Interface Bandwidth Asymmetry"
    - "Institutional Bandwidth Advantage"
    - "Attention Capacity Asymmetry"
    - "Signal Processing Imbalance"
  signature:
    - "high-node bandwidth↑"
    - "low-node processing capacity↓"
    - "interface load↑"
    - "documentation burden↑"
    - "contestability↓"
    - "consent validity↓"
    - "H↑"
  primary_layers:
    origin:
      - "U1 — Power / Budgets"
      - "U2 — Configuration / Boundaries"
      - "U3 — Execution / Runtime"
      - "U4 — Information / Truth"
      - "U5 — Coordination / Time"
      - "U6 — Coherence Field"
      - "U7 — Memory / Recurrence"
      - "U8 — Environment / Field"
    manifestation:
      - "U1 — Power"
      - "U2 — Boundaries"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U5 — Time"
      - "U6 — Field"
      - "U8 — Environment"
  state_variables:
    - "Ψ"
    - "Φ"
    - "Γ"
    - "BΣ"
    - "K"
    - "H"
    - "Au"
    - "Λ"
    - "R"
    - "G"
    - "D"
    - "O"
    - "Τ"
  first_gate_failure: "Bandwidth Symmetry Gate"
  restoration:
    - "Bandwidth Symmetry Audit"
    - "Interface Load Reduction"
    - "Negotiation Capacity Restoration"
    - "Documentation Burden Reduction"
    - "Consent Revalidation"
    - "Signal Receivability Repair"
    - "Processing Support Provision"
    - "Auditability Restoration"
    - "Asymmetry Debt Accounting"
    - "Local Coherence Restoration"