VR-COV-VR-CPX-TRAY
① SA Source
- Source: 開啟完整 SA 文章
- Section:
CPX Form Factor - Line hint:
211
Context Before
On a side note, VR NVL72 was initially known as VR NVL144 as Jensen math ↗ from GTC 2025 defined the number of GPU as the number of GPU compute die in system (with 2 compute dies per package and 72 Rubin packages per Oberon rack = 144 compute die). The naming was changed back to VR NVL72 to represent the 72 Rubin GPU packages in the system in late December. This was right before CES 2026 where the naming was officially confirmed as VR NVL72.
CPX Form Factor
Evidence
Context After
Source: Nvidia VR NVL72 BoM and Power Budget Model ↗
Although Nvidia initially planned to integrate the CPX accelerator into the VR NVL72 rack, the current development suggests that CPX will only be offered as a standalone rack as we detailed in our article introducing Nvidia ↗CPX ↗. To recap Rubin-era system planning in our previous CPX article, Nvidia initially contemplated three VR NVL72 configurations:
② Atomic Claim
The proposed Rubin CPX rack diagram labels eight Rubin CPX GPUs per compute tray.
- Epistemic Mode:
ATTRIBUTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "GPUS_PER_PROPOSED_COMPUTE_TRAY",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/Rubin CPX",
"label": "Rubin CPX"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [
"8"
],
"value_text": "8"
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | Rubin CPX | 04_knowledge_base/Rubin CPX |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
The proposed Rubin CPX rack diagram labels eight Rubin CPX GPUs per compute tray.
V2 Semantic Frame Draft
{
"attribute": "GPUS_PER_PROPOSED_COMPUTE_TRAY",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/Rubin CPX",
"label": "Rubin CPX"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [
"8"
],
"value_text": "8"
}
}V2 Revision Metadata Draft
{
"epistemic_mode": "ATTRIBUTED",
"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 才是正式決策。