SA260324R-0245
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Oberon and Kyber Updates, Larger World Sizes Introduced, More Networking Updates - Line hint:
303
Context Before
Source: SemiAnalysis Networking Model ↗
Evidence
Each NVLink Switch Chip connects via flyover cables to the connector (144 DPs used x 200 Gbit/s bi-di channel = 28.8Tbit/s) connectors at the edge of the switch blade, and these connectors plug into the midplane board. Nvidia is looking into using co-packaged Copper to reduce loss further, in case NPC doesn’t work. As far as we know the Nvidia is telling supply chain to go for fully co-packaged copper.
Context After
Rubin Ultra NVL288
Though not officially discussed by Nvidia at GTC 2026, an NVL288 concept has been explored within the supply chain. This would entail two NVL144 Kyber racks placed adjacent to each other, with a rack-to-rack copper backplane used to connect the two racks. One possibility is that all 288 GPUs are connected all to all, but this would require higher radix switches than the current NVLink 7 switches which only offer a maximum radix of 144 ports of 200G.
② Atomic Claim
In the March 2026 Kyber prototype/design discussion: Nvidia 正在評估使用 co-packaged Copper 進一步降低 loss，以防 NPC 無法運作。
- Epistemic Mode:
ASSERTED - Mapping Status:
PARTIAL
③ Semantic Frame
{
"additional_nodes": [],
"frame_type": "RELATION",
"object": {
"id": "04_knowledge_base/Copper",
"label": "Copper"
},
"predicate": "EVALUATES_CO_PACKAGED",
"qualifiers": {
"condition_text": "目的為進一步降低 loss；NPC 在此 atomic claim 沒有 canonical mapping",
"numeric_mentions": [],
"temporal_mentions": []
},
"subject": {
"id": "02_companies/NVDA",
"label": "Nvidia"
}
}④ Canonical Entity Mapping
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
In the March 2026 Kyber prototype/design discussion: Nvidia 正在評估使用 co-packaged Copper 進一步降低 loss，以防 NPC 無法運作。
V2 Semantic Frame Draft
{
"additional_nodes": [],
"frame_type": "RELATION",
"object": {
"id": "04_knowledge_base/Copper",
"label": "Copper"
},
"predicate": "EVALUATES_CO_PACKAGED",
"qualifiers": {
"condition_text": "目的為進一步降低 loss；NPC 在此 atomic claim 沒有 canonical mapping",
"numeric_mentions": [],
"temporal_mentions": []
},
"subject": {
"id": "02_companies/NVDA",
"label": "Nvidia"
}
}V2 Revision Metadata Draft
{
"epistemic_mode": "ASSERTED",
"mapping_status": "PARTIAL"
}⑥ 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 才是正式決策。