VR2R-0166
① SA Source
- Source: 開啟完整 SA 文章
- Section:
CPX Form Factor - Line hint:
215
Context Before
Source: Nvidia VR NVL72 BoM and Power Budget Model ↗
Evidence
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:
Context After
VR NVL72 (Regular): Standard Oberon VR NVL72 without CPX
② Atomic Claim
回顧 Rubin 時代的 system planning，Nvidia 最初考慮過 3 種 VR NVL72 configurations。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Vera Rubin",
"label": "Rubin"
},
"role": "platform"
},
{
"node": {
"id": "02_companies/NVDA",
"label": "Nvidia"
},
"role": "vendor"
},
{
"node": {
"id": "04_knowledge_base/VR NVL72",
"label": "VR NVL72"
},
"role": "system"
}
],
"qualifiers": {
"condition_text": null,
"numeric_mentions": [
"3"
],
"temporal_mentions": [
"initially"
]
},
"relation_type": "INITIAL_VR_NVL72_CONFIGURATION_COUNT"
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| platform | Rubin | 04_knowledge_base/Vera Rubin |
| vendor | Nvidia | NVDA |
| system | VR NVL72 | 04_knowledge_base/VR NVL72 |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
回顧 Rubin 時代的 system planning，Nvidia 最初考慮過 3 種 VR NVL72 configurations。
V2 Semantic Frame Draft
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Vera Rubin",
"label": "Rubin"
},
"role": "platform"
},
{
"node": {
"id": "02_companies/NVDA",
"label": "Nvidia"
},
"role": "vendor"
},
{
"node": {
"id": "04_knowledge_base/VR NVL72",
"label": "VR NVL72"
},
"role": "system"
}
],
"qualifiers": {
"condition_text": null,
"numeric_mentions": [
"3"
],
"temporal_mentions": [
"initially"
]
},
"relation_type": "INITIAL_VR_NVL72_CONFIGURATION_COUNT"
}V2 Revision Metadata Draft
{
"epistemic_mode": "ASSERTED",
"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 才是正式決策。