VR2R-0175

回到這篇 SA Coverage

① SA Source

Context Before

Rubin CPX was originally architected as a GDDR7-based accelerator optimized for prefill, based on three key considerations:

Evidence

Prefill is primarily FLOPs-limited, not bandwidth-limited, making HBM less indispensable.

Context After

HBM’s increased bandwidth is structurally underutilized in prefill.

② Atomic Claim

Prefill 主要受 FLOPs 限制,而不是 bandwidth 限制,因此 HBM 的不可替代性較低。

  • Epistemic Mode: ASSERTED
  • Mapping Status: COMPLETE

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/Prefill",
        "label": "Prefill"
      },
      "role": "workload"
    },
    {
      "node": {
        "id": "04_knowledge_base/HBM",
        "label": "HBM"
      },
      "role": "memory"
    }
  ],
  "qualifiers": {
    "condition_text": "prefill primarily FLOPs-limited rather than bandwidth-limited",
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "relation_type": "PREFILL_RESOURCE_BOUND_AND_HBM_DEPENDENCY"
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
workloadPrefillPrefill
memoryHBMHBM

⑤ V2 Draft(需要修正時直接編輯)

Inline repair

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

V2 Atomic Claim Draft

Prefill 主要受 FLOPs 限制,而不是 bandwidth 限制,因此 HBM 的不可替代性較低。

V2 Semantic Frame Draft

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/Prefill",
        "label": "Prefill"
      },
      "role": "workload"
    },
    {
      "node": {
        "id": "04_knowledge_base/HBM",
        "label": "HBM"
      },
      "role": "memory"
    }
  ],
  "qualifiers": {
    "condition_text": "prefill primarily FLOPs-limited rather than bandwidth-limited",
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "relation_type": "PREFILL_RESOURCE_BOUND_AND_HBM_DEPENDENCY"
}

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