clm_364a096336e14e478ae9a51fe7301ac7_r1

NIEK2-0203

① SA Source

• Source: 開啟完整 SA 文章
• Section: Nvidia’s CPO Roadmap
• Line hint: 221

Context Before

Nvidia’s approach has been to use copper where they can, and optics where they must. The architecture of NVL1152 in the Feynman generation will follow the same principle. It is clear that the NVL1152 will adopt CPO to connect between racks, but from GPUs to NVLink Switches is currently copper POR. Nvidia is unable to achieve another doubling of electrical lane speed from 224Gbit/s bi-di to 448Gbit/s uni-di means bandwidth isn’t that amazing.

While 448G high speed SerDes have big challenges for shoreline, reach, and power versus using a die-to-die connection to an optical engine, the manufacturing challenges, cost, and reliability for Feynman necessitate using copper to the Switch.

Evidence

For now, our base case stands at copper being used within each rack and CPO between the racks

Context After

For now – our best estimate of Nvidia’s CPO roadmap is as follows:

Rubin:

② Atomic Claim

目前 SemiAnalysis 的 base case 是：每個機櫃內使用 copper，機櫃之間使用 CPO。

• Epistemic Mode: INFERRED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "additional_nodes": [],
  "frame_type": "RELATION",
  "object": {
    "id": "04_knowledge_base/CPO",
    "label": "CPO"
  },
  "predicate": "USES",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": [
      "目前"
    ]
  },
  "subject": {
    "id": "04_knowledge_base/Copper",
    "label": "copper"
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
subject	copper	Copper
object	CPO	CPO

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