SA260324R-0226::SPLIT01
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Oberon and Kyber Updates, Larger World Sizes Introduced, More Networking Updates - Line hint:
277
Context Before
Source: SemiAnalysis
Evidence
Each switch blade is also double in height vs the GTC 2025 prototype, with 6 NVLink 7 switches per switch blade, and 12 switch blades per rack, amounting to a total of 72 NVLink 7 switches per Kyber rack. The GPUs are connected all-to-all to the switch blades via 2 PCB midplanes or 1 midplane per canister.
Context After
Kyber midplane PCB (GPU side). Source: Nvidia, SemiAnalysis
② Atomic Claim
Kyber 的每個 switch blade 高度比 GTC 2025 prototype 增加一倍。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "SWITCH_BLADE_HEIGHT_VS_GTC_2025_PROTOTYPE",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/NVIDIA Kyber Rack",
"label": "Kyber"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [
"2"
],
"temporal_mentions": [
"GTC 2025"
]
},
"value": {
"numeric_mentions": [
"2"
],
"value_text": "2x height"
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | Kyber | 04_knowledge_base/NVIDIA Kyber Rack |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
Kyber 的每個 switch blade 高度比 GTC 2025 prototype 增加一倍。
V2 Semantic Frame Draft
{
"attribute": "SWITCH_BLADE_HEIGHT_VS_GTC_2025_PROTOTYPE",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/NVIDIA Kyber Rack",
"label": "Kyber"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [
"2"
],
"temporal_mentions": [
"GTC 2025"
]
},
"value": {
"numeric_mentions": [
"2"
],
"value_text": "2x height"
}
}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 才是正式決策。