VR2R-0157_r1

VR2R-0157

① SA Source

• Source: 開啟完整 SA 文章
• Section: Rubin Oberon Rack: NVL72 not NVL144 nor NVL36
• Line hint: 127

Context Before

The key difference between the Blackwell and Rubin Oberon architecture is the number of SKUs offered to customers. As Blackwell Oberon was the first ever mass deployment of a rack scale solution with rack power density over 100KW for the GB200 NVL72 SKU, many datacenters did not have the infrastructure ready to support 100kw+ per rack. Nvidia offered two SKUs of Blackwell Oberon: GB200 NVL72 and GB200 NVL36x2. The latter being a lower density SKU offered for customers who did not have the infra ready to handle the thermals of a single high density rack.

Evidence

Unlike Blackwell, Rubin is only offered in the VR NVL72 SKU.

Context After

The set up is very similar to that of GB200/GB300 NVL72. Each VR NVL72 system consists of:

② Atomic Claim

不同於 Blackwell，Rubin 只提供 VR NVL72 SKU。

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/Blackwell",
        "label": "Blackwell"
      },
      "role": "comparison_generation"
    },
    {
      "node": {
        "id": "04_knowledge_base/Vera Rubin",
        "label": "Rubin"
      },
      "role": "generation"
    },
    {
      "node": {
        "id": "04_knowledge_base/VR NVL72",
        "label": "VR NVL72"
      },
      "role": "sku"
    }
  ],
  "qualifiers": {
    "condition_text": "Rubin only offered in VR NVL72 SKU",
    "numeric_mentions": [
      "72"
    ],
    "temporal_mentions": []
  },
  "relation_type": "RUBIN_SINGLE_OBERON_SKU"
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
comparison_generation	Blackwell	Blackwell
generation	Rubin	04_knowledge_base/Vera Rubin
sku	VR NVL72	04_knowledge_base/VR NVL72

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