NIEK2-0204
① 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
this could easily change
Context After
For now – our best estimate of Nvidia’s CPO roadmap is as follows:
Rubin:
② Atomic Claim
關於 copper：這個設計仍可能輕易改變。
- Epistemic Mode:
HYPOTHETICAL - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "COUNT",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/Copper",
"label": "copper"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "關於 copper：這個設計仍可能輕易改變。"
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | copper | Copper |
⑤ 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 才是正式決策。