VR2R-0665
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Ethernet-Based Cluster Deployments - Line hint:
897
Context Before
Source: SemiAnalysis AI Networking Model ↗
The catch is that 102.4T Minipack-4 switches may not be shipped in time for Vera Rubin NVL72 rack deployments, and if this were to be the case, some NSF clusters will be shipped using 51.2T Minipack-3 switches instead. This means that gearboxes within the AECs will have to be used to convert 200G per lane SerDes speed at the NIC to 100G per lane SerDes speed at the switch.
Evidence
Meta will not be the only hyperscaler using 1.6T AECs for its VR200 deployments, however. We think xAI will use 1.6T AECs for both NIC-to-TOR and switch-to-switch connectivity at the leaf, spine and core layers. It will be a single-plane network replacing most 1.6T transceivers at the switch boxes – and this can give Credo plenty of pricing power.
Context After
Hyperscaler Customization and Assembly Logistics
Customization
② Atomic Claim
原文預期：Meta 不會是唯一在 VR200 deployments 採用 1.6T AEC 的 hyperscaler。
- Epistemic Mode:
EXPECTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "02_companies/META",
"label": "Meta"
},
"role": "operator"
},
{
"node": {
"id": "04_knowledge_base/Hyperscaler",
"label": "hyperscaler"
},
"role": "operator_type"
},
{
"node": {
"id": "04_knowledge_base/Active electrical cable",
"label": "AEC"
},
"role": "cable"
}
],
"qualifiers": {
"condition_text": "VR200 is plain text in source claim; Future VR200 1.6T AEC adoption beyond Meta",
"numeric_mentions": [
"1.6T"
],
"temporal_mentions": []
},
"relation_type": "HYPERSCALERS_USE_1P6T_AEC_FOR_VR200"
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| operator | Meta | META |
| operator_type | hyperscaler | Hyperscaler |
| cable | AEC | 04_knowledge_base/Active electrical cable |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
原文預期：Meta 不會是唯一在 VR200 deployments 採用 1.6T AEC 的 hyperscaler。
V2 Semantic Frame Draft
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "02_companies/META",
"label": "Meta"
},
"role": "operator"
},
{
"node": {
"id": "04_knowledge_base/Hyperscaler",
"label": "hyperscaler"
},
"role": "operator_type"
},
{
"node": {
"id": "04_knowledge_base/Active electrical cable",
"label": "AEC"
},
"role": "cable"
}
],
"qualifiers": {
"condition_text": "VR200 is plain text in source claim; Future VR200 1.6T AEC adoption beyond Meta",
"numeric_mentions": [
"1.6T"
],
"temporal_mentions": []
},
"relation_type": "HYPERSCALERS_USE_1P6T_AEC_FOR_VR200"
}V2 Revision Metadata Draft
{
"epistemic_mode": "EXPECTED",
"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 才是正式決策。