VR2R-0086

① SA Source

Context Before

Blackwell Ultra GB300 added 50% more dense FP4 while

Evidence

keeping sparse FP4 FLOPs the same, while AMD’s MI355X stopped supporting structured sparsity on MXFP8, MXFP6

Context After

and MXFP4 formats to save silicon area.

② Atomic Claim

……sparse FP4 FLOPs 維持不變;另一方面,AMD 的 MI355X 已停止在 MXFP8 與 MXFP6 上支援 structured sparsity……

  • Epistemic Mode: ASSERTED
  • Mapping Status: PARTIAL

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "02_companies/AMD",
        "label": "AMD"
      },
      "role": "vendor"
    },
    {
      "node": {
        "id": "04_knowledge_base/MI355X",
        "label": "MI355X"
      },
      "role": "product"
    },
    {
      "node": {
        "id": "04_knowledge_base/MXFP8",
        "label": "MXFP8"
      },
      "role": "format"
    },
    {
      "node": {
        "id": "04_knowledge_base/MXFP6",
        "label": "MXFP6"
      },
      "role": "format"
    },
    {
      "node": {
        "id": "04_knowledge_base/Sparsity",
        "label": "structured sparsity"
      },
      "role": "feature"
    },
    {
      "node": {
        "id": "04_knowledge_base/FP4",
        "label": "FP4"
      },
      "role": "precision"
    }
  ],
  "qualifiers": {
    "condition_text": "句子由 VR2R-0085 延續,且下一 claim 再補 MXFP4",
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "relation_type": "STRUCTURED_SPARSITY_SUPPORT_CHANGE"
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
vendorAMDAMD
productMI355XMI355X
formatMXFP8MXFP8
formatMXFP6MXFP6
featurestructured sparsitySparsity
precisionFP4FP4

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