SA260324R-0261::RESEG01

回到這篇 SA Coverage

① SA Source

Context Before

image

Source: SemiAnalysis

Evidence

All current evidence in the supply chain points to NVSwitch 7 being the same bandwidth as NVSwitch 6, but that is seems a bit illogical to be frank. Our belief is that NVSwitch 7 is actually 2x the bandwidth and radix of NVSwitch 6, so all-to-all can be done, and architecturally that makes the most sense from a systems perspective.

Context After

Rubin Ultra NVL576

To push the scale up world size beyond 144 GPUs and across multiple racks, optics are needed as we are approaching the maximum compute density that is within the reach of copper. Rubin Ultra NVL576 is now on the roadmap with 8 racks of lower density Oberon.

② Atomic Claim

SemiAnalysis 判斷 NVSwitch 7 的 radix 可能是 NVSwitch 6 的 2 倍。

  • Epistemic Mode: INFERRED
  • Mapping Status: CLAIM_ONLY

③ Semantic Frame

{
  "frame_type": "CLAIM_ONLY",
  "qualifiers": {
    "condition_text": "SemiAnalysis belief",
    "numeric_mentions": [
      "2x"
    ],
    "temporal_mentions": []
  },
  "reason": "NVSWITCH7_RADIX_ANALYST_BELIEF",
  "statement": "SemiAnalysis believes NVSwitch 7 may have twice the radix of NVSwitch 6."
}

④ 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

SemiAnalysis 判斷 NVSwitch 7 的 radix 可能是 NVSwitch 6 的 2 倍。

V2 Semantic Frame Draft

{
  "frame_type": "CLAIM_ONLY",
  "qualifiers": {
    "condition_text": "SemiAnalysis belief",
    "numeric_mentions": [
      "2x"
    ],
    "temporal_mentions": []
  },
  "reason": "NVSWITCH7_RADIX_ANALYST_BELIEF",
  "statement": "SemiAnalysis believes NVSwitch 7 may have twice the radix of NVSwitch 6."
}

V2 Revision Metadata Draft

{
  "epistemic_mode": "INFERRED",
  "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 才是正式決策。