VR2-0170
① SA Source
- Source: 開啟完整 SA 文章
- Section:
CPX Form Factor - Line hint:
227
Context Before
VR NVL72 CPX (Integrated): Rubin GPU and Rubin CPX within the same compute tray
Evidence
Context After
The standalone/dedicated rack direction materially changes the deployment calculus. A dual-rack approach allows hyperscalers to scale prefill and decode capacity independently, optimize datacenter power envelopes, and reduce system-level failure domains versus tightly coupled trays. More importantly, it formalizes architectural disaggregation between inference prefill (compute-bound) and decode (bandwidth-bound).
Rubin CPX was originally architected as a GDDR7-based accelerator optimized for prefill, based on three key considerations:
② Atomic Claim
VR NVL72 CPX（Dual Rack）：Rubin CPX 部署於獨立 rack，與 VR NVL72 rack 並列。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"additional_nodes": [
{
"id": "04_knowledge_base/Vera Rubin",
"label": "Rubin"
}
],
"frame_type": "RELATION",
"object": {
"id": "04_knowledge_base/CPX High-Density Interconnect Paradigm",
"label": "CPX"
},
"predicate": "CONNECTS_TO",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"subject": {
"id": "04_knowledge_base/VR NVL72",
"label": "VR NVL72"
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| subject | VR NVL72 | 04_knowledge_base/VR NVL72 |
| object | CPX | 04_knowledge_base/CPX High-Density Interconnect Paradigm |
| additional_0 | Rubin | 04_knowledge_base/Vera Rubin |
⑤ 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 才是正式決策。