SA260324R-0350_r1

SA260324R-0350

① SA Source

• Source: 開啟完整 SA 文章
• Section: NVL288 System
• Line hint: 448

Context Before

Evidence

For the Vera Rubin Ultra NVL288 System that we discussed above, we would say the cable backplane return for Kyber.

Context After

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.

② Atomic Claim

對前述 Vera Rubin Ultra NVL288 system，SemiAnalysis 認為 Kyber 會重新採用 cable backplane。

• Epistemic Mode: ASSERTED
• Mapping Status: PARTIAL

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/Rubin Ultra",
        "label": "Rubin Ultra"
      },
      "role": "platform"
    },
    {
      "node": {
        "id": "04_knowledge_base/NVL288",
        "label": "NVL288"
      },
      "role": "system"
    },
    {
      "node": {
        "id": "04_knowledge_base/NVIDIA Kyber Rack",
        "label": "Kyber"
      },
      "role": "rack"
    },
    {
      "node": {
        "id": "04_knowledge_base/Backplane",
        "label": "cable backplane"
      },
      "role": "backplane"
    }
  ],
  "qualifiers": {
    "condition_text": "SemiAnalysis analyst statement",
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "relation_type": "CABLE_BACKPLANE_RETURNS_FOR_KYBER_NVL288"
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
platform	Rubin Ultra	04_knowledge_base/Rubin Ultra
system	NVL288	NVL288
rack	Kyber	04_knowledge_base/NVIDIA Kyber Rack
backplane	cable backplane	Backplane

⑤ 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 才是正式決策。