/apply/usb-quiet-utility-research
USB-C cable compatibility
Research stage · deterministic computation over committed research fixture data · not admitted · not certified · no canonical Counterpedia Answer identity
Question
I have a USB-C cable. Will it connect this MacBook Pro to this Studio Display?
Fixed objects: 14-inch MacBook Pro (M3 Pro, Nov 2023) + Apple Studio Display (2022)
Scenario USB-D1 — Cable A
Answer
Cable A: Apple 240W USB-C Charge Cable (2 m)
Why
| connector | compatible |
| video_transport | incompatible |
| power | compatible_with_ceiling |
Limiting factor
Power delivery ceiling: 96W (limited by Studio Display published output; cable ceiling is higher).
Video transport: cable explicitly does not support video (Apple USB-C Charge Cable, per USB-S03).
Applicability
Applies only to the exact fixed research fixture objects: 14-inch MacBook Pro M3 Pro (November 2023) + Apple Studio Display (2022) + Cable A. Do not apply this result to other configurations, hardware generations, or cable models without a separate derivation.
Why not a stronger answer?
This result is research-stage: derived from committed research fixture facts, not from captured and adjudicated source editions. No compatibility certification or recommendation is issued. The exact charging behavior of this cable connected to Studio Display when video is absent has not been empirically tested in this fixture.
Inputs
Host: MacBook Pro M3 Pro (2023) — 3× Thunderbolt 4 ports, USB-C, charging, DisplayPort (USB-S01). Display: Studio Display (2022) — Thunderbolt 3 USB-C input, 96W host charging (USB-S02). Cable A: USB-C connectors, 240W charging, does not support video (USB-S03, USB-S04).
Source roles: USB-S01 (host) · USB-S02 (display) · USB-S03/S04 (Cable A) · USB-S05 (Cable B) · USB-S06 (guidance)
These are research source-family refs — not SourceEditions; no custody chain exists at this stage.
Reproduce
To reproduce this result locally: run deriveUsbCompatibility(inputs) from lib/counterpedia/derivations/compatibilityIntersection.ts with the exact inputs below. Implementation ref: usb-compatibility-kernel/v0.1.
Not a canonical public derivation identity or hash.
Machine projection
{
"implementation_ref": "usb-compatibility-kernel/v0.1",
"inputs": {
"cable": {
"connector_usb_c": "present",
"video_transport": "absent",
"power_ceiling_watts": 240
},
"host": {
"has_usb_c_port": "present"
},
"display": {
"accepts_usb_c_input": "present",
"power_supply_ceiling_watts": 96
}
},
"result": {
"connector": "compatible",
"video_transport": "incompatible",
"power": "compatible_with_ceiling",
"power_ceiling_watts": 96,
"overall": "incompatible"
}
}Reader and machine are projections of the same internal derivation result.
Scenario USB-D2 — Cable B
Answer
Cable B: Apple Thunderbolt 4 (USB-C) Pro Cable (1.8 m)
Why
| connector | compatible |
| video_transport | compatible |
| power | compatible_with_ceiling |
Limiting factor
Power delivery ceiling: 96W (limited by Studio Display published output; cable ceiling is higher).
Applicability
Applies only to the exact fixed research fixture objects: 14-inch MacBook Pro M3 Pro (November 2023) + Apple Studio Display (2022) + Cable B. Do not apply this result to other configurations, hardware generations, or cable models without a separate derivation.
Why not a stronger answer?
This result is research-stage: derived from committed research fixture facts. No certification is issued. A higher power ceiling on the cable (100W) does not raise the display's published 96W charging output.
Inputs
Host: MacBook Pro M3 Pro (2023) (USB-S01). Display: Studio Display (2022) (USB-S02). Cable B: Thunderbolt 3 + 4, USB4 40Gb/s, DisplayPort HBR3 video, 100W charging (USB-S05). Apple explicitly lists Studio Display as a supported connection target (USB-S06).
Source roles: USB-S01 (host) · USB-S02 (display) · USB-S03/S04 (Cable A) · USB-S05 (Cable B) · USB-S06 (guidance)
These are research source-family refs — not SourceEditions; no custody chain exists at this stage.
Reproduce
To reproduce this result locally: run deriveUsbCompatibility(inputs) from lib/counterpedia/derivations/compatibilityIntersection.ts with the exact inputs below. Implementation ref: usb-compatibility-kernel/v0.1.
Not a canonical public derivation identity or hash.
Machine projection
{
"implementation_ref": "usb-compatibility-kernel/v0.1",
"inputs": {
"cable": {
"connector_usb_c": "present",
"video_transport": "present",
"power_ceiling_watts": 100
},
"host": {
"has_usb_c_port": "present"
},
"display": {
"accepts_usb_c_input": "present",
"power_supply_ceiling_watts": 96
}
},
"result": {
"connector": "compatible",
"video_transport": "compatible",
"power": "compatible_with_ceiling",
"power_ceiling_watts": 96,
"overall": "compatible"
}
}Reader and machine are projections of the same internal derivation result.
Scenario USB-D3 — UNKNOWN regression (cable-video proposition removed)
Answer
Cable (video capability unknown): USB-C cable — video transport capability not established
Why
| connector | compatible |
| video_transport | unknown |
| power | compatible_with_ceiling |
Limiting factor
Power delivery ceiling: 96W (limited by Studio Display published output; cable ceiling is higher).
Video transport: proposition absent — cannot determine from available facts.
Applicability
Applies only to the exact fixed research fixture objects: 14-inch MacBook Pro M3 Pro (November 2023) + Apple Studio Display (2022) + Cable (video capability unknown). Do not apply this result to other configurations, hardware generations, or cable models without a separate derivation.
Why not a stronger answer?
Without an explicit fact about whether this cable supports video transport, the derivation cannot produce a compatibility determination. USB-C connector shape alone does not imply video capability. The result is UNKNOWN — not a partial YES.
Inputs
Same host and display as above. Cable: USB-C connector present, 240W charging, video transport capability: UNKNOWN (proposition removed to exercise the regression case).
Source roles: USB-S01 (host) · USB-S02 (display) · USB-S03/S04 (Cable A) · USB-S05 (Cable B) · USB-S06 (guidance)
These are research source-family refs — not SourceEditions; no custody chain exists at this stage.
Reproduce
To reproduce this result locally: run deriveUsbCompatibility(inputs) from lib/counterpedia/derivations/compatibilityIntersection.ts with the exact inputs below. Implementation ref: usb-compatibility-kernel/v0.1.
Not a canonical public derivation identity or hash.
Machine projection
{
"implementation_ref": "usb-compatibility-kernel/v0.1",
"inputs": {
"cable": {
"connector_usb_c": "present",
"video_transport": "unknown",
"power_ceiling_watts": 240
},
"host": {
"has_usb_c_port": "present"
},
"display": {
"accepts_usb_c_input": "present",
"power_supply_ceiling_watts": 96
}
},
"result": {
"connector": "compatible",
"video_transport": "unknown",
"power": "compatible_with_ceiling",
"power_ceiling_watts": 96,
"overall": "unknown"
}
}Reader and machine are projections of the same internal derivation result.
Key insight
USB-C connector shape does not determine video or transport capability. Cable A (240W) has a higher power rating than Cable B (100W) but cannot support a display connection. A specification is not a score — compatibility is a derived relation among versioned objects, capabilities, requirements, and constraints.
Rule: connector shape alone never implies transport/video. Unresolved capability → UNKNOWN. Explicitly absent capability → INCOMPATIBLE.