SA260324R-0282_r1

SA260324R-0282

① SA Source

• Source: 開啟完整 SA 文章
• Section: Vera ETL256
• Line hint: 354

Context Before

The Vera standalone rack addresses this directly, achieving unprecedented density by fitting 256 CPUs into a single rack — a feat that necessitates liquid cooling. The underlying rationale mirrors the NVL rack design philosophy: pack compute tightly enough that copper interconnects can reach everything within the rack, eliminating the need for optical transceivers on the spine. The cost savings from copper more than offset the additional cooling overhead.

Evidence

Each Vera ETL rack consists of 32 compute trays, 16 above

Context After

and 16 below, arranged symmetrically around four 1U MGX ETL switch trays (based on Spectrum-6) in the middle. The symmetric split is deliberate: it minimizes cable length variance between compute trays and the spine, keeping all connections within copper reach. From each switch tray, rear-facing ports connect to that copper spine for intra-rack communication, while 32 front-facing OSFP cages provide optical connectivity to the rest of the POD.

② Atomic Claim

每個 Vera ETL rack 由 32 個 compute trays 組成，其中 16 個位於上方……

• Epistemic Mode: ASSERTED
• Mapping Status: PARTIAL

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/Vera ETL256",
        "label": "Vera ETL rack"
      },
      "role": "rack"
    },
    {
      "node": {
        "id": "04_knowledge_base/Compute Tray",
        "label": "compute tray"
      },
      "role": "component"
    }
  ],
  "qualifiers": {
    "condition_text": "extraction fragment continues in next claim",
    "numeric_mentions": [
      "32",
      "16"
    ],
    "temporal_mentions": []
  },
  "relation_type": "VERA_ETL_RACK_COMPUTE_TRAY_COUNT"
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
rack	Vera ETL rack	04_knowledge_base/Vera ETL256
component	compute tray	04_knowledge_base/Compute Tray

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