NIEK2-0376

① SA Source

Context Before

Interestingly, the Kyber rack exhibited at the GTC 2026 show floor is missing OSFP cages for scale-out networking. Instead, we only see 4x MPO ports from each compute tray. This design has effectively taken key pluggable transceiver items (driver, TIA, etc.) other than the DSP and put them on a Midboard Optical Module (MBOM) which then connects to the PCB via a land grid array (LGA) socket. Two CX-9s share one MBOM, which then connects to the MPO faceplate via a short fiber connection. The MBOM provides two MPO ports at 2x800G each for 1.6T of total connectivity.

image

Evidence

4 MPO ports on the left, rather than OSFP cages

Context After

The use of MBOM would block the use of any form of pluggable transceiver or AEC, and naturally hyperscalers are saying “CP-Hell No” to that idea and are continuing to push for an OSFP cage so they can continue using pluggables.

It is important to point out that many aspects of the Kyber design are still in flux and there could still be a number of design changes before Kyber racks are actually deployed. After all – the change from the four canister design to a two compute tray canister + one switch blade bank is already a huge change.

② Atomic Claim

圖左側可看到 4 個 MPO ports,而不是 OSFP cages。

  • Epistemic Mode: ASSERTED
  • Mapping Status: COMPLETE

③ Semantic Frame

{
  "attribute": "PORT_COUNT",
  "context_nodes": [
    {
      "id": "04_knowledge_base/OSFP (Octal Small Form-factor Pluggable)",
      "label": "OSFP"
    }
  ],
  "entity": {
    "id": "04_knowledge_base/MPO",
    "label": "MPO"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "4"
    ],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [
      "4"
    ],
    "value_text": "圖左側可看到 4 個 MPO ports,而不是 OSFP cages。"
  }
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
entityMPOMPO
context_0OSFP04_knowledge_base/OSFP (Octal Small Form-factor Pluggable)

⑤ Human Review

請在 Properties 逐項確認:

  • 原文 → Atomic Claim 是否忠實
  • Atomic Claim → Semantic Frame 是否忠實
  • Canonical Entity mapping 是否正確
  • Epistemic mode 是否保留原文語氣
  • 最後選擇 review_action

Review state

Markdown 內文不是正式 approval。只有 Apply bridge 寫入的 Decision Ledger event 才是正式決策。