clm_cc4cc65434fc4e03b34517b4087e3ba4_r1

NIEK2-0234

① SA Source

• Source: 開啟完整 SA 文章
• Section: Oberon and Kyber Updates, Larger World Sizes Introduced, More Networking Updates
• Line hint: 285

Context Before

Kyber midplane PCB (GPU side). Source: Nvidia, SemiAnalysis

For Rubin Ultra NVL144 Kyber, there will be no CPO used for scale up as we have told clients multiple times ↗, despite rumors from other analysts suggesting scale-up CPO introduction for Kyber. However, optics for NVLink are coming and will be progressively phased in. Scale-up CPO will first be used for the Rubin Ultra NVL 576 system to connect between 8 Oberon form factor racks, forming a two-layer all-to-all network. A copper backplane will still be used for scale-up networking within the racks however. This is still for low volume / testing purposes.

Evidence

Moving back to the Kyber Rack, each Rubin Ultra logical GPU offers 14.4Tbit/s uni-di of scale-up bandwidth, using an 80DP connector (72 DPs used x 200Gbit/s bi-di channel = 14.4Tbit/s) per GPU for connectivity to the midplane board

Context After

Source: SemiAnalysis

② Atomic Claim

回到 Kyber Rack，每顆 Rubin Ultra logical GPU 提供 14.4Tbit/s uni-di scale-up 頻寬；每顆 GPU 以一個 80DP connector（使用 72 DPs × 200Gbit/s bi-di channel＝14.4Tbit/s）連到 midplane board。

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "comparison_expression": "回到 Kyber Rack，每顆 Rubin Ultra logical GPU 提供 14.4Tbit/s uni-di scale-up 頻寬；每顆 GPU 以一個 80DP connector（使用 72 DPs × 200Gbit/s bi-di channel＝14.4Tbit/s）連到 midplane board。",
  "entities": [
    {
      "id": "04_knowledge_base/NVIDIA Kyber Rack",
      "label": "Kyber Rack"
    },
    {
      "id": "04_knowledge_base/Rubin Ultra",
      "label": "Rubin Ultra"
    },
    {
      "id": "04_knowledge_base/GPU",
      "label": "GPU"
    },
    {
      "id": "04_knowledge_base/14.4Tbit per second",
      "label": "14.4Tbit/s"
    },
    {
      "id": "04_knowledge_base/Midplane",
      "label": "midplane"
    }
  ],
  "frame_type": "COMPARISON",
  "metric": "BANDWIDTH",
  "operator": "MULTIPLE_OF",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "14.4Tb",
      "80",
      "72",
      "200Gb"
    ],
    "temporal_mentions": []
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
comparison_entity_0	Kyber Rack	04_knowledge_base/NVIDIA Kyber Rack
comparison_entity_1	Rubin Ultra	04_knowledge_base/Rubin Ultra
comparison_entity_2	GPU	GPU
comparison_entity_3	14.4Tbit/s	04_knowledge_base/14.4Tbit per second
comparison_entity_4	midplane	Midplane

⑤ 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 才是正式決策。