clm_f5766a1c03c847c6b949b618c29be486_r1

VR2R-0560::RESEG02

回到這篇 SA Coverage

① SA Source

• Source: 開啟完整 SA 文章
• Section: GB200 Hardware Architecture - Component Supply Chain & BOM
• Line hint: 711

Context Before

Source: Nvidia VR NVL72 Component BoM and Power Budget Model ↗

Evidence

The diagram below shows how the NVLink 6 signal traverses through the tray. Each of the green lines represents nine 400G logical ports of NVLink 6, or 18 TX/RX lanes of 200G. Because there is only 1 DP per lane using bidirectional SerDes, there are a total of 18 DPs between any connector and any switch for a total of 72 DPs per connector, which is the same as prior generation of NVLink 5 Switch Tray.

Context After

Source: Nvidia VR NVL72 Component BoM and Power Budget Model ↗

② Atomic Claim

每個 connector 的 72 個 differential pairs（DPs）與前代 NVLink 5 Switch Tray 相同。

• Epistemic Mode: ASSERTED
• Mapping Status: CLAIM_ONLY

③ Semantic Frame

{
  "frame_type": "CLAIM_ONLY",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "72 DPs"
    ],
    "temporal_mentions": []
  },
  "reason": "PER_CONNECTOR_DP_COUNT_UNCHANGED_VS_NVLINK5",
  "statement": "The 72 differential pairs per connector are the same as in the prior-generation NVLink 5 Switch Tray."
}

④ Canonical Entity Mapping

• 此 CLAIM_ONLY revision 沒有 canonical Entity mapping。

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

Inline repair

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

V2 Atomic Claim Draft

每個 connector 的 72 個 differential pairs（DPs）與前代 NVLink 5 Switch Tray 相同。

V2 Semantic Frame Draft

{
  "frame_type": "CLAIM_ONLY",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "72 DPs"
    ],
    "temporal_mentions": []
  },
  "reason": "PER_CONNECTOR_DP_COUNT_UNCHANGED_VS_NVLINK5",
  "statement": "The 72 differential pairs per connector are the same as in the prior-generation NVLink 5 Switch Tray."
}

V2 Revision Metadata Draft

{
  "epistemic_mode": "ASSERTED",
  "mapping_status": "CLAIM_ONLY"
}

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