NIEK2-0357
① SA Source
- Source: 開啟完整 SA 文章
- Section:
FIT Joining the Party - Line hint:
445
Context Before
For the Vera Rubin Ultra NVL288 System that we discussed above, we would say the cable backplane return for Kyber. If Rubin Ultra is deployed in such a form factor – each of the Rubin Ultra GPUs will have a scale-up bandwidth of 14.4Tbit/s uni-di, requiring 144 DPs of cables to connect to the NVSwitches. 144 DPs times 288 GPUs means a total of 41,472 DPs to connect this larger world size domain. This is a lot of cables, so it is more of an upper bound of how much cable content could be used here. If there is oversubscription or if the inter-rack connection is made through the switches – it is possible fewer DPs would be needed.
FIT Joining the Party
Evidence
Backplane cable cartridge and Paladin connector demand is so strong that Amphenol cannot keep up with supply
Context After
Kyber Voronoi – Another FIT Win?
The Kyber midplane will utilize many 8×19 DP connectors to interface with the compute trays at the front of the rack, and to the switch blades in the back of the rack.
② Atomic Claim
Backplane cable cartridge 與 Paladin connector 需求強到 Amphenol 已無法單獨滿足供應。
- Epistemic Mode:
ASSERTED - Mapping Status:
PARTIAL
③ Semantic Frame
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Backplane",
"label": "Backplane"
},
"role": "supplier"
},
{
"node": {
"id": "04_knowledge_base/Paladin connector",
"label": "Paladin connector"
},
"role": "supplied_item_or_application"
},
{
"node": {
"id": "02_companies/APH",
"label": "Amphenol"
},
"role": "context"
}
],
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"relation_type": "SUPPLIES"
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| supplier | Backplane | Backplane |
| supplied_item_or_application | Paladin connector | 04_knowledge_base/Paladin connector |
| context | Amphenol | APH |
⑤ 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 才是正式決策。