VR2R-0084_r1

VR2R-0084

① SA Source

• Source: 開啟完整 SA 文章
• Section: Rubin
• Line hint: 71

Context Before

A notable omission from Rubin is the mention of Sparse FLOPs. In previous generations, 2:4 structured sparsity was used to double marketing FLOPs numbers. However, adoption was minimal especially at low precisions due to accuracy losses from the rigid sparsity structure forcing half of the values to be zero.

Evidence

Programmers basically ignored structured sparsity as it was not useful, which caused hardware designs to change as well.

Context After

Blackwell Ultra GB300 added 50% more dense FP4 while keeping sparse FP4 FLOPs the same, while AMD’s MI355X stopped supporting structured sparsity on MXFP8, MXFP6 and MXFP4 formats to save silicon area.

② Atomic Claim

Programmers 基本上忽略 structured sparsity，因為它實用性不足，而這也促使 hardware design 隨之改變。

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "attribute": "PROGRAMMER_ADOPTION_AND_HARDWARE_EFFECT",
  "context_nodes": [],
  "entity": {
    "id": "04_knowledge_base/Sparsity",
    "label": "structured sparsity"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": "because it was not useful",
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [],
    "value_text": "programmers 幾乎不採用，並促使 hardware design 改變。"
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
entity	structured sparsity	Sparsity

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