clm_f5feead6fe534a4e8306ced392ceb9b7_r1

VR2R-0669::SPLIT02

回到這篇 SA Coverage

① SA Source

• Source: 開啟完整 SA 文章
• Section: Customization
• Line hint: 903

Context Before

Hyperscaler Customization and Assembly Logistics

Customization

Evidence

For GB300, although the reference design has four ConnectX-8 NICs for the backend network and one Bluefield-3 for frontend network, most hyperscalers have their own design and alternative networking configurations, especially for Bluefield-3. Beside networking configuration, the power delivery modules, the local NVMe storage, and the management module are also highly customized and differentiated across customers.

Context After

For example, for some racks, even Amazon is deploying ConnectX-8 in GB300s in many cases. Also, most hyperscalers are deploying their in-house DPU instead of Bluefield-3 for frontend networking. The power delivery module and management modules in GB300 are also highly customized as every customer has differing preferences for these modules. As such, the front half of GB300 is highly customizable with each hyperscalers’ design differing from each other significantly.

② Atomic Claim

Most hyperscalers have their own GB300 networking configurations, especially alternatives to BlueField-3.

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "attribute": "HYPERSCALER_CUSTOMIZATION",
  "context_nodes": [
    {
      "id": "04_knowledge_base/Hyperscaler",
      "label": "hyperscalers"
    },
    {
      "id": "04_knowledge_base/BlueField-3",
      "label": "BlueField-3"
    }
  ],
  "entity": {
    "id": "04_knowledge_base/GB300",
    "label": "GB300"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [],
    "value_text": "Most hyperscalers have their own GB300 networking configurations, especially alternatives to BlueField-3."
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
entity	GB300	GB300
context_0	hyperscalers	Hyperscaler
context_1	BlueField-3	BlueField-3

⑤ V2 Draft（需要修正時直接編輯）

Inline repair

只編輯以下三個 Draft 區塊。完成後將 review_action 設為 REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。

V2 Atomic Claim Draft

Most hyperscalers have their own GB300 networking configurations, especially alternatives to BlueField-3.

V2 Semantic Frame Draft

{
  "attribute": "HYPERSCALER_CUSTOMIZATION",
  "context_nodes": [
    {
      "id": "04_knowledge_base/Hyperscaler",
      "label": "hyperscalers"
    },
    {
      "id": "04_knowledge_base/BlueField-3",
      "label": "BlueField-3"
    }
  ],
  "entity": {
    "id": "04_knowledge_base/GB300",
    "label": "GB300"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [],
    "value_text": "Most hyperscalers have their own GB300 networking configurations, especially alternatives to BlueField-3."
  }
}

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