VR2-0183

① SA Source

Context Before

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

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 .

Evidence

narrowing the cost gap between a GDDR-based CPX and lower-spec HBM configurations

Context After

Compute Tray Redesign

One of the major changes with VR NVL72 is within the compute tray. This redesign of the compute tray is centered around simplifying assembly, namely eliminating cables from the compute tray as cables have been the major point of failure of GB200/300 assembly. As Jensen put it at CES 2026, the cableless design reduces the compute tray assembly time from 2 hours to 5 minutes. To achieve this, the VR NVL72 compute tray adopts a modular design with the modules connecting to each via board-to-board connectors.

② Atomic Claim

HBM premium 收斂,使 GDDR-based CPX 與 lower-spec HBM configuration 之間的成本差距縮小。

  • Epistemic Mode: ASSERTED
  • Mapping Status: COMPLETE

③ Semantic Frame

{
  "comparison_expression": "HBM premium 收斂,使 GDDR-based CPX 與 lower-spec HBM configuration 之間的成本差距縮小。",
  "entities": [
    {
      "id": "04_knowledge_base/HBM",
      "label": "HBM"
    },
    {
      "id": "04_knowledge_base/GDDR",
      "label": "GDDR"
    },
    {
      "id": "04_knowledge_base/CPX High-Density Interconnect Paradigm",
      "label": "CPX"
    }
  ],
  "frame_type": "COMPARISON",
  "metric": "COST",
  "operator": "COMPARES_WITH",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  }
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
comparison_entity_0HBMHBM
comparison_entity_1GDDRGDDR
comparison_entity_2CPX04_knowledge_base/CPX High-Density Interconnect Paradigm

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