SA260324R-0241_r1

SA260324R-0241

① SA Source

• Source: 開啟完整 SA 文章
• Section: Oberon and Kyber Updates, Larger World Sizes Introduced, More Networking Updates
• Line hint: 304

Context Before

In the Kyber Switch Blade picture below, we can see that there are 2 separate PCBs carrying 3 Switches each. The switch blade should have 6 152DP connectors, 3 connectors serving each midplane board. The picture is a prototype blade using less dense connectors, which is why there are 12 connectors instead of the 6 that we expect in the production version.

Evidence

Each 28.8T NVLink Switch has 144 lanes of 200G (simultaneous bi-directional) which means each Switch has 24 lanes of 200G going to each connector.

Context After

Copper flyover cables are used to connect each switch to the midplane, as the distances involved are too long for PCB traces. This is also why the switches are further away from the midplane, to provide space for the routing of the flyover cables.

② Atomic Claim

每顆 28.8T NVLink Switch 有 144 lanes 的 200G simultaneous bi-directional link，因此每顆 switch 會有 24 lanes 的 200G 連到每個 connector。

• Epistemic Mode: ASSERTED
• Mapping Status: PARTIAL

③ Semantic Frame

{
  "attribute": "LANE_CONFIGURATION",
  "context_nodes": [
    {
      "id": "04_knowledge_base/200G",
      "label": "200G"
    }
  ],
  "entity": {
    "id": "04_knowledge_base/NVSwitch",
    "label": "NVLink Switch"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": "connector 沒有 canonical entity",
    "numeric_mentions": [
      "28.8T",
      "144",
      "200G",
      "24"
    ],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [
      "28.8T",
      "144",
      "200G",
      "24"
    ],
    "value_text": "144 lanes × 200G simultaneous bi-directional；每個 connector 對應 24 lanes × 200G。"
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
entity	NVLink Switch	NVSwitch
context_node	200G	200G

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