VR2-0174

① SA Source

Context Before

VR NVL72 CPX (Dual Rack): Rubin CPX deployed in a separate rack alongside the VR NVL72 rack

The standalone/dedicated rack direction materially changes the deployment calculus. A dual-rack approach allows hyperscalers to scale prefill and decode capacity independently, optimize datacenter power envelopes, and reduce system-level failure domains versus tightly coupled trays. More importantly, it formalizes architectural disaggregation between inference prefill (compute-bound) and decode (bandwidth-bound).

Evidence

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

Context After

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

② Atomic Claim

Rubin CPX 原先被設計成以 GDDR7 為基礎、針對 prefill 最佳化的 accelerator,主要基於三項考量。

  • Epistemic Mode: ASSERTED
  • Mapping Status: COMPLETE

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/CPX High-Density Interconnect Paradigm",
        "label": "CPX"
      },
      "role": "endpoint_or_system"
    },
    {
      "node": {
        "id": "04_knowledge_base/GDDR7",
        "label": "GDDR7"
      },
      "role": "connected_entity"
    },
    {
      "node": {
        "id": "04_knowledge_base/Prefill",
        "label": "prefill"
      },
      "role": "connected_entity"
    },
    {
      "node": {
        "id": "04_knowledge_base/Vera Rubin",
        "label": "Rubin"
      },
      "role": "context_entity"
    }
  ],
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "relation_type": "CONNECTS_TO"
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
endpoint_or_systemCPX04_knowledge_base/CPX High-Density Interconnect Paradigm
connected_entityGDDR7GDDR7
connected_entityprefillPrefill
context_entityRubin04_knowledge_base/Vera Rubin

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