SA260324R-0081_r1

SA260324R-0081

① SA Source

• Source: 開啟完整 SA 文章
• Section: SRAM and Memory Hierarchy
• Line hint: 87

Context Before

One of the benefits of relying on SF4 is that it isn’t constrained like TSMC’s N3, which is putting a cap on accelerator production and is a key reason why the industry remains compute constrained. This is in addition to not having HBM which is also constrained.

Evidence

This allows Nvidia to ramp production of the LPU without sacrificing or eating into their valuable TSMC allocation or HBM allocations, representing true incremental revenue

Context After

and capacity that noone else can access.

② Atomic Claim

這讓 Nvidia 可以擴大 LPU 產量，而不必犧牲或侵蝕珍貴的 TSMC 產能配額與 HBM 配額，因此形成真正的 incremental revenue。

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "02_companies/NVDA",
        "label": "Nvidia"
      },
      "role": "company"
    },
    {
      "node": {
        "id": "04_knowledge_base/Groq LPU",
        "label": "LPU"
      },
      "role": "product"
    },
    {
      "node": {
        "id": "02_companies/2330 台積電",
        "label": "TSMC"
      },
      "role": "foundry_allocation"
    },
    {
      "node": {
        "id": "04_knowledge_base/HBM",
        "label": "HBM"
      },
      "role": "memory_allocation"
    }
  ],
  "qualifiers": {
    "condition_text": "ramp LPU production without sacrificing TSMC or HBM allocations；represents incremental revenue",
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "relation_type": "INCREMENTAL_LPU_CAPACITY_WITHOUT_CORE_ALLOCATION_CANNIBALIZATION"
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
company	Nvidia	NVDA
product	LPU	04_knowledge_base/Groq LPU
foundry_allocation	TSMC	02_companies/2330 台積電
memory_allocation	HBM	HBM

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