VR2R-0171::RESEG02
① SA Source
- Source: 開啟完整 SA 文章
- Section:
CPX Form Factor - Line hint:
229
Context Before
VR NVL72 CPX (Dual Rack): Rubin CPX deployed in a separate rack alongside the VR NVL72 rack
Evidence
The standalone/dedicated rack direction materially changes the deployment calculus. A dual-rack approach allows hyperscalers to scale prefill and decode capacity independently, optimize datacenter power envelopes, and reduce system-level failure domains versus tightly coupled trays. More importantly, it formalizes architectural disaggregation between inference prefill (compute-bound) and decode (bandwidth-bound).
Context After
Rubin CPX was originally architected as a GDDR7-based accelerator optimized for prefill, based on three key considerations:
② Atomic Claim
Dual-rack approach 可最佳化 datacenter power envelope。
- Epistemic Mode:
ASSERTED - Mapping Status:
CLAIM_ONLY
③ Semantic Frame
{
"frame_type": "CLAIM_ONLY",
"qualifiers": {
"condition_text": "dual-rack approach",
"numeric_mentions": [],
"temporal_mentions": []
},
"reason": "DATACENTER_POWER_ENVELOPE_NOT_CANONICALIZED",
"statement": "Dual-rack approach can optimize datacenter power envelopes."
}④ Canonical Entity Mapping
- 此
CLAIM_ONLYrevision 沒有 canonical Entity mapping。
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
Dual-rack approach 可最佳化 datacenter power envelope。
V2 Semantic Frame Draft
{
"frame_type": "CLAIM_ONLY",
"qualifiers": {
"condition_text": "dual-rack approach",
"numeric_mentions": [],
"temporal_mentions": []
},
"reason": "DATACENTER_POWER_ENVELOPE_NOT_CANONICALIZED",
"statement": "Dual-rack approach can optimize datacenter power envelopes."
}V2 Revision Metadata Draft
{
"epistemic_mode": "ASSERTED",
"mapping_status": "CLAIM_ONLY"
}⑥ 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 才是正式決策。