VR2R-0679_r1

VR2R-0679

① SA Source

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

Context Before

For VR NVL72, although some level of customization is still available, there are a lot more limitations on the form factor. 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.

Evidence

Given the limitation on form factor and dimensions, hyperscalers are redesigning the board layout and module form factor of their in-house DPU to match that of Bluefield-4.

Context After

For the power delivery modules and management, some customers are also looking to combine them. Amazon does have a JBOK / Nitro Box NIC version for VR NVL72.

② Atomic Claim

受到 form factor 與尺寸限制，hyperscalers 正重新設計自研 DPU 的 board layout 與 module form factor，使其符合 BlueField-4 的規格。

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/Hyperscaler",
        "label": "hyperscaler"
      },
      "role": "customer_type"
    },
    {
      "node": {
        "id": "04_knowledge_base/DPU",
        "label": "DPU"
      },
      "role": "custom_component"
    },
    {
      "node": {
        "id": "04_knowledge_base/BlueField-4",
        "label": "BlueField-4"
      },
      "role": "reference_component"
    }
  ],
  "qualifiers": {
    "condition_text": "form-factor and dimensional constraints",
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "relation_type": "HYPERSCALERS_REDESIGN_DPU_TO_MATCH_BLUEFIELD4_FORM_FACTOR"
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
customer_type	hyperscaler	Hyperscaler
custom_component	DPU	DPU
reference_component	BlueField-4	BlueField-4

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