SA260324R-0379
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Mid-board Optics – Nvidia’s War on Pluggables - Line hint:
465
Context Before
4 MPO ports on the left, rather than OSFP cages. Source: Nvidia, SemiAnalysis
Evidence
The use of MBOM would block the use of any form of pluggable transceiver or AEC, and naturally hyperscalers are saying “CP-Hell No” to that idea and are continuing to push for an OSFP cage so they can continue using pluggables.
Context After
It is important to point out that many aspects of the Kyber design are still in flux and there could still be a number of design changes before Kyber racks are actually deployed. After all – the change from the four canister design to a two compute tray canister + one switch blade bank is already a huge change.
② Atomic Claim
Hyperscaler 對 MBOM 方案明顯反對，並持續要求保留 OSFP cage，以便繼續使用 pluggable。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Hyperscaler",
"label": "Hyperscaler"
},
"role": "customer"
},
{
"node": {
"id": "04_knowledge_base/OSFP (Octal Small Form-factor Pluggable)",
"label": "OSFP"
},
"role": "preferred_interface"
},
{
"node": {
"id": "04_knowledge_base/Pluggable transceiver",
"label": "pluggable transceiver"
},
"role": "preferred_module"
},
{
"node": {
"id": "04_knowledge_base/光模塊",
"label": "MBOM"
},
"role": "rejected_option"
}
],
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"relation_type": "HYPERSCALERS_PREFER_OSFP_FOR_PLUGGABLES_OVER_MBOM"
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| customer | Hyperscaler | Hyperscaler |
| preferred_interface | OSFP | 04_knowledge_base/OSFP (Octal Small Form-factor Pluggable) |
| preferred_module | pluggable transceiver | 04_knowledge_base/Pluggable transceiver |
| rejected_option | MBOM | 04_knowledge_base/光模塊 |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
Hyperscaler 對 MBOM 方案明顯反對，並持續要求保留 OSFP cage，以便繼續使用 pluggable。
V2 Semantic Frame Draft
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Hyperscaler",
"label": "Hyperscaler"
},
"role": "customer"
},
{
"node": {
"id": "04_knowledge_base/OSFP (Octal Small Form-factor Pluggable)",
"label": "OSFP"
},
"role": "preferred_interface"
},
{
"node": {
"id": "04_knowledge_base/Pluggable transceiver",
"label": "pluggable transceiver"
},
"role": "preferred_module"
},
{
"node": {
"id": "04_knowledge_base/光模塊",
"label": "MBOM"
},
"role": "rejected_option"
}
],
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"relation_type": "HYPERSCALERS_PREFER_OSFP_FOR_PLUGGABLES_OVER_MBOM"
}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 才是正式決策。