VR2R-0680
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Customization - Line hint:
911
Context Before
Source: Nvidia VR NVL72 Component BoM and Power Budget Model ↗
Evidence
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 DSP instead of Bluefield-4. 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. 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
Context After
Assembly Automation and Logistics
At CES 2026, Jensen mentioned that with the streamlined cableless design and automation assembly process, compute tray assembly time has significantly reduced from 2 hours to 5 minutes from Blackwell to Rubin. There are only three L10 level compute tray assembly partners with automation capability for the Rubin platform – Foxconn, Quanta, and Wistron.
② Atomic Claim
Some VR NVL72 customers are considering combining power-delivery and management modules.
- Epistemic Mode:
ASSERTED - Mapping Status:
PARTIAL
③ Semantic Frame
{
"frame_type": "CLAIM_ONLY",
"qualifiers": {
"condition_text": "VR NVL72 customization context",
"numeric_mentions": [],
"temporal_mentions": []
},
"reason": "MODULE_CATEGORIES_AND_CUSTOMERS_ARE_PLAIN_TEXT",
"statement": "Some VR NVL72 customers are considering combining power-delivery and management modules."
}④ Canonical Entity Mapping
- 此
CLAIM_ONLYrevision 沒有 canonical Entity mapping。
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
Some VR NVL72 customers are considering combining power-delivery and management modules.
V2 Semantic Frame Draft
{
"frame_type": "CLAIM_ONLY",
"qualifiers": {
"condition_text": "VR NVL72 customization context",
"numeric_mentions": [],
"temporal_mentions": []
},
"reason": "MODULE_CATEGORIES_AND_CUSTOMERS_ARE_PLAIN_TEXT",
"statement": "Some VR NVL72 customers are considering combining power-delivery and management modules."
}V2 Revision Metadata Draft
{
"epistemic_mode": "ASSERTED",
"mapping_status": "PARTIAL"
}⑥ 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 才是正式決策。