clm_ed154c9b3f594a2c84f58a841982f089_r2

VR2R-0058

回到這篇 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

Rubin architecture prioritizes bandwidth and low-precision compute.

• Epistemic Mode: ASSERTED
• Mapping Status: PARTIAL

③ Semantic Frame

{
  "frame_type": "CLAIM_ONLY",
  "qualifiers": {
    "condition_text": "architecture 指涉前文 Rubin，但此 atomic claim 未明示主詞",
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "reason": "ARCHITECTURE_SUBJECT_IMPLICIT_IN_EXTRACTION",
  "statement": "Rubin architecture prioritizes bandwidth and low-precision compute."
}

④ 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

Rubin architecture prioritizes bandwidth and low-precision compute.

V2 Semantic Frame Draft

{
  "frame_type": "CLAIM_ONLY",
  "qualifiers": {
    "condition_text": "architecture 指涉前文 Rubin，但此 atomic claim 未明示主詞",
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "reason": "ARCHITECTURE_SUBJECT_IMPLICIT_IN_EXTRACTION",
  "statement": "Rubin architecture prioritizes bandwidth and low-precision compute."
}

V2 Revision Metadata Draft

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

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