Home / Start Start with the task
What needs to connect? Choose the task to find an existing worksheet. Nothing is saved or filled in for you.
Jump to Choose a task Decision examples Other paths Browse instead
All eight primary starts Every route remains usable without the guided router. 01 Connector discovery
Identify a connector Start from the physical form, markings and family. Keep unknown contact counts and function separate.
Boundary: Physical identification is not proof of electrical function, protocol support, device compatibility or safety.
Start this task → 02 Display connection brief
Connect one display Choose the documented source and display endpoints, then investigate one directed connection class.
Boundary: The brief does not promise resolution, refresh rate, HDR, VRR, adapter behavior or a complete system result.
Start this task → 03 USB data brief
Connect a USB device Document one host-to-peripheral data path for storage, webcams, interfaces or serial devices.
Boundary: The brief does not infer negotiated speed, charging behavior, hub behavior or electrical safety from connector shape.
Start this task → 04 Card-reader worksheet
Read a memory card Check the exact card family, reader support and optional camera slot before the USB handoff.
Boundary: The worksheet does not approve recording modes, media health or measured transfer performance.
Start this task → 05 Network connection desk
Build a wired network Keep Ethernet link roles, PoE classes, injectors and observed switch modes explicit.
Boundary: The desk does not certify cabling, predict throughput or infer a powered device’s real demand.
Start this task → 06 Audio connection desk
Connect audio gear Start with signal role, channel layout and exact endpoints instead of matching plug shapes.
Boundary: The desk does not invent wiring conversions, set gain or automatically authorize phantom power.
Start this task → 07 Multi-display desk
Run multiple displays Model the host, dock and monitor paths with native limits, software paths and operating conditions separate.
Boundary: The desk does not combine maxima from incompatible configurations or declare a dock universally compatible.
Start this task → 08 Charging and power desk
Charge or power a device Separate source allocation, exact load evidence, cable limits and output-profile documentation.
Boundary: The desk does not perform live USB-PD negotiation, measure demand or issue a universal charger recommendation.
Start this task → Common connection questions
The next useful question, not a guessed answer. Sixteen illustrative tasks show how to separate a form, a role and a documented capability. These are not diagnoses or hardware tests. Opening a desk does not select equipment or fill in evidence.
More ways in Guided start / optional
Find my starting desk Choose only what you know. No model names, notes or private text are requested.
No save · no device access Nothing selected. Your answers are not saved. An optional handoff carries only one fixed categorical task token.
The guided router needs JavaScript, but every destination remains available in the complete route list below.
Choose the strongest fact you already have
Task, connector or exact model. How a starting point is chosen
Practical connection decisions · static & source-linked
Follow the whole connection, not just the shape. Pick the closest documented situation below. Each illustrated stage and stop condition comes from the existing native decision reader, not a new compatibility solver. These are 29 synthetic documentation exercises (16 authenticated originals plus 13 new, different selections), never real equipment approvals or model-specific recommendations.
29 documented cases9 stops / rejected inputs18 need evidence0 hardware approvals
One display Direction, video transport and converter class 12 scenarios ↓ USB data Host, peripheral, data cable and software 6 scenarios ↓ Docks and multiple displays Native resources, upstream cable and software paths 5 scenarios ↓ Charging and power Port allocations, output profiles and actual cable 6 scenarios ↓ How to read the flow: source → physical cable / converter / dock when modeled → destination. Missing intermediate evidence is shown as missing, not filled in. “Documented class only” is not “works.” A rejected choice has no synthesized path. Every case has its own native worksheet and exact source-register links.
Evidence needed Case 01 / V159 retained
USB-C charges, but the screen stays blank Charging observed on a port does not document a working video path.
The native reader lacks one or more facts required for this described task.
01 Source / output USB-C source (unverified) form only Verify the actual output role and complete target mode on this exact port.
02 Cable / converter USB-C → HDMI converter class only Check both ends, documented direction, target and any product-specific auxiliary power.
S014 · S519 03 Destination / input HDMI display input (unverified) form only Verify the selected input accepts the requested mode and transport.
Check first Check which video transport the exact source port and destination document; charging or connector shape alone does not answer this.
Read evidence and missing conditions ↗
Still missing · 8 Check which video transport the exact source port and destination document; charging or connector shape alone does not answer this. Source / output: identify the exact device and verify its role; only a form is selected. Destination / input: identify the exact device and verify its role; only a form is selected. Identify the actual devices and verify their output/input roles; the current shape-only choice is not evidence. Does the exact source output the full target mode on this physical port? Does the selected display input accept that mode, protocol and direction? Does the actual cable or converter document both ends and the complete target? Have host/OS requirements, length, color format, compression and any supplied converter power been checked? Review limits · 4 A documentation brief, not a recommendation to buy or connect hardware. No performance, compatibility or electrical approval is produced. Only a single source, one investigated cable/converter class and a single display input are represented. Docks, KVMs, branches, charging and simultaneous displays require a separate analysis. Profile assertions come from manufacturer pages; no independent human approval or hardware test is implied. Source dates are retained, not refreshed by opening this brief. A missing connection class is a scope boundary. Matching forms do not establish contacts, negotiated protocol or capability. Existing exact claim excerpts DisplayPort Alternate Mode can carry video from a supported USB-C source to an HDMI display through a suitable converter. C041A · S014
VESA describes USB-C to HDMI accessories as DisplayPort Alt Mode protocol converters, with the USB-C end attached to the video source. C041B · S519
Native source register: S003 · S012 · S014 · S015 · S018 · S036 · S062 · S064 · S365 · S446 · S447 · S448 · S449 · S450 · S451 · S452 · S453 · S511 · S518 · S519 · S605 · S606 · S643 · S972 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (2) — not measurements Requested target: Investigate a 3840 × 2160 at 60 Hz display task; color format, HDR and actual equipment still need documentation. Source → destination is the selected signal direction, not an instruction to reverse an adapter. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable display desk ↗
Evidence needed Case 02 / V159 retained
Known source and display, unknown actual cable Documented endpoint roles do not identify or approve the cable between them.
The native reader lacks one or more facts required for this described task.
01 Source / output MacBook Air (13-inch, M4, 2025) / Thunderbolt 4 / USB-C scoped profile Verify the actual output role and complete target mode on this exact port.
S065 02 Cable / converter USB-C → HDMI converter class only Check both ends, documented direction, target and any product-specific auxiliary power.
S014 · S519 03 Destination / input Dell UltraSharp U2723QE / HDMI input scoped profile Verify the selected input accepts the requested mode and transport.
S061 Check first Check which video transport the exact source port and destination document; charging or connector shape alone does not answer this.
Read evidence and missing conditions ↗
Still missing · 5 Check which video transport the exact source port and destination document; charging or connector shape alone does not answer this. Does the exact source output the full target mode on this physical port? Does the selected display input accept that mode, protocol and direction? Does the actual cable or converter document both ends and the complete target? Have host/OS requirements, length, color format, compression and any supplied converter power been checked? Review limits · 4 A documentation brief, not a recommendation to buy or connect hardware. No performance, compatibility or electrical approval is produced. Only a single source, one investigated cable/converter class and a single display input are represented. Docks, KVMs, branches, charging and simultaneous displays require a separate analysis. Profile assertions come from manufacturer pages; no independent human approval or hardware test is implied. Source dates are retained, not refreshed by opening this brief. A missing connection class is a scope boundary. Matching forms do not establish contacts, negotiated protocol or capability. Existing exact claim excerpts DisplayPort Alternate Mode can carry video from a supported USB-C source to an HDMI display through a suitable converter. C041A · S014
VESA describes USB-C to HDMI accessories as DisplayPort Alt Mode protocol converters, with the USB-C end attached to the video source. C041B · S519
Native source register: S003 · S012 · S014 · S015 · S018 · S036 · S061 · S062 · S064 · S065 · S365 · S446 · S447 · S448 · S449 · S450 · S451 · S452 · S453 · S511 · S518 · S519 · S605 · S606 · S643 · S972 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (2) — not measurements Requested target: Investigate a 3840 × 2160 at 60 Hz display task; color format, HDR and actual equipment still need documentation. Source → destination is the selected signal direction, not an instruction to reverse an adapter. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable display desk ↗
Evidence needed Case 03 / V159 retained
A passive DisplayPort-to-HDMI adapter A DisplayPort outline alone does not establish dual-mode support.
The native reader lacks one or more facts required for this described task.
01 Source / output DisplayPort source (unverified) form only Verify the actual output role and complete target mode on this exact port.
02 Cable / converter DisplayPort → HDMI passive adapter class only Check both ends, documented direction, target and any product-specific auxiliary power.
S846 · S634 · S644 03 Destination / input HDMI display input (unverified) form only Verify the selected input accepts the requested mode and transport.
Check first Check the exact source documentation for DP++ support before investigating this passive class.
Read evidence and missing conditions ↗
Still missing · 9 Check the exact source documentation for DP++ support before investigating this passive class. Source / output: identify the exact device and verify its role; only a form is selected. Destination / input: identify the exact device and verify its role; only a form is selected. Identify the actual devices and verify their output/input roles; the current shape-only choice is not evidence. Does the exact source output the full target mode on this physical port? Does the selected display input accept that mode, protocol and direction? Does the actual cable or converter document both ends and the complete target? Have host/OS requirements, length, color format, compression and any supplied converter power been checked? +1 more in the native worksheet
Review limits · 4 A documentation brief, not a recommendation to buy or connect hardware. No performance, compatibility or electrical approval is produced. Only a single source, one investigated cable/converter class and a single display input are represented. Docks, KVMs, branches, charging and simultaneous displays require a separate analysis. Profile assertions come from manufacturer pages; no independent human approval or hardware test is implied. Source dates are retained, not refreshed by opening this brief. A missing connection class is a scope boundary. Matching forms do not establish contacts, negotiated protocol or capability. Existing exact claim excerpts The cited passive DisplayPort-to-HDMI adapter class requires a DisplayPort dual-mode (DP++) source; the DP2HDMI2 manufacturer document states that requirement. C044A · S846
DP2HD4KADAP is listed as passive, with a DisplayPort input and HDMI output; its source must support DP++ HDMI/DVI pass-through. C044B · S634
The passive DP2HD4KADAP sheet lists 3840 x 2160 at 30 Hz and no HDR support. C044C · S634
VESA limits passive DisplayPort to HDMI or DVI adapter operation to DisplayPort source devices with DP++ capability; equipment documentation must establish that feature. C044D · S644
Native source register: S012 · S014 · S015 · S018 · S036 · S365 · S368 · S450 · S451 · S452 · S453 · S518 · S520 · S606 · S634 · S644 · S846 · S976 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (2) — not measurements Requested target: Investigate a 3840 × 2160 at 60 Hz display task; color format, HDR and actual equipment still need documentation. Source → destination is the selected signal direction, not an instruction to reverse an adapter. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable display desk ↗
Evidence needed Case 04 / V159 retained
HDMI source, DisplayPort display A DP-to-HDMI product is not automatically a reverse-direction converter.
The native reader lacks one or more facts required for this described task.
01 Source / output HDMI source (unverified) form only Verify the actual output role and complete target mode on this exact port.
02 Cable / converter HDMI → DisplayPort active converter class only Check both ends, documented direction, target and any product-specific auxiliary power.
S036 · S645 03 Destination / input DisplayPort display input (unverified) form only Verify the selected input accepts the requested mode and transport.
Check first Check that the converter explicitly runs from the HDMI source to the DisplayPort display, including its own power instructions.
Read evidence and missing conditions ↗
Still missing · 8 Check that the converter explicitly runs from the HDMI source to the DisplayPort display, including its own power instructions. Source / output: identify the exact device and verify its role; only a form is selected. Destination / input: identify the exact device and verify its role; only a form is selected. Identify the actual devices and verify their output/input roles; the current shape-only choice is not evidence. Does the exact source output the full target mode on this physical port? Does the selected display input accept that mode, protocol and direction? Does the actual cable or converter document both ends and the complete target? Have host/OS requirements, length, color format, compression and any supplied converter power been checked? Review limits · 4 A documentation brief, not a recommendation to buy or connect hardware. No performance, compatibility or electrical approval is produced. Only a single source, one investigated cable/converter class and a single display input are represented. Docks, KVMs, branches, charging and simultaneous displays require a separate analysis. Profile assertions come from manufacturer pages; no independent human approval or hardware test is implied. Source dates are retained, not refreshed by opening this brief. A missing connection class is a scope boundary. Matching forms do not establish contacts, negotiated protocol or capability. Existing exact claim excerpts An HDMI-source to DisplayPort-display path needs a converter designed for that direction; example products use active conversion and auxiliary USB power. C045A · S036
128-HDMI-DISPLAYPORT is explicitly one-way from an HDMI source to a DisplayPort display. Its attached USB-A lead is described for power, and the power table specifies 5 V DC. C045B · S036
128-HDMI-DISPLAYPORT lists 3840 x 2160 at 60 Hz; its notes require both source and display to support that resolution and refresh rate. C045C · S036
Plugable distinguishes one-way DisplayPort-source to HDMI-display cables from active HDMI-source to DisplayPort-display converters; a typical DP-to-HDMI cable is not a reversible HDMI-to-DP solution. C045D · S645
Native source register: S012 · S014 · S015 · S018 · S036 · S365 · S368 · S450 · S451 · S452 · S453 · S518 · S520 · S606 · S644 · S645 · S976 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (2) — not measurements Requested target: Investigate a 3840 × 2160 at 60 Hz display task; color format, HDR and actual equipment still need documentation. Source → destination is the selected signal direction, not an instruction to reverse an adapter. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable display desk ↗
Selection rejected Case 05 / V159 retained
The right-looking ends, the wrong selected direction An invalid class selection is rejected, not silently reversed or replaced.
The native validator rejected this ordered selection. No path or hardware verdict was generated.
Path withheld by the native validator. No fabricated source, adapter or destination chain is displayed for an invalid selection.
Check first The selected class does not describe this directed one-step pair. Choose a new class after changing either end.
Read evidence and missing conditions ↗
Still missing · 0 No unchecked category in this narrow projection. This is not working-connection approval.
Review limits · 0 All original source and physical-check limits remain.
Native source register: No scoped source is attached to this rejected input. Original inspection dates and limitations remain in each record.
Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable display desk ↗
Evidence needed Case 06 / V159 retained
No one-step class appears Missing catalogue coverage does not prove that a connection is impossible.
The native reader lacks one or more facts required for this described task.
01 Source / output HDMI source (unverified) form only Verify the actual output role and complete target mode on this exact port.
02 Cable / converter No class selected class only Check both ends, documented direction, target and any product-specific auxiliary power.
03 Destination / input USB-C display input (unverified) form only Verify the selected input accepts the requested mode and transport.
Check first Source / output: identify the exact device and verify its role; only a form is selected.
Read evidence and missing conditions ↗
Still missing · 9 Source / output: identify the exact device and verify its role; only a form is selected. Destination / input: identify the exact device and verify its role; only a form is selected. No one-step class is represented for this pair. Use an exact-product multistage plan; absence here is not proof of impossibility. This pair has no one-step class here. That is a coverage limit, not proof the devices cannot connect. Use a product-specific multi-stage plan. Identify the actual devices and verify their output/input roles; the current shape-only choice is not evidence. Does the exact source output the full target mode on this physical port? Does the selected display input accept that mode, protocol and direction? Does the actual cable or converter document both ends and the complete target? +1 more in the native worksheet
Review limits · 4 A documentation brief, not a recommendation to buy or connect hardware. No performance, compatibility or electrical approval is produced. Only a single source, one investigated cable/converter class and a single display input are represented. Docks, KVMs, branches, charging and simultaneous displays require a separate analysis. Profile assertions come from manufacturer pages; no independent human approval or hardware test is implied. Source dates are retained, not refreshed by opening this brief. A missing connection class is a scope boundary. Matching forms do not establish contacts, negotiated protocol or capability. Native source register: S003 · S012 · S014 · S015 · S018 · S036 · S062 · S064 · S365 · S446 · S447 · S448 · S449 · S450 · S451 · S452 · S453 · S511 · S518 · S605 · S606 · S643 · S972 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (2) — not measurements Requested target: Investigate a 3840 × 2160 at 60 Hz display task; color format, HDR and actual equipment still need documentation. Source → destination is the selected signal direction, not an instruction to reverse an adapter. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable display desk ↗
Evidence needed Case 17 / V172 addition
USB-C source to a DisplayPort input A connector marked USB-C still needs exact video-mode evidence.
The native reader lacks one or more facts required for this described task.
01 Source / output USB-C source (unverified) form only Verify the actual output role and complete target mode on this exact port.
02 Cable / converter USB-C → DisplayPort cable class only Check both ends, documented direction, target and any product-specific auxiliary power.
S037 · S519 03 Destination / input DisplayPort display input (unverified) form only Verify the selected input accepts the requested mode and transport.
Check first Check which video transport the exact source port and destination document; charging or connector shape alone does not answer this.
Read evidence and missing conditions ↗
Still missing · 8 Check which video transport the exact source port and destination document; charging or connector shape alone does not answer this. Source / output: identify the exact device and verify its role; only a form is selected. Destination / input: identify the exact device and verify its role; only a form is selected. Identify the actual devices and verify their output/input roles; the current shape-only choice is not evidence. Does the exact source output the full target mode on this physical port? Does the selected display input accept that mode, protocol and direction? Does the actual cable or converter document both ends and the complete target? Have host/OS requirements, length, color format, compression and any supplied converter power been checked? Review limits · 4 A documentation brief, not a recommendation to buy or connect hardware. No performance, compatibility or electrical approval is produced. Only a single source, one investigated cable/converter class and a single display input are represented. Docks, KVMs, branches, charging and simultaneous displays require a separate analysis. Profile assertions come from manufacturer pages; no independent human approval or hardware test is implied. Source dates are retained, not refreshed by opening this brief. A missing connection class is a scope boundary. Matching forms do not establish contacts, negotiated protocol or capability. Existing exact claim excerpts USB-C to DisplayPort video requires supported DisplayPort transport; some specifically documented cables also support the reverse direction. C042A · S037
VESA states that an Alt Mode display receives no image when connected to a USB-C port that does not support DisplayPort over USB-C. C042B · S519
Native source register: S003 · S014 · S015 · S036 · S037 · S062 · S064 · S368 · S446 · S447 · S448 · S449 · S450 · S451 · S452 · S453 · S511 · S519 · S520 · S605 · S643 · S644 · S972 · S976 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (2) — not measurements Requested target: Investigate a 3840 × 2160 at 60 Hz display task; color format, HDR and actual equipment still need documentation. Source → destination is the selected signal direction, not an instruction to reverse an adapter. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable display desk ↗
Evidence needed Case 18 / V172 addition
DisplayPort to HDMI, investigating an active class An active conversion class is not interchangeable with a passive dual-mode path.
The native reader lacks one or more facts required for this described task.
01 Source / output DisplayPort source (unverified) form only Verify the actual output role and complete target mode on this exact port.
02 Cable / converter DisplayPort → HDMI active converter class only Check both ends, documented direction, target and any product-specific auxiliary power.
S035 03 Destination / input HDMI display input (unverified) form only Verify the selected input accepts the requested mode and transport.
Check first Source / output: identify the exact device and verify its role; only a form is selected.
Read evidence and missing conditions ↗
Still missing · 7 Source / output: identify the exact device and verify its role; only a form is selected. Destination / input: identify the exact device and verify its role; only a form is selected. Identify the actual devices and verify their output/input roles; the current shape-only choice is not evidence. Does the exact source output the full target mode on this physical port? Does the selected display input accept that mode, protocol and direction? Does the actual cable or converter document both ends and the complete target? Have host/OS requirements, length, color format, compression and any supplied converter power been checked? Review limits · 4 A documentation brief, not a recommendation to buy or connect hardware. No performance, compatibility or electrical approval is produced. Only a single source, one investigated cable/converter class and a single display input are represented. Docks, KVMs, branches, charging and simultaneous displays require a separate analysis. Profile assertions come from manufacturer pages; no independent human approval or hardware test is implied. Source dates are retained, not refreshed by opening this brief. A missing connection class is a scope boundary. Matching forms do not establish contacts, negotiated protocol or capability. Existing exact claim excerpts An active DisplayPort-to-HDMI converter translates a DisplayPort source for an HDMI display; direction is product-specific. C043A · S035
The DP2HD4KS manufacturer sheet identifies an active DisplayPort-input to HDMI-output adapter and lists both DP++ and non-DP++ sources in its host-compatibility scope. C043B · S035
DP2HD4KS is specified for 3840 x 2160 at 30 Hz; its performance table lists no HDR support. C043C · S035
Native source register: S012 · S014 · S015 · S018 · S035 · S036 · S365 · S368 · S450 · S451 · S452 · S453 · S518 · S520 · S606 · S644 · S976 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (2) — not measurements Requested target: Investigate a 3840 × 2160 at 60 Hz display task; color format, HDR and actual equipment still need documentation. Source → destination is the selected signal direction, not an instruction to reverse an adapter. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable display desk ↗
Evidence needed Case 19 / V172 addition
HDMI source to DisplayPort, no converter selected A known direction with no selected class is not an approved one-step path.
The native reader lacks one or more facts required for this described task.
01 Source / output HDMI source (unverified) form only Verify the actual output role and complete target mode on this exact port.
02 Cable / converter No class selected class only Check both ends, documented direction, target and any product-specific auxiliary power.
03 Destination / input DisplayPort display input (unverified) form only Verify the selected input accepts the requested mode and transport.
Check first Source / output: identify the exact device and verify its role; only a form is selected.
Read evidence and missing conditions ↗
Still missing · 9 Source / output: identify the exact device and verify its role; only a form is selected. Destination / input: identify the exact device and verify its role; only a form is selected. Choose a direction-specific class explicitly. Select one direction-specific connection class to investigate. Identify the actual devices and verify their output/input roles; the current shape-only choice is not evidence. Does the exact source output the full target mode on this physical port? Does the selected display input accept that mode, protocol and direction? Does the actual cable or converter document both ends and the complete target? +1 more in the native worksheet
Review limits · 4 A documentation brief, not a recommendation to buy or connect hardware. No performance, compatibility or electrical approval is produced. Only a single source, one investigated cable/converter class and a single display input are represented. Docks, KVMs, branches, charging and simultaneous displays require a separate analysis. Profile assertions come from manufacturer pages; no independent human approval or hardware test is implied. Source dates are retained, not refreshed by opening this brief. A missing connection class is a scope boundary. Matching forms do not establish contacts, negotiated protocol or capability. Native source register: S012 · S014 · S015 · S018 · S036 · S365 · S368 · S450 · S451 · S452 · S453 · S518 · S520 · S606 · S644 · S976 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (2) — not measurements Requested target: Investigate a 3840 × 2160 at 60 Hz display task; color format, HDR and actual equipment still need documentation. Source → destination is the selected signal direction, not an instruction to reverse an adapter. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable display desk ↗
Selection rejected Case 20 / V172 addition
Reversing a USB-C-to-HDMI class Changing which device outputs video invalidates a one-way class.
The native validator rejected this ordered selection. No path or hardware verdict was generated.
Path withheld by the native validator. No fabricated source, adapter or destination chain is displayed for an invalid selection.
Check first The selected class does not describe this directed one-step pair. Choose a new class after changing either end.
Read evidence and missing conditions ↗
Still missing · 0 No unchecked category in this narrow projection. This is not working-connection approval.
Review limits · 0 All original source and physical-check limits remain.
Native source register: No scoped source is attached to this rejected input. Original inspection dates and limitations remain in each record.
Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable display desk ↗
Evidence needed Case 21 / V172 addition
Exact host documentation, different display input Source-scope evidence cannot automatically establish the new destination input.
The native reader lacks one or more facts required for this described task.
01 Source / output MacBook Air (13-inch, M4, 2025) / Thunderbolt 4 / USB-C scoped profile Verify the actual output role and complete target mode on this exact port.
S065 02 Cable / converter USB-C → DisplayPort cable class only Check both ends, documented direction, target and any product-specific auxiliary power.
S037 · S519 03 Destination / input Dell UltraSharp U2723QE / DisplayPort input scoped profile Verify the selected input accepts the requested mode and transport.
S061 Check first Check which video transport the exact source port and destination document; charging or connector shape alone does not answer this.
Read evidence and missing conditions ↗
Still missing · 5 Check which video transport the exact source port and destination document; charging or connector shape alone does not answer this. Does the exact source output the full target mode on this physical port? Does the selected display input accept that mode, protocol and direction? Does the actual cable or converter document both ends and the complete target? Have host/OS requirements, length, color format, compression and any supplied converter power been checked? Review limits · 4 A documentation brief, not a recommendation to buy or connect hardware. No performance, compatibility or electrical approval is produced. Only a single source, one investigated cable/converter class and a single display input are represented. Docks, KVMs, branches, charging and simultaneous displays require a separate analysis. Profile assertions come from manufacturer pages; no independent human approval or hardware test is implied. Source dates are retained, not refreshed by opening this brief. A missing connection class is a scope boundary. Matching forms do not establish contacts, negotiated protocol or capability. Existing exact claim excerpts USB-C to DisplayPort video requires supported DisplayPort transport; some specifically documented cables also support the reverse direction. C042A · S037
VESA states that an Alt Mode display receives no image when connected to a USB-C port that does not support DisplayPort over USB-C. C042B · S519
Native source register: S003 · S014 · S015 · S036 · S037 · S061 · S062 · S064 · S065 · S368 · S446 · S447 · S448 · S449 · S450 · S451 · S452 · S453 · S511 · S519 · S520 · S605 · S643 · S644 · S972 · S976 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (2) — not measurements Requested target: Investigate a 3840 × 2160 at 60 Hz display task; color format, HDR and actual equipment still need documentation. Source → destination is the selected signal direction, not an instruction to reverse an adapter. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable display desk ↗
Evidence needed Case 22 / V172 addition
HDMI to HDMI, direct cable-class question A direct-form class still does not authenticate the physical cable or requested video mode.
The native reader lacks one or more facts required for this described task.
01 Source / output HDMI source (unverified) form only Verify the actual output role and complete target mode on this exact port.
02 Cable / converter HDMI-family direct cable class only Check both ends, documented direction, target and any product-specific auxiliary power.
03 Destination / input HDMI display input (unverified) form only Verify the selected input accepts the requested mode and transport.
Check first Source / output: identify the exact device and verify its role; only a form is selected.
Read evidence and missing conditions ↗
Still missing · 7 Source / output: identify the exact device and verify its role; only a form is selected. Destination / input: identify the exact device and verify its role; only a form is selected. Identify the actual devices and verify their output/input roles; the current shape-only choice is not evidence. Does the exact source output the full target mode on this physical port? Does the selected display input accept that mode, protocol and direction? Does the actual cable or converter document both ends and the complete target? Have host/OS requirements, length, color format, compression and any supplied converter power been checked? Review limits · 4 A documentation brief, not a recommendation to buy or connect hardware. No performance, compatibility or electrical approval is produced. Only a single source, one investigated cable/converter class and a single display input are represented. Docks, KVMs, branches, charging and simultaneous displays require a separate analysis. Profile assertions come from manufacturer pages; no independent human approval or hardware test is implied. Source dates are retained, not refreshed by opening this brief. A missing connection class is a scope boundary. Matching forms do not establish contacts, negotiated protocol or capability. Native source register: S012 · S014 · S018 · S036 · S365 · S450 · S451 · S452 · S453 · S518 · S606 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (2) — not measurements Requested target: Investigate a 3840 × 2160 at 60 Hz display task; color format, HDR and actual equipment still need documentation. Source → destination is the selected signal direction, not an instruction to reverse an adapter. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable display desk ↗
Evidence needed Case 07 / V159 retained
A charging claim is the only cable evidence A power observation does not fill the data-capability field.
The native reader lacks one or more facts required for this described task.
01 Host / data role Manually identified USB-C host form only Check the exact host role and requested peripheral task.
02 Cable / data path USB-C to USB-C data cable class only Document the exact cable data mode separately from charging power.
03 Peripheral / destination Manually identified USB-C peripheral form only Check its actual data port, task, software and power requirements.
Check first Host / data role: exact device identity and task support are unknown.
Read evidence and missing conditions ↗
Still missing · 6 Host / data role: exact device identity and task support are unknown. Peripheral / destination: exact device identity and task support are unknown. Host data role: record the missing documentation or observation. Peripheral and task: record the missing documentation or observation. Cable data capability: record the missing documentation or observation. Software and operating system: record the missing documentation or observation. Review limits · 9 Confirm the intended file system, workload, sustained behavior and the actual USB mode for this host, drive and cable. Verify the host role and the peripheral port role from their exact documentation. Verify the complete cable data specification, both physical ends and any actual adapters. Check the power requirement independently; a power-marked cable or USB-C input is not proof of a working data connection. Keep operating-system, driver, application and permission requirements with the task. +4 more in the native worksheet
Native source register: S003 · S004 · S015 · S040 · S062 · S064 · S074 · S446 · S447 · S448 · S449 · S450 · S451 · S452 · S453 · S511 · S605 · S643 · S972 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (1) — not measurements Power requirements — owner observation: Synthetic observation: device charges. No data capability has been documented. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable usb desk ↗
Documented class only Case 08 / V159 retained
Every USB evidence category has an owner note Recorded notes are not independent checks. Planner capabilities remain unknown.
The native reader can describe the selected source scope. Owner observations are not independently verified.
01 Host / data role MacBook Air (13-inch, M4, 2025) / Thunderbolt 4 / USB-C scoped profile Check the exact host role and requested peripheral task.
S065 02 Cable / data path USB-C to USB-C data cable class only Document the exact cable data mode separately from charging power.
03 Peripheral / destination Kingston XS1000 / USB-C drive connection scoped profile Check its actual data port, task, software and power requirements.
S073 Check first Confirm the intended file system, workload, sustained behavior and the actual USB mode for this host, drive and cable.
Read evidence and missing conditions ↗
Still missing · 0 No unchecked category in this narrow projection. This is not working-connection approval.
Review limits · 9 Confirm the intended file system, workload, sustained behavior and the actual USB mode for this host, drive and cable. Verify the host role and the peripheral port role from their exact documentation. Verify the complete cable data specification, both physical ends and any actual adapters. Check the power requirement independently; a power-marked cable or USB-C input is not proof of a working data connection. Keep operating-system, driver, application and permission requirements with the task. +4 more in the native worksheet
Native source register: S003 · S004 · S015 · S040 · S062 · S064 · S065 · S073 · S074 · S446 · S447 · S448 · S449 · S450 · S451 · S452 · S453 · S511 · S605 · S643 · S972 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (5) — not measurements Host data role — owner observation: Synthetic owner observation; exact documentation requires independent review. Peripheral and task — owner observation: Synthetic owner observation; exact documentation requires independent review. Cable data capability — owner observation: Synthetic owner observation; exact documentation requires independent review. Power requirements — owner observation: Synthetic owner observation; exact documentation requires independent review. Software and operating system — owner observation: Synthetic owner observation; exact documentation requires independent review. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable usb desk ↗
Stop and resolve Case 09 / V159 retained
An owner note conflicts with the intended USB task The conflict stays visible until it is explicitly resolved.
The existing engine found conflicting assumptions or documented limits; do not bypass the stop.
01 Host / data role MacBook Air (13-inch, M4, 2025) / Thunderbolt 4 / USB-C scoped profile Check the exact host role and requested peripheral task.
S065 02 Cable / data path USB-C to USB-C data cable class only Document the exact cable data mode separately from charging power.
03 Peripheral / destination Kingston XS1000 / USB-C drive connection scoped profile Check its actual data port, task, software and power requirements.
S073 Check first Owner-reported Cable data capability: Synthetic cable description lists charging only; intended data support is unresolved.
Read evidence and missing conditions ↗
Still missing · 4 Host data role: record the missing documentation or observation. Peripheral and task: record the missing documentation or observation. Power requirements: record the missing documentation or observation. Software and operating system: record the missing documentation or observation. Review limits · 9 Confirm the intended file system, workload, sustained behavior and the actual USB mode for this host, drive and cable. Verify the host role and the peripheral port role from their exact documentation. Verify the complete cable data specification, both physical ends and any actual adapters. Check the power requirement independently; a power-marked cable or USB-C input is not proof of a working data connection. Keep operating-system, driver, application and permission requirements with the task. +4 more in the native worksheet
Native source register: S003 · S004 · S015 · S040 · S062 · S064 · S065 · S073 · S074 · S446 · S447 · S448 · S449 · S450 · S451 · S452 · S453 · S511 · S605 · S643 · S972 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (1) — not measurements Cable data capability — owner conflict: Synthetic cable description lists charging only; intended data support is unresolved. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable usb desk ↗
Selection rejected Case 10 / V159 retained
A dock is selected as a direct USB endpoint An ineligible role is rejected, not replaced with a similar-looking form.
The native validator rejected this ordered selection. No path or hardware verdict was generated.
Path withheld by the native validator. No fabricated source, adapter or destination chain is displayed for an invalid selection.
Check first That port is not an eligible direct USB-data endpoint on this side. Power-only inputs, monitor hubs, docks, dual-role phone/tablet assumptions and host-to-host links are not substituted.
Read evidence and missing conditions ↗
Still missing · 0 No unchecked category in this narrow projection. This is not working-connection approval.
Review limits · 0 All original source and physical-check limits remain.
Native source register: No scoped source is attached to this rejected input. Original inspection dates and limitations remain in each record.
Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable usb desk ↗
Evidence needed Case 23 / V172 addition
USB cable, not even a charging observation Removing a recorded power observation cannot establish a USB data path.
The native reader lacks one or more facts required for this described task.
01 Host / data role Manually identified USB-C host form only Check the exact host role and requested peripheral task.
02 Cable / data path USB-C to USB-C data cable class only Document the exact cable data mode separately from charging power.
03 Peripheral / destination Manually identified USB-C peripheral form only Check its actual data port, task, software and power requirements.
Check first Host / data role: exact device identity and task support are unknown.
Read evidence and missing conditions ↗
Still missing · 7 Host / data role: exact device identity and task support are unknown. Peripheral / destination: exact device identity and task support are unknown. Host data role: record the missing documentation or observation. Peripheral and task: record the missing documentation or observation. Cable data capability: record the missing documentation or observation. Power requirements: record the missing documentation or observation. Software and operating system: record the missing documentation or observation. Review limits · 9 Confirm the intended file system, workload, sustained behavior and the actual USB mode for this host, drive and cable. Verify the host role and the peripheral port role from their exact documentation. Verify the complete cable data specification, both physical ends and any actual adapters. Check the power requirement independently; a power-marked cable or USB-C input is not proof of a working data connection. Keep operating-system, driver, application and permission requirements with the task. +4 more in the native worksheet
Native source register: S003 · S004 · S015 · S040 · S062 · S064 · S074 · S446 · S447 · S448 · S449 · S450 · S451 · S452 · S453 · S511 · S605 · S643 · S972 Original inspection dates and limitations remain in each record.
Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable usb desk ↗
Evidence needed Case 24 / V172 addition
Host identity reverted to connector form only Complete owner notes cannot prove host capability, especially if the exact host identity is missing.
The native reader lacks one or more facts required for this described task.
01 Host / data role Manually identified USB-C host form only Check the exact host role and requested peripheral task.
02 Cable / data path USB-C to USB-C data cable class only Document the exact cable data mode separately from charging power.
03 Peripheral / destination Kingston XS1000 / USB-C drive connection scoped profile Check its actual data port, task, software and power requirements.
S073 Check first Host / data role: exact device identity and task support are unknown.
Read evidence and missing conditions ↗
Still missing · 2 Host / data role: exact device identity and task support are unknown. Host data role: record the missing documentation or observation. Review limits · 9 Confirm the intended file system, workload, sustained behavior and the actual USB mode for this host, drive and cable. Verify the host role and the peripheral port role from their exact documentation. Verify the complete cable data specification, both physical ends and any actual adapters. Check the power requirement independently; a power-marked cable or USB-C input is not proof of a working data connection. Keep operating-system, driver, application and permission requirements with the task. +4 more in the native worksheet
Native source register: S003 · S004 · S015 · S040 · S062 · S064 · S073 · S074 · S446 · S447 · S448 · S449 · S450 · S451 · S452 · S453 · S511 · S605 · S643 · S972 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (4) — not measurements Peripheral and task — owner observation: Synthetic owner observation; exact documentation requires independent review. Cable data capability — owner observation: Synthetic owner observation; exact documentation requires independent review. Power requirements — owner observation: Synthetic owner observation; exact documentation requires independent review. Software and operating system — owner observation: Synthetic owner observation; exact documentation requires independent review. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable usb desk ↗
Task area / dock
Docks and multiple displays Native resources, upstream cable and software paths
Open dock worksheet ↗
Stop and resolve Case 11 / V159 retained
Two dock sockets, a constrained native display count Socket count is not an independent-display count.
The existing engine found conflicting assumptions or documented limits; do not bypass the stop.
01 Source / host MacBook Air (M1, 2020) — Thunderbolt / USB4 scoped profile Check native display count, selected operating system, lid state and other stated conditions.
S153 02 Upstream cable Unidentified upstream cable owner input Check the actual host-to-dock transport and cable documentation.
03 Intermediate / dock CalDigit TS4 scoped profile Check transport, shared outputs, firmware and software paths separately.
S147 04 Destination / path 1 Dell UltraSharp U2723QE — DisplayPort input · unit 1 scoped profile Document output dp, requested 3840 × 2160 at 60 Hz, and this path’s cable (owner state: unknown).
S158 05 Destination / path 2 Dell UltraSharp U2723QE — USB-C video upstream · unit 2 scoped profile Document output tb-1, requested 3840 × 2160 at 60 Hz, and this path’s cable (owner state: unknown).
S158 Check first Whole selection · Host native-display count: 2 listed native path(s), against the scoped 1-display host count with lid open. Software-rendered paths are counted separately; resolution and actual operation remain unverified.
Read evidence and missing conditions ↗
Still missing · 4 Whole selection · Upstream cable: Exact upstream cable evidence has not been checked. Whole selection · Simultaneous resolution table: No exact normalized simultaneous-mode table case matches all recorded conditions. This does not mean the request is unsupported. HBR, DSC, refresh rate and lower-mode substitutions are never inferred. Path 1 / DisplayPort output · Exact display cable: No exact display cable evidence has been recorded. Path 2 / Downstream Thunderbolt 1 · Exact display cable: No exact display cable evidence has been recorded. Review limits · 4 Whole selection · Scope: Only the paths listed here are counted. Other external displays on the host would change the native budget; no second dock, daisy chain or split screen is modeled. Path 1 / DisplayPort output · Requested display mode: Requested 3840 × 2160 at 60 Hz; monitor reference mode 3840 × 2160 at 60 Hz. A panel reference is not an exact input timing table or a simultaneous dock-mode guarantee. Path 2 / Downstream Thunderbolt 1 · Requested display mode: Requested 3840 × 2160 at 60 Hz; monitor reference mode 3840 × 2160 at 60 Hz. A panel reference is not an exact input timing table or a simultaneous dock-mode guarantee. One exact host port group, one dock and up to four direct monitor paths for independent extended desktops. No other external displays, daisy chains, splitters, PBP/PIP, eGPUs, charging assessment or hardware tests are modeled. A documented count or table row is not a connection approval; unknown does not mean incompatible. Native source register: S147 · S153 · S158 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (3) — not measurements transport: thunderbolt (owner selection, not a measurement) platform: macos (owner selection, not a measurement) lid: open (owner selection, not a measurement) Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable dock desk ↗
Evidence needed Case 12 / V159 retained
Native and software-rendered displays together Owner-declared software states are not permissions granted or checked by this site.
The native reader lacks one or more facts required for this described task.
01 Source / host MacBook Air (M1, 2020) — Thunderbolt / USB4 scoped profile Check native display count, selected operating system, lid state and other stated conditions.
S153 02 Upstream cable Owner-declared upstream cable state: documented owner input Check the actual host-to-dock transport and cable documentation.
03 Intermediate / dock Plugable UD-6950PDZ scoped profile Check transport, shared outputs, firmware and software paths separately.
S151 · S152 04 Destination / path 1 Dell UltraSharp U2723QE — HDMI input · unit 1 scoped profile Document output hdmi-1, requested 3840 × 2160 at 60 Hz, and this path’s cable (owner state: documented).
S158 05 Destination / path 2 Dell UltraSharp U2723QE — HDMI input · unit 2 scoped profile Document output hdmi-2, requested 3840 × 2160 at 60 Hz, and this path’s cable (owner state: documented).
S158 06 Destination / path 3 Dell UltraSharp U2723QE — HDMI input · unit 3 scoped profile Document output hdmi-3, requested 3840 × 2160 at 60 Hz, and this path’s cable (owner state: documented).
S158 Check first Whole selection · Simultaneous resolution table: No exact normalized simultaneous-mode table case matches all recorded conditions. This does not mean the request is unsupported. HBR, DSC, refresh rate and lower-mode substitutions are never inferred.
Read evidence and missing conditions ↗
Still missing · 1 Whole selection · Simultaneous resolution table: No exact normalized simultaneous-mode table case matches all recorded conditions. This does not mean the request is unsupported. HBR, DSC, refresh rate and lower-mode substitutions are never inferred. Review limits · 5 Whole selection · Scope: Only the paths listed here are counted. Other external displays on the host would change the native budget; no second dock, daisy chain or split screen is modeled. Path 1 / Display 1 — HDMI · Requested display mode: Requested 3840 × 2160 at 60 Hz; monitor reference mode 3840 × 2160 at 60 Hz. A panel reference is not an exact input timing table or a simultaneous dock-mode guarantee. Path 2 / Display 2 — HDMI · Requested display mode: Requested 3840 × 2160 at 60 Hz; monitor reference mode 3840 × 2160 at 60 Hz. A panel reference is not an exact input timing table or a simultaneous dock-mode guarantee. Path 3 / Display 3 — HDMI · Requested display mode: Requested 3840 × 2160 at 60 Hz; monitor reference mode 3840 × 2160 at 60 Hz. A panel reference is not an exact input timing table or a simultaneous dock-mode guarantee. One exact host port group, one dock and up to four direct monitor paths for independent extended desktops. No other external displays, daisy chains, splitters, PBP/PIP, eGPUs, charging assessment or hardware tests are modeled. A documented count or table row is not a connection approval; unknown does not mean incompatible. Native source register: S151 · S152 · S153 · S158 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (6) — not measurements transport: usb-c-dp (owner selection, not a measurement) platform: macos (owner selection, not a measurement) upstream cable: documented (owner selection, not a measurement) driver: running (owner selection, not a measurement) permission: granted (owner selection, not a measurement) purpose: productivity (owner selection, not a measurement) Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable dock desk ↗
Evidence needed Case 13 / V159 retained
The resolution is listed, but conditions are unknown A reference-table match is not a measured video-mode result.
The native reader lacks one or more facts required for this described task.
01 Source / host Dell Latitude 7440 — Thunderbolt 4 / DisplayPort Alt Mode scoped profile Check native display count, selected operating system, lid state and other stated conditions.
S157 02 Upstream cable Unidentified upstream cable owner input Check the actual host-to-dock transport and cable documentation.
03 Intermediate / dock Dell Thunderbolt Dock WD22TB4 scoped profile Check transport, shared outputs, firmware and software paths separately.
S148 · S149 04 Destination / path 1 Dell UltraSharp U2723QE — DisplayPort input · unit 1 scoped profile Document output dp-1, requested 3840 × 2160 at 60 Hz, and this path’s cable (owner state: unknown).
S158 05 Destination / path 2 Dell UltraSharp U2723QE — DisplayPort input · unit 2 scoped profile Document output dp-2, requested 3840 × 2160 at 60 Hz, and this path’s cable (owner state: unknown).
S158 Check first Whole selection · Upstream cable: Exact upstream cable evidence has not been checked.
Read evidence and missing conditions ↗
Still missing · 5 Whole selection · Upstream cable: Exact upstream cable evidence has not been checked. Whole selection · Host native-display count: The current host/platform scope does not establish a native external-display count. Do not infer it from two physical ports. Whole selection · Simultaneous resolution table: No exact normalized simultaneous-mode table case matches all recorded conditions. This does not mean the request is unsupported. HBR, DSC, refresh rate and lower-mode substitutions are never inferred. Path 1 / Rear DisplayPort 1 · Exact display cable: No exact display cable evidence has been recorded. Path 2 / Rear DisplayPort 2 · Exact display cable: No exact display cable evidence has been recorded. Review limits · 4 Whole selection · Scope: Only the paths listed here are counted. Other external displays on the host would change the native budget; no second dock, daisy chain or split screen is modeled. Path 1 / Rear DisplayPort 1 · Requested display mode: Requested 3840 × 2160 at 60 Hz; monitor reference mode 3840 × 2160 at 60 Hz. A panel reference is not an exact input timing table or a simultaneous dock-mode guarantee. Path 2 / Rear DisplayPort 2 · Requested display mode: Requested 3840 × 2160 at 60 Hz; monitor reference mode 3840 × 2160 at 60 Hz. A panel reference is not an exact input timing table or a simultaneous dock-mode guarantee. One exact host port group, one dock and up to four direct monitor paths for independent extended desktops. No other external displays, daisy chains, splitters, PBP/PIP, eGPUs, charging assessment or hardware tests are modeled. A documented count or table row is not a connection approval; unknown does not mean incompatible. Native source register: S148 · S149 · S157 · S158 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (2) — not measurements transport: usb-c-dp (owner selection, not a measurement) platform: windows (owner selection, not a measurement) Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable dock desk ↗
Evidence needed Case 25 / V172 addition
Dock path with unknown upstream cable and software state Upstream transport, display software and each downstream cable remain distinct requirements.
The native reader lacks one or more facts required for this described task.
01 Source / host MacBook Air (M1, 2020) — Thunderbolt / USB4 scoped profile Check native display count, selected operating system, lid state and other stated conditions.
S153 02 Upstream cable Unidentified upstream cable owner input Check the actual host-to-dock transport and cable documentation.
03 Intermediate / dock Plugable UD-6950PDZ scoped profile Check transport, shared outputs, firmware and software paths separately.
S151 · S152 04 Destination / path 1 Dell UltraSharp U2723QE — HDMI input · unit 1 scoped profile Document output hdmi-1, requested 3840 × 2160 at 60 Hz, and this path’s cable (owner state: unknown).
S158 05 Destination / path 2 Dell UltraSharp U2723QE — HDMI input · unit 2 scoped profile Document output hdmi-2, requested 3840 × 2160 at 60 Hz, and this path’s cable (owner state: unknown).
S158 Check first Whole selection · Upstream cable: Exact upstream cable evidence has not been checked.
Read evidence and missing conditions ↗
Still missing · 6 Whole selection · Upstream cable: Exact upstream cable evidence has not been checked. Whole selection · DisplayLink runtime: The DisplayLink runtime state is unknown. Hardware sockets alone do not supply these software-rendered displays. Whole selection · macOS screen permission: The relevant screen-access permission state is unknown. Whole selection · Simultaneous resolution table: No exact normalized simultaneous-mode table case matches all recorded conditions. This does not mean the request is unsupported. HBR, DSC, refresh rate and lower-mode substitutions are never inferred. Path 1 / Display 1 — HDMI · Exact display cable: No exact display cable evidence has been recorded. Path 2 / Display 2 — HDMI · Exact display cable: No exact display cable evidence has been recorded. Review limits · 4 Whole selection · Scope: Only the paths listed here are counted. Other external displays on the host would change the native budget; no second dock, daisy chain or split screen is modeled. Path 1 / Display 1 — HDMI · Requested display mode: Requested 3840 × 2160 at 60 Hz; monitor reference mode 3840 × 2160 at 60 Hz. A panel reference is not an exact input timing table or a simultaneous dock-mode guarantee. Path 2 / Display 2 — HDMI · Requested display mode: Requested 3840 × 2160 at 60 Hz; monitor reference mode 3840 × 2160 at 60 Hz. A panel reference is not an exact input timing table or a simultaneous dock-mode guarantee. One exact host port group, one dock and up to four direct monitor paths for independent extended desktops. No other external displays, daisy chains, splitters, PBP/PIP, eGPUs, charging assessment or hardware tests are modeled. A documented count or table row is not a connection approval; unknown does not mean incompatible. Native source register: S151 · S152 · S153 · S158 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (3) — not measurements transport: usb-c-dp (owner selection, not a measurement) platform: macos (owner selection, not a measurement) purpose: productivity (owner selection, not a measurement) Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable dock desk ↗
Stop and resolve Case 26 / V172 addition
The same dock with a changed host lid state An operating-state change can expose the native-output count boundary.
The existing engine found conflicting assumptions or documented limits; do not bypass the stop.
01 Source / host MacBook Air (M1, 2020) — Thunderbolt / USB4 scoped profile Check native display count, selected operating system, lid state and other stated conditions.
S153 02 Upstream cable Owner-declared upstream cable state: documented owner input Check the actual host-to-dock transport and cable documentation.
03 Intermediate / dock CalDigit TS4 scoped profile Check transport, shared outputs, firmware and software paths separately.
S147 04 Destination / path 1 Dell UltraSharp U2723QE — DisplayPort input · unit 1 scoped profile Document output dp, requested 3840 × 2160 at 60 Hz, and this path’s cable (owner state: unknown).
S158 05 Destination / path 2 Dell UltraSharp U2723QE — USB-C video upstream · unit 2 scoped profile Document output tb-1, requested 3840 × 2160 at 60 Hz, and this path’s cable (owner state: unknown).
S158 Check first Whole selection · Host native-display count: 2 listed native path(s), against the scoped 1-display host count with lid closed. Software-rendered paths are counted separately; resolution and actual operation remain unverified.
Read evidence and missing conditions ↗
Still missing · 3 Whole selection · Simultaneous resolution table: No exact normalized simultaneous-mode table case matches all recorded conditions. This does not mean the request is unsupported. HBR, DSC, refresh rate and lower-mode substitutions are never inferred. Path 1 / DisplayPort output · Exact display cable: No exact display cable evidence has been recorded. Path 2 / Downstream Thunderbolt 1 · Exact display cable: No exact display cable evidence has been recorded. Review limits · 4 Whole selection · Scope: Only the paths listed here are counted. Other external displays on the host would change the native budget; no second dock, daisy chain or split screen is modeled. Path 1 / DisplayPort output · Requested display mode: Requested 3840 × 2160 at 60 Hz; monitor reference mode 3840 × 2160 at 60 Hz. A panel reference is not an exact input timing table or a simultaneous dock-mode guarantee. Path 2 / Downstream Thunderbolt 1 · Requested display mode: Requested 3840 × 2160 at 60 Hz; monitor reference mode 3840 × 2160 at 60 Hz. A panel reference is not an exact input timing table or a simultaneous dock-mode guarantee. One exact host port group, one dock and up to four direct monitor paths for independent extended desktops. No other external displays, daisy chains, splitters, PBP/PIP, eGPUs, charging assessment or hardware tests are modeled. A documented count or table row is not a connection approval; unknown does not mean incompatible. Native source register: S147 · S153 · S158 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (4) — not measurements transport: thunderbolt (owner selection, not a measurement) platform: macos (owner selection, not a measurement) lid: closed (owner selection, not a measurement) upstream cable: documented (owner selection, not a measurement) Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable dock desk ↗
Stop and resolve Case 14 / V159 retained
A charger’s headline power is split across ports Stated load targets are assumptions, not measured consumption.
The existing engine found conflicting assumptions or documented limits; do not bypass the stop.
01 Source / charger Anker 735 Charger (Nano II 65W), A2667 scoped profile Check the exact occupied-port allocation and required output profile.
S161 02 Cable / load 1 No exact cable reference selected owner input Actual-cable evidence is unknown; a model reference is not a cable authentication.
03 Destination / load 1 Unknown / other device owner input Document the device input and required voltage/current or charging profile separately.
04 Cable / load 2 No exact cable reference selected owner input Actual-cable evidence is unknown; a model reference is not a cable authentication.
05 Destination / load 2 Unknown / other device owner input Document the device input and required voltage/current or charging profile separately.
Check first Whole selection · Source total: 70 W in stated targets; 0 targets remain unknown. Source headline ceiling: 65 W. A total within this number does not grant each port the same allowance.
Read evidence and missing conditions ↗
Still missing · 4 Load 1 / USB-C 1 · Voltage and current: A wattage target does not establish a shared voltage, current, PPS range or EPR negotiation. These remain unassessed. Load 1 / USB-C 1 · Cable evidence: No exact cable reference is established. Connector shape does not provide its power rating. Load 2 / USB-C 2 · Voltage and current: A wattage target does not establish a shared voltage, current, PPS range or EPR negotiation. These remain unassessed. Load 2 / USB-C 2 · Cable evidence: No exact cable reference is established. Connector shape does not provide its power rating. Review limits · 2 Load 1 / USB-C 1 · Target arithmetic: 45 W is within the 45 W selected documentary upper bound. This does not establish the voltage/current path, actual cable, runtime power, fast charging or safety. Published upper bounds and anonymous target assumptions only. A numeric allowance is not a compatible, safe, negotiated or fast-charging connection. No mains, battery, thermal, PPS/EPR negotiation, adapter chain or hardware operation is modeled. Native source register: S161 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (3) — not measurements Port occupancy: complete (owner selection) Load 1: watts target; cable evidence unknown. A stated requirement is not observed consumption. Load 2: watts target; cable evidence unknown. A stated requirement is not observed consumption. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable power desk ↗
Evidence needed Case 15 / V159 retained
Enough headline watts, missing voltage evidence An absent normalized profile is an evidence gap, not a verified unsupported result.
The native reader lacks one or more facts required for this described task.
01 Source / charger Raspberry Pi 27W USB-C Power Supply scoped profile Check the exact occupied-port allocation and required output profile.
S162 02 Cable / load 1 Source’s attached lead scoped profile Actual-cable evidence is unknown; a model reference is not a cable authentication.
S162 03 Destination / load 1 Unknown / other device owner input Document the device input and required voltage/current or charging profile separately.
Check first Load 1 / Factory-attached USB-C lead · Fixed profile: The requested voltage is not present in the normalized source evidence for this case. Missing evidence is not a finding of incompatibility.
Read evidence and missing conditions ↗
Still missing · 2 Load 1 / Factory-attached USB-C lead · Fixed profile: The requested voltage is not present in the normalized source evidence for this case. Missing evidence is not a finding of incompatibility. Load 1 / Factory-attached USB-C lead · Cable assembly: The original factory-attached lead is part of the source profile. Its physical identity and condition are owner observations; extensions and modified leads are outside scope. Review limits · 3 Whole selection · Source total: 20 W in stated targets; 0 targets remain unknown. Source headline ceiling: 27 W. A total within this number does not grant each port the same allowance. Load 1 / Factory-attached USB-C lead · Target arithmetic: 20 W is within the 27 W selected documentary upper bound. This does not establish the voltage/current path, actual cable, runtime power, fast charging or safety. Published upper bounds and anonymous target assumptions only. A numeric allowance is not a compatible, safe, negotiated or fast-charging connection. No mains, battery, thermal, PPS/EPR negotiation, adapter chain or hardware operation is modeled. Native source register: S162 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (2) — not measurements Port occupancy: complete (owner selection) Load 1: fixed target; cable evidence unknown. A stated requirement is not observed consumption. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable power desk ↗
Documented class only Case 16 / V159 retained
A target fits a documented upper bound Being within an arithmetic ceiling is not compatibility or delivered-power approval.
The native reader can describe the selected source scope. Owner observations are not independently verified.
01 Source / charger Raspberry Pi 27W USB-C Power Supply scoped profile Check the exact occupied-port allocation and required output profile.
S162 02 Cable / load 1 Source’s attached lead scoped profile Actual-cable evidence is documented; a model reference is not a cable authentication.
S162 03 Destination / load 1 Unknown / other device owner input Document the device input and required voltage/current or charging profile separately.
Check first Whole selection · Source total: 25.5 W in stated targets; 0 targets remain unknown. Source headline ceiling: 27 W. A total within this number does not grant each port the same allowance.
Read evidence and missing conditions ↗
Still missing · 0 No unchecked category in this narrow projection. This is not working-connection approval.
Review limits · 3 Whole selection · Source total: 25.5 W in stated targets; 0 targets remain unknown. Source headline ceiling: 27 W. A total within this number does not grant each port the same allowance. Load 1 / Factory-attached USB-C lead · Target arithmetic: 25.5 W is within the 25.5 W selected documentary upper bound. This does not establish the voltage/current path, actual cable, runtime power, fast charging or safety. Published upper bounds and anonymous target assumptions only. A numeric allowance is not a compatible, safe, negotiated or fast-charging connection. No mains, battery, thermal, PPS/EPR negotiation, adapter chain or hardware operation is modeled. Native source register: S162 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (2) — not measurements Port occupancy: complete (owner selection) Load 1: fixed target; cable evidence documented. A stated requirement is not observed consumption. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable power desk ↗
Evidence needed Case 27 / V172 addition
A power ceiling without cable documentation A numeric source ceiling and an exact cable assembly are different evidence categories.
The native reader lacks one or more facts required for this described task.
01 Source / charger Raspberry Pi 27W USB-C Power Supply scoped profile Check the exact occupied-port allocation and required output profile.
S162 02 Cable / load 1 Source’s attached lead scoped profile Actual-cable evidence is unknown; a model reference is not a cable authentication.
S162 03 Destination / load 1 Unknown / other device owner input Document the device input and required voltage/current or charging profile separately.
Check first Load 1 / Factory-attached USB-C lead · Cable assembly: The original factory-attached lead is part of the source profile. Its physical identity and condition are owner observations; extensions and modified leads are outside scope.
Read evidence and missing conditions ↗
Still missing · 1 Load 1 / Factory-attached USB-C lead · Cable assembly: The original factory-attached lead is part of the source profile. Its physical identity and condition are owner observations; extensions and modified leads are outside scope. Review limits · 3 Whole selection · Source total: 25.5 W in stated targets; 0 targets remain unknown. Source headline ceiling: 27 W. A total within this number does not grant each port the same allowance. Load 1 / Factory-attached USB-C lead · Target arithmetic: 25.5 W is within the 25.5 W selected documentary upper bound. This does not establish the voltage/current path, actual cable, runtime power, fast charging or safety. Published upper bounds and anonymous target assumptions only. A numeric allowance is not a compatible, safe, negotiated or fast-charging connection. No mains, battery, thermal, PPS/EPR negotiation, adapter chain or hardware operation is modeled. Native source register: S162 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (2) — not measurements Port occupancy: complete (owner selection) Load 1: fixed target; cable evidence unknown. A stated requirement is not observed consumption. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable power desk ↗
Selection rejected Case 28 / V172 addition
Out-of-contract current input is rejected An implausible worksheet entry is rejected before any power assessment; not a physical verdict.
The native validator rejected this ordered selection. No path or hardware verdict was generated.
Path withheld by the native validator. No fabricated source, adapter or destination chain is displayed for an invalid selection.
Check first selection.rows[0].required_ma: greater than maximum
Read evidence and missing conditions ↗
Still missing · 0 No unchecked category in this narrow projection. This is not working-connection approval.
Review limits · 0 All original source and physical-check limits remain.
Native source register: No scoped source is attached to this rejected input. Original inspection dates and limitations remain in each record.
Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable power desk ↗
Stop and resolve Case 29 / V172 addition
Shared charger, incomplete occupied-port evidence Headline watts cannot substitute for verified port allocation under real load.
The existing engine found conflicting assumptions or documented limits; do not bypass the stop.
01 Source / charger Anker 735 Charger (Nano II 65W), A2667 scoped profile Check the exact occupied-port allocation and required output profile.
S161 02 Cable / load 1 No exact cable reference selected owner input Actual-cable evidence is unknown; a model reference is not a cable authentication.
03 Destination / load 1 Unknown / other device owner input Document the device input and required voltage/current or charging profile separately.
04 Cable / load 2 No exact cable reference selected owner input Actual-cable evidence is unknown; a model reference is not a cable authentication.
05 Destination / load 2 Unknown / other device owner input Document the device input and required voltage/current or charging profile separately.
Check first Whole selection · Source total: 70 W in stated targets; 0 targets remain unknown. Source headline ceiling: 65 W. A total within this number does not grant each port the same allowance.
Read evidence and missing conditions ↗
Still missing · 5 Whole selection · Occupied ports: Confirm that all connected ports and attached cables are represented. Single-device ceilings do not prove other loads are absent. Load 1 / USB-C 1 · Voltage and current: A wattage target does not establish a shared voltage, current, PPS range or EPR negotiation. These remain unassessed. Load 1 / USB-C 1 · Cable evidence: No exact cable reference is established. Connector shape does not provide its power rating. Load 2 / USB-C 2 · Voltage and current: A wattage target does not establish a shared voltage, current, PPS range or EPR negotiation. These remain unassessed. Load 2 / USB-C 2 · Cable evidence: No exact cable reference is established. Connector shape does not provide its power rating. Review limits · 3 Whole selection · Allocation evidence: Selected documented case: Published upper bounds; no automatic redistribution or measured delivery. These are upper limits, not measured delivery. Load 1 / USB-C 1 · Target arithmetic: 45 W is within the 45 W selected documentary upper bound. This does not establish the voltage/current path, actual cable, runtime power, fast charging or safety. Published upper bounds and anonymous target assumptions only. A numeric allowance is not a compatible, safe, negotiated or fast-charging connection. No mains, battery, thermal, PPS/EPR negotiation, adapter chain or hardware operation is modeled. Native source register: S161 Original inspection dates and limitations remain in each record.
Owner-declared assumptions (3) — not measurements Port occupancy: unknown (owner selection) Load 1: watts target; cable evidence unknown. A stated requirement is not observed consumption. Load 2: watts target; cable evidence unknown. A stated requirement is not observed consumption. Documentation and explicitly recorded assumptions only. No compatibility, safety, negotiated rate, delivered power or measured performance approval. Source dates and review limits are unchanged.
Open the editable power desk ↗
What this does not establish: individual hardware fit, cable authenticity, firmware, certified interoperability, power negotiation or measured performance. Only existing evidence sources and limited authored selections were read. Read coverage limitations · Inspect the source register . One entry point / explicit rules
Begin with what you actually know. Choose a task, a visible connector or an exact model. The task router explains its destination without filling in your hardware or evidence. Task handoff and desk continuation remain optional, inspectable and reversible.
No hidden recommendation model. The rules distinguish task intent, physical identification and documented models. Every routed or continued step shows its reason, transfer preview and stop line before you leave the current desk.
The routing rule
Start with intent. A task can cross several connector forms and standards. The workflow should therefore begin with what you need to accomplish, then narrow to the exact devices, ports, cables and documented limits.
How the evidence model works → Before choosing a cable, qualify the path. Source-linked USB, power, Thunderbolt and video tables distinguish cable class from endpoint capability.
Open the capability library → Identify → Compare → Connect
A useful next step. Twenty-four worked reading tasks across the existing references and tools. An unconfirmed candidate, an ambiguous identity and no matching image remain different states. None is a compatibility verdict.
Miniature repair 6 tasks PC power 4 tasks RF & network 4 tasks Power & charging 2 tasks USB & display 4 tasks Storage & media 4 tasks The direct reference and inspection links work without JavaScript. Use source text rather than interpreting a simplified silhouette as an engineering drawing.
Start with the task and the exact equipment Eight bounded journeys separate connector form, documented role, conversion direction and missing prerequisites. No equipment is selected for you.
T01 · USB-C source to an HDMI display A USB-C-to-HDMI display path needs documented video output on the exact USB-C port and a converter for that direction. USB-C shape or successful charging does not establish video.
T02 · HDMI source to a USB-C display Do not reverse an ordinary USB-C-to-HDMI adapter. Investigate an exact converter documented from HDMI output to a USB-C display input; the destination’s USB-C shape alone does not establish display-input support.
T03 · DisplayPort source to an HDMI display For the named passive class, the DisplayPort source must document DP++ support. An active converter is a different product class; active does not itself promise a higher display mode.
T04 · Mini DisplayPort versus Thunderbolt Mini DisplayPort shape alone cannot distinguish a Mini DisplayPort display path from Thunderbolt 1/2. Identify the exact port protocol and display type before choosing an adapter.
T05 · TRS/TRRS headset connection Count the conductive plug sections, then establish the device’s audio role and wiring convention. TRRS shape does not choose CTIA versus OMTP microphone/ground assignment.
T06 · Ethernet markings versus port and PoE capability An 8P8C-style outline or cable category marking does not identify an Ethernet service or power role. Separate exact port function, the data path and any PoE requirement.
T07 · Barrel fit versus electrical requirements Do not energize a barrel-powered device from a size match. Outer/inner diameter and exposed mating length are separate from required voltage, polarity and available current; unresolved electrical or review scope is a stop.
T08 · GPU versus CPU auxiliary power Do not select a CPU/EPS or GPU/PCIe power cable by count, location or a similar shell. Use the exact PSU/cable type and motherboard/GPU documentation; unresolved cable identity or review scope is a stop.
