VR2R-0133::SPLIT01
① SA Source
- Source: 開啟完整 SA 文章
- Section:
ConnectX-9 - Line hint:
165
Context Before
Source: Nvidia VR NVL72 Component BoM and Power Budget Model ↗
Evidence
The ConnectX-9 is largely iterative from ConnectX-8, with the same 800G networking bandwidth and 48-lane PCIe6 switch capability. However, CX-9 now supports 800G Ethernet with 4x200G PAM4 SerDes, compared to CX-8 that only supported it on InfiniBand. For the Rubin platform, NVIDIA is doubling the number of NICs per GPU to achieve 2x scale-out bandwidth.
Context After
BlueField-4
② Atomic Claim
ConnectX-9 is largely iterative from ConnectX-8.
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "DESIGN_EVOLUTION",
"context_nodes": [
{
"id": "04_knowledge_base/ConnectX-8",
"label": "ConnectX-8"
}
],
"entity": {
"id": "04_knowledge_base/ConnectX-9",
"label": "ConnectX-9"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "ConnectX-9 is largely iterative from ConnectX-8."
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | ConnectX-9 | ConnectX-9 |
| context_0 | ConnectX-8 | ConnectX-8 |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
ConnectX-9 is largely iterative from ConnectX-8.
V2 Semantic Frame Draft
{
"attribute": "DESIGN_EVOLUTION",
"context_nodes": [
{
"id": "04_knowledge_base/ConnectX-8",
"label": "ConnectX-8"
}
],
"entity": {
"id": "04_knowledge_base/ConnectX-9",
"label": "ConnectX-9"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "ConnectX-9 is largely iterative from ConnectX-8."
}
}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 才是正式決策。