clm_77f869755fa14d72afb06591ec84f805_r2

VR2R-0026

回到這篇 SA Coverage

① SA Source

• Source: 開啟完整 SA 文章
• Section: Vera Rubin – Extreme Co-Design: An Evolution from Grace Blackwell Oberon
• Line hint: 35

Context Before

Next, we will discuss the major networks of the VR NVL72 system, namely the scale up NVLink 6 network and the backend scale out network. We will discuss the logistical implications of much more limited hyperscaler customisation and the assembly supplier landscape.

Lastly, the report ends with a discussion on the TCO of the VR NVL72 system as well as the BoM and Power Budget estimate supporting the TCO analysis. Behind the paywall, we also provide readers with insight into Nvidia’s plans for their Groq IP. We will also cover some of the challenges with regards to HBM ramp for Micron, SK Hynix, and Samsung.

Evidence

Today we are also launching the VR NVL72 Component BoM and Power Budget Model ↗. It provides a system-level bill of materials and power budget analysis for the VR NVL72 system covered in this article. This is important because various vendors and their shares of the subcomponents will drive whether they are winners or losers in the $500B Rubin buildout. The downstream impacts and dislocations in the market are large. The model covers:

Context After

**Nvidia Compute Tray Content: **Strata module with Rubin GPU, Vera CPU, SOCAMM memory; BlueField-4; ConnectX-9

② Atomic Claim

SemiAnalysis 預期，各 vendor 的 subcomponent share 將影響其在原文所述 $500B Rubin buildout 中的贏家／輸家地位。

• Epistemic Mode: EXPECTED
• Mapping Status: PARTIAL

③ Semantic Frame

{
  "attribute": "BUILDOUT_VALUE_AND_VENDOR_SHARE_IMPACT",
  "context_nodes": [],
  "entity": {
    "id": "04_knowledge_base/Vera Rubin",
    "label": "Rubin"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": "their refers to vendors from prior extraction fragment; SemiAnalysis expected vendor outcomes in the stated $500B Rubin buildout",
    "numeric_mentions": [
      "$500B"
    ],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [
      "$500B"
    ],
    "value_text": "Rubin buildout 規模為 5,000 億美元；vendor 的 subcomponent share 將影響其受益程度。"
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
entity	Rubin	04_knowledge_base/Vera Rubin

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

Inline repair

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

V2 Atomic Claim Draft

SemiAnalysis 預期，各 vendor 的 subcomponent share 將影響其在原文所述 $500B Rubin buildout 中的贏家／輸家地位。

V2 Semantic Frame Draft

{
  "attribute": "BUILDOUT_VALUE_AND_VENDOR_SHARE_IMPACT",
  "context_nodes": [],
  "entity": {
    "id": "04_knowledge_base/Vera Rubin",
    "label": "Rubin"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": "their refers to vendors from prior extraction fragment; SemiAnalysis expected vendor outcomes in the stated $500B Rubin buildout",
    "numeric_mentions": [
      "$500B"
    ],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [
      "$500B"
    ],
    "value_text": "Rubin buildout 規模為 5,000 億美元；vendor 的 subcomponent share 將影響其受益程度。"
  }
}

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