VR2R-0154_r1

VR2R-0154

① SA Source

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

Context Before

The key difference between the Blackwell and Rubin Oberon architecture is the number of SKUs offered to customers.

Evidence

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.

Context After

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.

② Atomic Claim

Blackwell Oberon 的 GB200 NVL72 是第一批大規模部署、rack power density 超過 100KW 的 rack-scale solution；當時許多 datacenters 尚未具備支援每 rack 100KW+ 的 infrastructure。

• Epistemic Mode: ASSERTED
• Mapping Status: PARTIAL

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/Blackwell",
        "label": "Blackwell"
      },
      "role": "generation"
    },
    {
      "node": {
        "id": "04_knowledge_base/GB200 NVL72",
        "label": "GB200 NVL72"
      },
      "role": "system"
    },
    {
      "node": {
        "id": "04_knowledge_base/Power Density",
        "label": "power density"
      },
      "role": "metric"
    }
  ],
  "qualifiers": {
    "condition_text": "datacenters/infrastructure not canonicalized",
    "numeric_mentions": [
      "100KW",
      "100KW+"
    ],
    "temporal_mentions": []
  },
  "relation_type": "HIGH_POWER_RACK_DEPLOYMENT_CONSTRAINT"
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
generation	Blackwell	Blackwell
system	GB200 NVL72	04_knowledge_base/GB200 NVL72
metric	power density	04_knowledge_base/Power Density

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