VR2R-0201::SPLIT03
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Orchid - Line hint:
303
Context Before

Source: Nvidia VR NVL72 BoM and Power Budget Model ↗
Evidence
The Orchid Module houses two ConnectX-9 NICs, two 800G transceiver cages, and one E1.S module slot. Four Orchid modules sit at the front of the chassis. With two Orchid modules stacked on top of each other, they occupy the front left and front right chassis space. At the end of the module there is one Paladin HD2 board-to-board connector that mates with the connector on the midplane. The Orchid module is slim and long, allowing the PCIe 6 signal to travel from the midplane to the CX-9 NICs at the front of the chassis.
Context After
Midplane

② Atomic Claim
Each Orchid module houses one E1.S module slot.
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "E1S_SLOT",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/NVIDIA Orchid Board",
"label": "Orchid Module"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "Each Orchid module houses one E1.S module slot."
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | Orchid Module | 04_knowledge_base/NVIDIA Orchid Board |
⑤ V2 Draft(需要修正時直接編輯)
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR,再手動執行 Repair Preview。
執行腳本前,Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
Each Orchid module houses one E1.S module slot.
V2 Semantic Frame Draft
{
"attribute": "E1S_SLOT",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/NVIDIA Orchid Board",
"label": "Orchid Module"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "Each Orchid module houses one E1.S module slot."
}
}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 才是正式決策。