clm_fa3abfb207cc4dc48e5e3ad87aef4911_r3

VR2-0047

回到這篇 SA Coverage

① SA Source

• Source: 開啟完整 SA 文章
• Section: Extreme Co-design: 6 Silicon Product Offerings under the Rubin Platform - Chip Floorplans & Specifications
• Line hint: 85

Context Before

Source: SemiAnalysis, Nvidia

Evidence

Rubin’s dense FP4 and FP8 FLOPs increase by roughly ~3.5× versus GB200, while FP16 FLOPs rise by a more modest ~1.6x, underscoring NVIDIA’s continued emphasis on FP4/FP8 as the primary scaling vector. On the memory side, HBM capacity remains flat from GB300, while HBM bandwidth scales more aggressively at ~2.8x. Overall, the architecture prioritizes bandwidth and low-precision compute.

Context After

Source: SemiAnalysis, Nvidia

② Atomic Claim

記憶體方面，HBM capacity 與 GB300 相同。

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "comparison_expression": "記憶體方面，HBM capacity 與 GB300 相同。",
  "entities": [
    {
      "id": "04_knowledge_base/HBM",
      "label": "HBM"
    },
    {
      "id": "04_knowledge_base/GB300",
      "label": "GB300"
    }
  ],
  "frame_type": "COMPARISON",
  "metric": "CAPACITY",
  "operator": "EQUAL_TO",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
comparison_entity_0	HBM	HBM
comparison_entity_1	GB300	GB300

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

Inline repair

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

V2 Atomic Claim Draft

記憶體方面，HBM capacity 與 GB300 相同。

V2 Semantic Frame Draft

{
  "comparison_expression": "記憶體方面，HBM capacity 與 GB300 相同。",
  "entities": [
    {
      "id": "04_knowledge_base/HBM",
      "label": "HBM"
    },
    {
      "id": "04_knowledge_base/GB300",
      "label": "GB300"
    }
  ],
  "frame_type": "COMPARISON",
  "metric": "CAPACITY",
  "operator": "EQUAL_TO",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  }
}

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