schema_version: "1.0"

id: "FM-ISC-006"

title: "FM-ISC-006 — Asymmetric Bandwidth Coupling"

slug: "fm-isc-006-asymmetric-bandwidth-coupling"

type: "failure_mode"

status: "draft"

version: "0.1.0"

last_updated: "2026-06-19"

summary: "Asymmetric Bandwidth Coupling occurs when two or more nodes, systems, roles, interfaces, institutions, or relational fields are coupled while possessing unequal capacity to send, receive, process, contest, verify, refuse, repair, or absorb signals, causing one side to dominate the interaction bandwidth while the other carries compression, delay, overload, or hidden debt."

canonical_url: "/archive/failure-modes/registry/interactions-signals-couplings/fm-isc-006-asymmetric-bandwidth-coupling"

citation_id: "FM-ISC-006-v0-1-0"

canon:

tier: "registry"

state: "draft"

source: "UTS — Failure Modes Registry"

source_id: "FM-ISC-006"

classification:

family: "failure-modes"

module: "interactions-signals-couplings"

module_group: "isc"

density: "advanced-reference"

audience:

• "UTS readers"
• "interaction researchers"
• "signal systems researchers"
• "cybernetics researchers"
• "AI governance researchers"
• "interface researchers"
• "justice researchers"
• "restoration researchers"
• "coherence researchers"
• "machine readers"

tags:

• "failure-modes"
• "isc"
• "interactions"
• "signals"
• "couplings"
• "asymmetric-bandwidth-coupling"
• "fm-isc-006-asymmetric-bandwidth-coupling"
• "bandwidth-asymmetry"
• "asymmetric-coupling"
• "capacity"
• "interface"
• "hidden-debt"
• "coherence"

aliases:

• "Asymmetric Bandwidth Coupling"
• "Bandwidth-Asymmetric Coupling"
• "Asymmetric Signal Coupling"
• "Unequal Bandwidth Coupling"
• "One-Sided Bandwidth Coupling"
• "Bandwidth Dominance Coupling"
• "Receiver Overload Coupling"
• "Sender-Dominant Coupling"
• "Bandwidth Imbalance"
• "Asymmetric Interface Coupling"

related:

laws:

• "Coupling Requires Bandwidth Symmetry or Compensation"
• "Signal Capacity Must Match Coupling Load"
• "Receiver Capacity Bounds Valid Coupling"
• "High-Bandwidth Nodes Must Not Overrun Low-Bandwidth Nodes"
• "Contestability Requires Bandwidth"
• "Consent Requires Sufficient Bandwidth"
• "Bandwidth Compression Creates Hidden Debt"
• "Coupling Without Compatibility"
• "Signal Misclassification"
• "Hidden Debt Accumulation"
• "Asymmetric Bandwidth"
• "U4 Truth Substitution"

invariants:

• "Coupled Nodes Must Preserve Send/Receive Viability"
• "Bandwidth Asymmetry Must Be Accounted"
• "Low-Bandwidth Nodes Require Protection"
• "Contest and Refusal Require Adequate Channel Capacity"
• "Compression Must Not Erase Meaning"
• "Response Load Must Fit Receiver Capacity"
• "Bandwidth Compensation Must Be Auditable"

operators:

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

gates:

• "Bandwidth Symmetry Gate"
• "Receiver Capacity Gate"
• "Signal Load Gate"
• "Contestability Gate"
• "Refusal Gate"
• "Compression Gate"
• "Interface Fit Gate"
• "Auditability Gate"
• "Local Coherence Gate"

diagnostics:

• "Send / Receive Capacity"
• "Bandwidth Asymmetry"
• "Signal Load"
• "Receiver Overload"
• "Compression Loss"
• "Contestability Capacity"
• "Refusal Capacity"
• "Interface Fit"
• "Hidden Debt"
• "Local Coherence"

failure_modes:

• "FM-ISC-002 — Signal Misclassification"
• "FM-ISC-003 — Urgency Substitution"
• "FM-ISC-005 — Coupling Without Compatibility"
• "FM-ISC-009 — Consent Drift"
• "FM-ISC-010 — Scope Creep"
• "FM-ECO-023 — Asymmetric Bandwidth"
• "FM-ECO-026 — Dependency Lock-In"
• "FM-R-004 — Repair Burden Externalization"
• "FM-R-007 — Repair Suppression via Efficiency"
• "FM-C-011 — Zero-Slack Collapse"
• "FM-CORE-002 — Hidden Debt Accumulation"
• "FM-AIX-015 — User Agency Compression"

restoration_arcs:

• "Bandwidth Symmetry Audit"
• "Receiver Capacity Restoration"
• "Signal Load Reduction"
• "Interface Throttling"
• "Compression Loss Repair"
• "Contestability Restoration"
• "Refusal Channel Restoration"
• "Bandwidth Compensation"
• "Hidden Bandwidth Debt Accounting"
• "Local Coherence Restoration"

modules:

• "Interactions / Signals / Couplings"
• "Interfaces"
• "Cybernetics"
• "AI Governance"
• "Justice"
• "Economy"
• "Restoration"
• "Diagnostics"
• "Coherence"

navigation:

order: 1506

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/interactions-signals-couplings/fm-isc-006-asymmetric-bandwidth-coupling.md"

notes: "Corrected ISC numbering after recalibration. This is the canonical FM-ISC-006 from the reference list. Distinct from FM-ECO-023 — Asymmetric Bandwidth as the general interaction/coupling form; FM-ECO-023 is the economy-specific expression."

entry:

failure_mode_id: "FM-ISC-006"

failure_family: "Interactions / Signals / Couplings"

production_treatment: "Standalone Entry"

domain_specific_expressions:

• "FM-ECO-023 — Asymmetric Bandwidth"

parent_modes:

• "FM-ISC-005 — Coupling Without Compatibility"
• "FM-ISC-002 — Signal Misclassification"
• "FM-C-011 — Zero-Slack Collapse"
• "FM-CORE-002 — Hidden Debt Accumulation"
• "FM-AIX-015 — User Agency Compression"

first_gate_failure: "Bandwidth Symmetry Gate"

primary_hidden_debt: "Hidden debt accumulates when one side of a coupling has greater ability to send, process, escalate, automate, repeat, contest, or enforce signals than the other side has to receive, answer, refuse, verify, repair, or absorb them."

primary_inversion: "Connection becomes fairness; the system treats the presence of a shared channel as sufficient equality even when bandwidth, response capacity, contestability, and repair access are asymmetric."

primary_boundary_pattern: "The boundary between access and capacity collapses; a node is treated as reachable, consenting, informed, or participating simply because a channel exists, even if its bandwidth is insufficient."

primary_signature: "Coupling occurs; one side sends or imposes more signal than the other can process; low-bandwidth node compresses, delays, misreads, complies, exits, or overloads; high-bandwidth node treats the interaction as valid; hidden debt accumulates."

FM-ISC-006 — Asymmetric Bandwidth Coupling

Status: Draft

Archive Type: Failure Mode

System: Universal Theory Stack

Parent: Failure Modes

Canon Tier: Registry

Registry: Failure Modes Registry

Entry ID: FM-ISC-006

Family: Interactions / Signals / Couplings

Production Treatment: Standalone Entry

Domain-Specific Expression: FM-ECO-023 — Asymmetric Bandwidth

Parent Modes: FM-ISC-005 — Coupling Without Compatibility; FM-ISC-002 — Signal Misclassification; FM-C-011 — Zero-Slack Collapse; FM-CORE-002 — Hidden Debt Accumulation; FM-AIX-015 — User Agency Compression

0. Interaction Scope Note

This entry is conceptual and systems-oriented.

It does not treat unequal bandwidth, specialization, hierarchy, delegation, expertise, automation, high-capacity systems, low-capacity states, asymmetric roles, or one-to-many communication as inherently failed.

Bandwidth asymmetry can be coherent.

Some systems require different sending, receiving, processing, or response capacities across roles.

Asymmetric bandwidth can preserve coherence when it is:

• acknowledged
• compensated
• consent-aware
• capacity-aware
• throttled when necessary
• auditable
• not coercive
• not used to erase refusal
• not used to overload weaker nodes
• paired with translation support
• paired with appeal or contestability
• paired with repair access
• designed around the lower-bandwidth node’s viability
• validated by affected-state outcomes

The failure begins when the coupling assumes symmetry that does not exist.

The issue is not unequal capacity.

The issue is coupling through a channel whose bandwidth is unequal enough to distort consent, signal, response, or repair.

Asymmetric Bandwidth Coupling occurs when one node can speak, send, demand, automate, interpret, enforce, or repeat faster than another can receive, process, answer, refuse, verify, or recover.

1. Definition

Asymmetric Bandwidth Coupling occurs when two or more nodes, systems, roles, interfaces, institutions, or relational fields are coupled while possessing unequal capacity to send, receive, process, contest, verify, refuse, repair, or absorb signals, causing one side to dominate the interaction bandwidth while the other carries compression, delay, overload, or hidden debt.

The asymmetry may involve:

• signal volume
• response speed
• legal capacity
• technical literacy
• emotional capacity
• administrative capacity
• attention capacity
• language capacity
• interface access
• appeal capacity
• documentation capacity
• automation capacity
• institutional authority
• memory capacity
• model inference capacity
• enforcement capacity
• data access
• visibility
• support access
• time availability
• cognitive load
• review capacity
• bandwidth for refusal
• bandwidth for clarification
• bandwidth for repair

The core failure is:

coupling active
bandwidth asymmetry unaccounted
low-bandwidth node overloads
signal / consent / repair degrade
H↑

Asymmetric Bandwidth Coupling is not merely unequal communication.

It is unequal communication treated as valid coupling.

2. Core Pattern

The core pattern is:

1. Two or more nodes become coupled.
2. One node has greater bandwidth to send, enforce, automate, repeat, escalate, interpret, or demand.
3. Another node has lower bandwidth to receive, understand, contest, answer, refuse, repair, or recover.
4. The system treats the shared channel as adequate.
5. The lower-bandwidth node compresses signals, misses details, delays response, gives shallow compliance, cannot contest, or absorbs overload.
6. The higher-bandwidth node reads compliance, silence, delay, or reduced signal as agreement, stability, or lack of issue.
7. Hidden debt accumulates in the lower-bandwidth node.
8. Restoration requires reducing asymmetry, compensating bandwidth, throttling flow, or decoupling.

This failure often appears as:

they had a chance to respond

while the hidden truth may be:

they did not have enough bandwidth to meaningfully respond

or:

the channel was open

while the overlooked condition is:

an open channel is not the same as a usable channel

The restorative question is:

who has enough bandwidth to shape the coupling, and who only has enough bandwidth to absorb it?

Asymmetric Bandwidth Coupling turns channel access into false participation.

3. Failure Signature

Typical signature:

coupling↑
send/receive asymmetry↑
contestability↓
receiver load↑
signal compression↑
H↑

Extended signature:

automated system sends faster than user can contest
institution demands documentation faster than affected node can gather
platform changes terms faster than users can understand
manager sends workload faster than worker can absorb
AI infers more than user can review
legal system produces process faster than harmed node can navigate
support system routes users through forms faster than humans can explain context

Common forms include:

a platform sends policy changes and treats continued use as informed consent
an AI system generates profile inferences faster than the user can inspect or correct
a workplace assigns tasks through many channels while worker response bandwidth is limited
a legal or benefits system requires documentation from people already overloaded
a company automates denials while users must manually appeal each case
a governance body requests community input through channels that require high time and literacy
a support system allows only short categories for complex harm
a relationship demands immediate response from someone with lower emotional or processing bandwidth

The defining condition is not that one node has more capacity.

The defining condition is that the coupling ignores the asymmetry and treats resulting outputs as valid.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: high-bandwidth nodes control channels, timing, and response standards.
• U2 — Configuration / Boundaries: interfaces are designed around sender capacity rather than receiver viability.
• U3 — Execution / Runtime: signal flow exceeds receiver processing capacity.
• U4 — Information / Truth: response, silence, or compliance is misread as true participation.
• U5 — Coordination / Time: deadlines, lag, and tempo mismatch overload lower-bandwidth nodes.
• U6 — Coherence Field: channel availability creates a fairness aura.
• U7 — Memory / Recurrence: repeated uncorrected asymmetry becomes normalized.
• U8 — Environment / Field: institutional, platform, legal, or market systems reward high-bandwidth actors.

Common manifestation layers:

• U1 — Power: high-bandwidth node sets terms.
• U2 — Boundaries: low-bandwidth node lacks sufficient response boundary.
• U3 — Execution: overload occurs.
• U4 — Truth: shallow signal is counted as consent or understanding.
• U5 — Time: response windows compress.
• U6 — Field: “they had access” becomes legitimacy.
• U7 — Memory: nonresponse becomes history.

Asymmetric Bandwidth Coupling is primarily a Φ flow / K load failure, anchored in BΣ boundary and Au auditability weakness.

The system sends more than the coupled node can coherently receive.

5. Typical Development Sequence

A common development sequence is:

1. Coupling is established.
2. A shared interface or channel exists.
3. The high-bandwidth node sends, demands, changes, escalates, or automates rapidly.
4. The lower-bandwidth node receives too much, too fast, too densely, or too ambiguously.
5. The lower-bandwidth node compresses response.
6. Compression is misread as agreement, non-issue, low priority, or stable participation.
7. More signal or obligation is routed through the same channel.
8. Overload deepens.
9. The lower-bandwidth node misses deadlines, gives incomplete consent, fails to contest, or exits.
10. The high-bandwidth node treats this as ordinary channel behavior.
11. Hidden debt accumulates.

The loop often looks like:

asymmetric channel → receiver overload → compressed response → sender confidence → more signal

Another common loop is:

low-bandwidth node misses contest window → decision becomes final → future bandwidth narrows further

Asymmetric Bandwidth Coupling becomes self-reinforcing when loss of response capacity is treated as evidence that no response was needed.

6. Diagnostic Markers

Diagnostic markers include:

• One side sends more signal than the other can process.
• The system equates channel access with meaningful participation.
• Response windows are too short for the affected node.
• Users, workers, communities, or affected nodes must compress complex state into narrow forms.
• Appeals, refusals, or corrections require more bandwidth than acceptance.
• Silence or delay is treated as agreement.
• Automated decisions outpace manual contestability.
• Low-bandwidth nodes repeatedly miss opportunities to object.
• The high-bandwidth node controls formatting, timing, and interpretation.
• The receiving node’s overload is treated as individual failure.
• Meaning is lost through compression.
• Restoration improves when signal flow is throttled, translated, or compensated.

Useful diagnostics:

• Send / Receive Capacity: Compares signal output and processing ability.
• Bandwidth Asymmetry: Measures channel power imbalance.
• Signal Load: Tracks volume, density, frequency, and complexity.
• Receiver Overload: Measures burden on the lower-bandwidth node.
• Compression Loss: Identifies meaning lost due to narrow channels.
• Contestability Capacity: Tests ability to challenge decisions.
• Refusal Capacity: Tests ability to say no or stop coupling.
• Interface Fit: Determines whether channel matches node capacity.
• Hidden Debt: Tracks burden from unaccounted asymmetry.
• Local Coherence: Tests whether coupling remains viable for all nodes.

7. Related Gates

Relevant gates include:

• Bandwidth Symmetry Gate: Fails when coupling assumes equal bandwidth without compensation.
• Receiver Capacity Gate: Fails when signal load exceeds receiver capacity.
• Signal Load Gate: Fails when volume, speed, or complexity overwhelms the channel.
• Contestability Gate: Fails when affected nodes cannot meaningfully challenge.
• Refusal Gate: Fails when saying no requires more bandwidth than saying yes.
• Compression Gate: Fails when interface constraints erase meaning.
• Interface Fit Gate: Fails when channel design mismatches user or node capacity.
• Auditability Gate: Fails when asymmetry cannot be measured.
• Local Coherence Gate: Fails when lower-bandwidth nodes degrade.

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

The system assumes meaningful coupling because a channel exists.

8. Related Operators

Relevant operators include:

• Φ — Flow / Resource Movement: Primary operator; signal, obligation, data, and demand flow through the coupling.
• K — Constraint / Load: Rises in the lower-bandwidth node.
• BΣ — Boundary Integrity: Preserves limits on what can be sent, demanded, or inferred.
• Ψ — Observation / Interface: Determines what channel exists and what it can carry.
• Λ — Compatibility: Tests whether bandwidth fit supports coupling.
• Au — Auditability: Reveals asymmetry, overload, and compression loss.
• O — Coherence: May appear high because the channel functions technically.
• H — Hidden Debt: Accumulates through unprocessed signal and invalid consent.
• Γ — Selection: Selects response pathways based on compressed output.
• D — Damping: Should throttle flow and prevent overload.
• R — Restoration Capacity: Repairs overload, misclassification, and invalid coupling.
• G — Gain: Incentivizes high-volume senders or automated enforcement.
• Τ — Trajectory / Time: Tracks tempo mismatch and compounding overload.

Common operator pattern:

coupling established
Φ signal flow increases
Ψ channel appears open
BΣ receiver boundary weakens
K rises in receiver
D fails to throttle
Γ treats compressed response as valid
Au misses asymmetry
H accumulates

The core operator inversion is:

channel open → participation valid

instead of:

channel open + receiver bandwidth sufficient + contestability available + compression loss low → participation valid

Asymmetric Bandwidth Coupling turns reachability into consent-like validity.

9. Related Laws and Invariants

Related Laws

• Coupling Requires Bandwidth Symmetry or Compensation: unequal bandwidth requires design correction.
• Signal Capacity Must Match Coupling Load: channels must fit the load they carry.
• Receiver Capacity Bounds Valid Coupling: the lower-capacity node constrains safe flow.
• High-Bandwidth Nodes Must Not Overrun Low-Bandwidth Nodes: capacity advantage cannot define validity.
• Contestability Requires Bandwidth: challenge must be practically possible.
• Consent Requires Sufficient Bandwidth: meaningful agreement requires processing and refusal capacity.
• Bandwidth Compression Creates Hidden Debt: lost meaning becomes future burden.
• Coupling Without Compatibility: bandwidth mismatch is a compatibility failure.
• Signal Misclassification: compressed responses are easily misread.
• Hidden Debt Accumulation: unprocessed signal creates debt.
• Asymmetric Bandwidth: economy-specific bandwidth asymmetry applies as domain expression.
• U4 Truth Substitution: channel output replaces state truth.

Related Invariants

• Coupled Nodes Must Preserve Send/Receive Viability: both sides must remain capable of meaningful interaction.
• Bandwidth Asymmetry Must Be Accounted: unequal capacity cannot be hidden.
• Low-Bandwidth Nodes Require Protection: coupling must be designed around lower capacity.
• Contest and Refusal Require Adequate Channel Capacity: no and challenge need real bandwidth.
• Compression Must Not Erase Meaning: narrow channels cannot be treated as full truth.
• Response Load Must Fit Receiver Capacity: requests must respect processing load.
• Bandwidth Compensation Must Be Auditable: supports and throttles must be inspectable.

10. Common False Positives

Not every asymmetric channel is Asymmetric Bandwidth Coupling.

Common false positives include:

• One-to-many broadcast with no consent or response implication.
• High-bandwidth sender with strong receiver-side filters.
• Asymmetric expertise relationship with clear support.
• Automated system with easy human review.
• Narrow form used only for narrow purpose.
• Low-bandwidth participation with translation, time, and assistance.
• Legal or administrative process with advocates and source-carried burden.
• High-volume system with throttling and digest controls.
• Consent flow with sufficient explanation, time, revocation, and contestability.
• Emergency communication followed by accessible review.
• AI inference system with inspection, correction, and revocation.
• Delegated communication where representative bandwidth is validly authorized.

Clarifying rule:

This is not Asymmetric Bandwidth Coupling unless unequal send, receive, process, contest, verify, refuse, repair, or absorb capacity is ignored while the system treats the coupling’s outputs as valid participation, consent, understanding, repair, or response.

11. Common False Repairs

Common false repairs include:

• adding more notifications
• making forms longer
• creating dashboards for receiver-side overload
• offering help pages instead of reducing signal load
• adding faster automation to a one-sided process
• increasing response deadlines slightly without reducing complexity
• treating unread messages as user fault
• providing appeal channels that require excessive bandwidth
• compressing complex signals into more categories
• asking low-bandwidth nodes to attend more meetings
• adding AI summaries that hide source complexity
• creating self-service repair for source-caused overload
• measuring response rate instead of comprehension
• treating nonresponse as valid because notice was sent
• giving the high-bandwidth node better tooling only

False repair often produces the loop:

bandwidth asymmetry exposed → more communication added → receiver overload deepens

Another common loop is:

low-bandwidth node misses signal → system sends more reminders → overload worsens → more signals missed

The repair fails because it increases signal volume instead of restoring bandwidth fit.

12. Restoration Direction

Restoration requires measuring bandwidth asymmetry, reducing signal load, increasing receiver-side capacity, restoring contestability and refusal channels, throttling high-bandwidth senders, and repairing hidden debt created by compression and overload.

Primary restoration direction:

audit bandwidth asymmetry,
throttle signal load,
restore receiver capacity,
and repair compression debt

A fuller restoration path includes:

1. Name the coupling. Identify the nodes, interface, process, relationship, institution, or system connection.
2. Map bandwidth directions. Identify who sends, receives, processes, contests, verifies, refuses, and repairs.
3. Measure asymmetry. Compare signal volume, complexity, timing, response windows, and support.
4. Identify receiver overload. Determine what burden is carried by lower-bandwidth nodes.
5. Measure compression loss. Identify what meaning is lost through narrow channels.
6. Reduce signal load. Lower volume, frequency, density, and unnecessary complexity.
7. Throttle high-bandwidth actors. Limit automated or high-volume signaling when receivers cannot process it.
8. Increase receiver support. Add time, translation, human assistance, summaries with source trace, accessibility, and advocacy.
9. Restore contestability. Ensure appeals, challenges, and corrections are usable.
10. Restore refusal capacity. Make no, opt-out, withdrawal, and pause easier than compliance.
11. Repair misread outputs. Revisit decisions made from compressed or overloaded responses.
12. Account hidden bandwidth debt. Identify missed signals, invalid consent, overload, and delayed repair.
13. Validate local coherence. Confirm low-bandwidth nodes can actually participate.
14. Install bandwidth gates. Require receiver-capacity checks before coupling or escalation.
15. Monitor drift. Recheck bandwidth as systems automate, scale, or increase signal volume.

A valid restoration path should reduce:

receiver overload
compression loss
invalid participation
missed contestation
false consent
signal burden
bandwidth debt
H

Asymmetric Bandwidth Coupling is not repaired by giving the weaker node more things to process.

It is repaired by making the coupling fit the bandwidth of all coupled nodes.

13. Cross-Module Links

• Interactions / Signals / Couplings: Core ISC failure where coupling overloads one side’s signal capacity.
• Interfaces: Forms, dashboards, notifications, appeals, consent flows, and support channels determine practical bandwidth.
• Cybernetics: Feedback and correction fail when one side cannot process or return signal.
• AI Governance: AI systems can infer, decide, message, personalize, enforce, or refuse faster than users can inspect, contest, or correct.
• Justice: Legal, administrative, and institutional pathways often overload harmed or lower-power nodes.
• Economy: FM-ECO-023 expresses bandwidth asymmetry in economic systems, contracts, support, and market participation.
• Restoration: Repair requires reducing signal burden and restoring receiver capacity.
• Diagnostics: Requires bandwidth-asymmetry, receiver-overload, compression-loss, and contestability diagnostics.
• Coherence: Coherent coupling requires each node to have enough bandwidth to participate without hidden overload.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry

This mode maps upward to:

• FM-ISC-005 — Coupling Without Compatibility
• FM-ISC-002 — Signal Misclassification
• FM-C-011 — Zero-Slack Collapse
• FM-CORE-002 — Hidden Debt Accumulation
• FM-AIX-015 — User Agency Compression

Domain-specific expression:

• FM-ECO-023 — Asymmetric Bandwidth

Sibling or related ISC modes include:

• FM-ISC-001 — Identity-Binding Signal Capture
• FM-ISC-002 — Signal Misclassification
• FM-ISC-003 — Urgency Substitution
• FM-ISC-004 — Echo Loop Amplification
• FM-ISC-005 — Coupling Without Compatibility
• FM-ISC-007 — Premature Irreversible Coupling
• FM-ISC-008 — Coupling Under False Coherence
• FM-ISC-009 — Consent Drift
• FM-ISC-017 — Bandwidth Illusion

Related cross-family modes include:

• FM-ECO-023 — Asymmetric Bandwidth
• FM-ECO-026 — Dependency Lock-In
• FM-R-004 — Repair Burden Externalization
• FM-R-007 — Repair Suppression via Efficiency
• FM-C-011 — Zero-Slack Collapse
• FM-C-013 — Capacity Collapse / Control Impossibility
• FM-C-020 — Measurement Back-Action Loop
• FM-JC-004 — Under-Resourced Justice
• FM-JC-012 — Silence Misread as Stability
• FM-AIX-015 — User Agency Compression
• FM-AIX-018 — Civilizational Deskilling
• FM-CORE-002 — Hidden Debt Accumulation

Aliases preserved from source material:

• Asymmetric Bandwidth Coupling
• Bandwidth-Asymmetric Coupling
• Asymmetric Signal Coupling
• Unequal Bandwidth Coupling
• One-Sided Bandwidth Coupling
• Bandwidth Dominance Coupling
• Receiver Overload Coupling
• Sender-Dominant Coupling
• Bandwidth Imbalance
• Asymmetric Interface Coupling

15. Minimal Entry Version

Definition: Asymmetric Bandwidth Coupling occurs when two or more nodes, systems, roles, interfaces, institutions, or relational fields are coupled while possessing unequal capacity to send, receive, process, contest, verify, refuse, repair, or absorb signals, causing one side to dominate the interaction bandwidth while the other carries compression, delay, overload, or hidden debt.

Signature:

coupling↑
send/receive asymmetry↑
contestability↓
receiver load↑
signal compression↑
H↑

Restoration direction:

• name the coupling
• map bandwidth directions
• measure asymmetry
• identify receiver overload
• measure compression loss
• reduce signal load
• throttle high-bandwidth actors
• increase receiver support
• restore contestability
• restore refusal capacity
• repair misread outputs
• account hidden bandwidth debt
• validate local coherence
• install bandwidth gates
• monitor drift

16. Machine-Readable Summary

failure_mode:
  id: "FM-ISC-006"
  name: "Asymmetric Bandwidth Coupling"
  family: "Interactions / Signals / Couplings"
  production_treatment: "Standalone Entry"
  domain_specific_expressions:
    - "FM-ECO-023 — Asymmetric Bandwidth"
  parent_modes:
    - "FM-ISC-005 — Coupling Without Compatibility"
    - "FM-ISC-002 — Signal Misclassification"
    - "FM-C-011 — Zero-Slack Collapse"
    - "FM-CORE-002 — Hidden Debt Accumulation"
    - "FM-AIX-015 — User Agency Compression"
  primary_failure: "Unequal send, receive, process, contest, verify, refuse, repair, or absorb capacity is ignored while the system treats the coupling’s outputs as valid participation, consent, understanding, repair, or response."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ISC-006"
  scope_note: "Conceptual and systems-oriented; does not treat unequal bandwidth, specialization, hierarchy, delegation, expertise, automation, high-capacity systems, low-capacity states, asymmetric roles, or one-to-many communication as inherently failed."
  aliases:
    - "Asymmetric Bandwidth Coupling"
    - "Bandwidth-Asymmetric Coupling"
    - "Asymmetric Signal Coupling"
    - "Unequal Bandwidth Coupling"
    - "One-Sided Bandwidth Coupling"
    - "Bandwidth Dominance Coupling"
    - "Receiver Overload Coupling"
    - "Sender-Dominant Coupling"
    - "Bandwidth Imbalance"
    - "Asymmetric Interface Coupling"
  signature:
    - "coupling↑"
    - "send/receive asymmetry↑"
    - "contestability↓"
    - "receiver load↑"
    - "signal compression↑"
    - "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"
      - "U7 — Memory"
  state_variables:
    - "Φ"
    - "K"
    - "BΣ"
    - "Ψ"
    - "Λ"
    - "Au"
    - "O"
    - "H"
    - "Γ"
    - "D"
    - "R"
    - "G"
    - "Τ"
  first_gate_failure: "Bandwidth Symmetry Gate"
  restoration:
    - "Bandwidth Symmetry Audit"
    - "Receiver Capacity Restoration"
    - "Signal Load Reduction"
    - "Interface Throttling"
    - "Compression Loss Repair"
    - "Contestability Restoration"
    - "Refusal Channel Restoration"
    - "Bandwidth Compensation"
    - "Hidden Bandwidth Debt Accounting"
    - "Local Coherence Restoration"