VR2R-0163

① SA Source

Context Before

On a side note, VR NVL72 was initially known as VR NVL144 as Jensen math from GTC 2025 defined the number of GPU as the number of GPU compute die in system (with 2 compute dies per package and 72 Rubin packages per Oberon rack = 144 compute die).

Evidence

The naming was changed back to VR NVL72 to represent the 72 Rubin GPU packages in the system in late December.

Context After

This was right before CES 2026 where the naming was officially confirmed as VR NVL72.

② Atomic Claim

到 12 月下旬,命名改回 VR NVL72,以代表 system 內的 72 個 Rubin GPU packages。

  • Epistemic Mode: ASSERTED
  • Mapping Status: COMPLETE

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/VR NVL72",
        "label": "VR NVL72"
      },
      "role": "system"
    },
    {
      "node": {
        "id": "04_knowledge_base/Vera Rubin",
        "label": "Rubin"
      },
      "role": "platform"
    },
    {
      "node": {
        "id": "04_knowledge_base/GPU",
        "label": "GPU"
      },
      "role": "device"
    }
  ],
  "qualifiers": {
    "condition_text": "name reflects 72 Rubin GPU packages",
    "numeric_mentions": [
      "72"
    ],
    "temporal_mentions": [
      "late December"
    ]
  },
  "relation_type": "VR_NVL72_NAMING_BASIS"
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
systemVR NVL7204_knowledge_base/VR NVL72
platformRubin04_knowledge_base/Vera Rubin
deviceGPUGPU

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