clm_f66df9b007cd489bac043f36c4f632b1_r1

VR2R-0179::SPLIT02

回到這篇 SA Coverage

① SA Source

• Source: 開啟完整 SA 文章
• Section: CPX Form Factor
• Line hint: 245

Context Before

GDDR7 offers materially lower cost per GB and avoids the need for 2.5D packaging,

Evidence

However, Nvidia began exploring HBM-equipped variants for prefill, either via modified CPX configurations or through lower memory spec (such as using HBM3E) Rubin deployments dedicated to prefill, which we noted ↗ this way back in early December last year ↗ in our Accelerator & HBM model ↗.

Context After

We also think a lot this shift is driven by evolving memory economics. **Conventional DRAM pricing has risen sharply: **As DDR pricing increases, the relative premium of HBM compresses because pricing is more locked down in long term contracts, narrowing the cost gap between a GDDR-based CPX and lower-spec HBM configurations, therefore eliminating a lot of the cost benefits GDDR offers relative to performance. While memory bandwidth is not as important for pre-fill compare to decode, it is still necessary.

Compute Tray Redesign

② Atomic Claim

Nvidia began exploring lower-memory-spec Rubin deployments, such as HBM3E, dedicated to prefill.

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "attribute": "PREFILL_EXPLORATION",
  "context_nodes": [
    {
      "id": "04_knowledge_base/Vera Rubin",
      "label": "Rubin"
    },
    {
      "id": "04_knowledge_base/HBM3E",
      "label": "HBM3E"
    },
    {
      "id": "04_knowledge_base/Prefill",
      "label": "prefill"
    }
  ],
  "entity": {
    "id": "02_companies/NVDA",
    "label": "Nvidia"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [],
    "value_text": "Nvidia began exploring lower-memory-spec Rubin deployments, such as HBM3E, dedicated to prefill."
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
entity	Nvidia	NVDA
context_0	Rubin	04_knowledge_base/Vera Rubin
context_1	HBM3E	HBM3E
context_2	prefill	Prefill

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

Inline repair

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

V2 Atomic Claim Draft

Nvidia began exploring lower-memory-spec Rubin deployments, such as HBM3E, dedicated to prefill.

V2 Semantic Frame Draft

{
  "attribute": "PREFILL_EXPLORATION",
  "context_nodes": [
    {
      "id": "04_knowledge_base/Vera Rubin",
      "label": "Rubin"
    },
    {
      "id": "04_knowledge_base/HBM3E",
      "label": "HBM3E"
    },
    {
      "id": "04_knowledge_base/Prefill",
      "label": "prefill"
    }
  ],
  "entity": {
    "id": "02_companies/NVDA",
    "label": "Nvidia"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [],
    "value_text": "Nvidia began exploring lower-memory-spec Rubin deployments, such as HBM3E, dedicated to prefill."
  }
}

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