VR2R-0154::SPLIT01

回到這篇 SA Coverage

① SA Source

Context Before

Rubin Oberon Rack: NVL72 not NVL144 nor NVL36

Since the announcement of GB200 at Nvidia GTC 2024, the concept of an AI server system has shifted from a chassis to a rack scale system. In our GB200 article ↗, we discussed the evolution of Nvidia AI server form factor from HGX (8 GPU per node) to Oberon (NVL72 rack scale). While the HGX form factor still exists, the majority of Nvidia’s Blackwell GPUs are integrated in the Oberon form factor. Rubin will also be offered in both HGX and Oberon systems.

Evidence

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. We discussed the difference between the two form factors in the GB200 article ↗. ↗

Context After

Unlike Blackwell, Rubin is only offered in the VR NVL72 SKU. The set up is very similar to that of GB200/GB300 NVL72. Each VR NVL72 system consists of:

② Atomic Claim

Blackwell Oberon GB200 NVL72 was the first mass deployment of a rack-scale solution with power density exceeding 100kW per rack.

  • Epistemic Mode: ASSERTED
  • Mapping Status: COMPLETE

③ Semantic Frame

{
  "attribute": "DEPLOYMENT_MILESTONE",
  "context_nodes": [
    {
      "id": "04_knowledge_base/Blackwell",
      "label": "Blackwell"
    },
    {
      "id": "04_knowledge_base/NVIDIA Oberon",
      "label": "Oberon"
    },
    {
      "id": "04_knowledge_base/Power Density",
      "label": "power density"
    }
  ],
  "entity": {
    "id": "04_knowledge_base/GB200 NVL72",
    "label": "GB200 NVL72"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "100kW"
    ],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [
      "100kW"
    ],
    "value_text": "Blackwell Oberon GB200 NVL72 was the first mass deployment of a rack-scale solution with power density exceeding 100kW per rack."
  }
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
entityGB200 NVL7204_knowledge_base/GB200 NVL72
context_0BlackwellBlackwell
context_1Oberon04_knowledge_base/NVIDIA Oberon
context_2power density04_knowledge_base/Power Density

⑤ V2 Draft(需要修正時直接編輯)

Inline repair

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

V2 Atomic Claim Draft

Blackwell Oberon GB200 NVL72 was the first mass deployment of a rack-scale solution with power density exceeding 100kW per rack.

V2 Semantic Frame Draft

{
  "attribute": "DEPLOYMENT_MILESTONE",
  "context_nodes": [
    {
      "id": "04_knowledge_base/Blackwell",
      "label": "Blackwell"
    },
    {
      "id": "04_knowledge_base/NVIDIA Oberon",
      "label": "Oberon"
    },
    {
      "id": "04_knowledge_base/Power Density",
      "label": "power density"
    }
  ],
  "entity": {
    "id": "04_knowledge_base/GB200 NVL72",
    "label": "GB200 NVL72"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "100kW"
    ],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [
      "100kW"
    ],
    "value_text": "Blackwell Oberon GB200 NVL72 was the first mass deployment of a rack-scale solution with power density exceeding 100kW per rack."
  }
}

V2 Revision Metadata Draft

{
  "epistemic_mode": "ASSERTED",
  "mapping_status": "COMPLETE"
}

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