NIEK2-0202

① SA Source

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

With that said, the NVL1152 SKU is years out – and the roadmap is highly likely to shift

Context After

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

Rubin:

② Atomic Claim

不過,NVL1152 SKU 距離實際推出還有數年,roadmap 很可能繼續調整。

  • Epistemic Mode: EXPECTED
  • Mapping Status: PARTIAL

③ Semantic Frame

{
  "attribute": "UNSPECIFIED_ATTRIBUTE",
  "context_nodes": [],
  "entity": {
    "id": "04_knowledge_base/NVL1152",
    "label": "NVL1152"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [],
    "value_text": "不過,NVL1152 SKU 距離實際推出還有數年,roadmap 很可能繼續調整。"
  }
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
entityNVL1152NVL1152

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