VR2R-0675_r1

VR2R-0675

① SA Source

• Source: 開啟完整 SA 文章
• Section: Customization
• Line hint: 585

Context Before

For example, for some racks, even Amazon is deploying ConnectX-8 in GB300s in many cases. Also, most hyperscalers are deploying their in-house DPU instead of Bluefield-3 for frontend networking. The power delivery module and management modules in GB300 are also highly customized as every customer has differing preferences for these modules. As such, the front half of GB300 is highly customizable with each hyperscalers’ design differing from each other significantly.

Evidence

For VR NVL72, although some level of customization is still available, there are a lot more limitations on the form factor.

Context After

Given the modular and the cableless design of VR NVL72, the customized modules at the front of the chassis must match the form factor and dimension of Nvidia’s reference design. The modules available for customization are power delivery, Bluefield-4, and management modules. We expect most hyperscaler customers to adopt their in-house DPU instead of Bluefield-4.

② Atomic Claim

VR NVL72 雖然仍保留一定程度的客製化空間，但在 form factor 上的限制比 GB300 更多。

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/VR NVL72",
        "label": "VR NVL72"
      },
      "role": "platform"
    },
    {
      "node": {
        "id": "04_knowledge_base/GB300",
        "label": "GB300"
      },
      "role": "comparison_platform"
    }
  ],
  "qualifiers": {
    "condition_text": "customization remains available but more constrained",
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "relation_type": "VR_NVL72_HAS_MORE_FORM_FACTOR_LIMITS_THAN_GB300"
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
platform	VR NVL72	04_knowledge_base/VR NVL72
comparison_platform	GB300	GB300

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