VR2R-0056::SPLIT03
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Extreme Co-design: 6 Silicon Product Offerings under the Rubin Platform - Chip Floorplans & Specifications - Line hint:
85
Context Before
Source: SemiAnalysis, Nvidia
Evidence
Rubin’s dense FP4 and FP8 FLOPs increase by roughly ~3.5× versus GB200, while FP16 FLOPs rise by a more modest ~1.6x, underscoring NVIDIA’s continued emphasis on FP4/FP8 as the primary scaling vector. On the memory side, HBM capacity remains flat from GB300, while HBM bandwidth scales more aggressively at ~2.8x. Overall, the architecture prioritizes bandwidth and low-precision compute.
Context After
Source: SemiAnalysis, Nvidia
② Atomic Claim
SemiAnalysis 認為，這些 scaling differences 顯示 NVIDIA 持續將 FP4／FP8 作為主要 scaling vector。
- Epistemic Mode:
INFERRED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "02_companies/NVDA",
"label": "NVIDIA"
},
"role": "subject"
},
{
"node": {
"id": "04_knowledge_base/FP4",
"label": "FP4"
},
"role": "scaling_vector"
},
{
"node": {
"id": "04_knowledge_base/FP8",
"label": "FP8"
},
"role": "scaling_vector"
}
],
"qualifiers": {
"condition_text": "inferred from the relative FLOPS scaling described in the source",
"numeric_mentions": [],
"temporal_mentions": []
},
"relation_type": "PRIMARY_SCALING_VECTOR_INTERPRETATION"
}④ Canonical Entity Mapping
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
SemiAnalysis 認為，這些 scaling differences 顯示 NVIDIA 持續將 FP4／FP8 作為主要 scaling vector。
V2 Semantic Frame Draft
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "02_companies/NVDA",
"label": "NVIDIA"
},
"role": "subject"
},
{
"node": {
"id": "04_knowledge_base/FP4",
"label": "FP4"
},
"role": "scaling_vector"
},
{
"node": {
"id": "04_knowledge_base/FP8",
"label": "FP8"
},
"role": "scaling_vector"
}
],
"qualifiers": {
"condition_text": "inferred from the relative FLOPS scaling described in the source",
"numeric_mentions": [],
"temporal_mentions": []
},
"relation_type": "PRIMARY_SCALING_VECTOR_INTERPRETATION"
}V2 Revision Metadata Draft
{
"epistemic_mode": "INFERRED",
"mapping_status": "COMPLETE"
}⑥ 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 才是正式決策。