Task-domain path index
Browse 19 represented intermediate stages that carry usb data-domain evidence in the current topology library. The page does not claim that every stage can be combined with every other stage.
I006 · cable · record-class
USB-C → USB-C
requirements only: A power label alone does not establish that a cable is data-free; an actual product needs explicit no-data documentation before using this classification.
I007 · cable · record-class
USB-C → USB-C
requirements only: Data capability must be established from the exact cable's documented data mode or recognized marking.
I014 · cable · exact-product
USB-C → USB-C
documented: The represented product reference lists USB 2 data capability; it is not represented here as a high-speed-data or display cable.
I015 · cable · exact-product
USB-C → USB-C
documented: The represented product reference lists USB 2 data capability; its higher charging rating does not imply faster data.
I016 · cable · exact-product
USB-C → USB-C
documented: The represented product reference lists USB 3.2 Gen 2 data up to 10 Gbps.
I017 · cable · exact-product
USB-C → USB-C
documented: The represented product reference lists USB 2.0 data up to 480 Mbps.
I018 · cable · exact-product
USB-C → USB-C
documented: The represented product reference lists USB 2.0 data up to 480 Mbps.
I020 · dock · exact-product
USB-C → USB-C
documented: The exact TS4 evidence distinguishes its Thunderbolt host connection from documented downstream USB-C interfaces.
Modeled role: relay
I023 · dock · exact-product
USB-C → HDMI Type-A
partial: The exact product uses an upstream USB-C data path, but topology does not establish negotiated USB rate or driver availability.
Modeled role: relay
I024 · dock · exact-product
USB-C → HDMI Type-A
partial: The exact upstream USB-C connection is represented, but negotiated USB/DP transport and host support are not solved here.
Modeled role: relay
I026 · adapter · exact-product
USB Type-A → 8P8C modular Ethernet
documented: The exact UE300 source represents a USB 3.0 host interface feeding the adapter.
Modeled role: relay
I027 · reader · exact-product
CFexpress Type A → USB-C
partial: The reader has a documented USB-C computer connection, but cable capability and negotiated USB mode are not established by the media profile alone.
Modeled role: relay
I028 · reader · exact-product
Full-size SD card → USB-C
partial: The reader has a documented USB-C computer connection, while negotiated USB mode and cable capability remain unresolved.
Modeled role: relay
I029 · reader · exact-product
CFexpress Type B → USB-C
partial: The exact reader has a documented USB-C computer connection, but negotiated host/cable behavior is not solved here.
Modeled role: relay
I030 · reader · exact-product
Full-size SD card → USB-C
partial: The exact reader has a documented USB-C computer connection, but negotiated host/cable behavior is not solved here.
Modeled role: relay
I031 · reader · exact-product
CFexpress Type B → USB-C
partial: The product has an integrated USB-C cable and a secondary USB-C port as alternative upstream arrangements.
Modeled role: relay
I032 · reader · exact-product
Full-size SD card → USB-C
partial: The product has an integrated USB-C cable and a secondary USB-C port as alternative upstream arrangements.
Modeled role: relay
I033 · reader · exact-product
Full-size SD card → USB-C
partial: The dock host connection is USB-C-shaped Thunderbolt; topology does not reduce that transport to a generic USB mode.
Modeled role: relay
I034 · reader · exact-product
microSD card → USB-C
partial: The dock host connection is USB-C-shaped Thunderbolt; topology does not reduce that transport to a generic USB mode.
Modeled role: relay
These discovery surfaces route and reorganize facts already represented in the atlas. They do not add electrical ratings, universal pinouts, measured tolerances, exact-device support, wiring approval or an end-to-end compatibility result.
