clm_e7a8d330a32c4e32903856d605c21be7_r2

SA260324R-0235

回到這篇 SA Coverage

① SA Source

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

Context Before

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

Evidence

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.

Context After

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. Connecting all 144 GPUs in an all-to-all network will require 72 NVLink 7.0 Switch Chips running at 28.8Tbit/s uni-di of aggregate bandwidth each.

② Atomic Claim

SemiAnalysis 預期 Rubin Ultra NVL576 的 inter-rack CPO 配置仍僅用於低量／測試用途。

• Epistemic Mode: EXPECTED
• Mapping Status: PARTIAL

③ Semantic Frame

{
  "frame_type": "CLAIM_ONLY",
  "qualifiers": {
    "condition_text": "承接前文 NVL576/CPO configuration; Rubin Ultra NVL576 inter-rack CPO; low-volume/testing roadmap",
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "reason": "THIS_REFERENT_DEPENDS_ON_PRIOR_CPO_CONFIGURATION",
  "statement": "SemiAnalysis 預期 [[04_knowledge_base/Rubin Ultra|Rubin Ultra]] [[04_knowledge_base/NVL576|NVL576]] 的 inter-rack [[04_knowledge_base/CPO|CPO]] 配置仍僅用於低量／測試用途。"
}

④ Canonical Entity Mapping

• 此 CLAIM_ONLY revision 沒有 canonical Entity mapping。

⑤ V2 Draft（需要修正時直接編輯）

Inline repair

只編輯以下三個 Draft 區塊。完成後將 review_action 設為 REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。

V2 Atomic Claim Draft

SemiAnalysis 預期 Rubin Ultra NVL576 的 inter-rack CPO 配置仍僅用於低量／測試用途。

V2 Semantic Frame Draft

{
  "frame_type": "CLAIM_ONLY",
  "qualifiers": {
    "condition_text": "承接前文 NVL576/CPO configuration; Rubin Ultra NVL576 inter-rack CPO; low-volume/testing roadmap",
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "reason": "THIS_REFERENT_DEPENDS_ON_PRIOR_CPO_CONFIGURATION",
  "statement": "SemiAnalysis 預期 [[04_knowledge_base/Rubin Ultra|Rubin Ultra]] [[04_knowledge_base/NVL576|NVL576]] 的 inter-rack [[04_knowledge_base/CPO|CPO]] 配置仍僅用於低量／測試用途。"
}

V2 Revision Metadata Draft

{
  "epistemic_mode": "EXPECTED",
  "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 才是正式決策。