SA260324R-0361_r1

SA260324R-0361

① SA Source

• Source: 開啟完整 SA 文章
• Section: Kyber Voronoi - Another FIT Win?
• Line hint: 458

Context Before

For Kyber, Nvidia is now in the driver’s seat when it comes to IP and

Evidence

they have designed a proprietary connector spec named Voronoi, so it will no longer be the Amphenol Paladin connector.

Context After

There are three vendors bidding for the project: FIT, Molex and Amphenol. FIT appears to be leading the market for these connectors, but Amphenol is reportedly also working together closely with FIT to manufacture the connectors. The design and implementation of Voronoi remains in flux, but both FIT and Amphenol will need to ramp significant production volume with the specification licensed from Nvidia.

② Atomic Claim

Nvidia 設計了名為 Voronoi 的 proprietary connector spec，因此不再沿用 Amphenol 的 Paladin connector。

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "02_companies/NVDA",
        "label": "Nvidia"
      },
      "role": "designer"
    },
    {
      "node": {
        "id": "04_knowledge_base/Voronoi connector",
        "label": "Voronoi"
      },
      "role": "new_connector"
    },
    {
      "node": {
        "id": "02_companies/APH",
        "label": "Amphenol"
      },
      "role": "incumbent_supplier"
    },
    {
      "node": {
        "id": "04_knowledge_base/Paladin connector",
        "label": "Paladin connector"
      },
      "role": "replaced_connector"
    }
  ],
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "relation_type": "VORONOI_REPLACES_PALADIN_SPEC"
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
designer	Nvidia	NVDA
new_connector	Voronoi	04_knowledge_base/Voronoi connector
incumbent_supplier	Amphenol	APH
replaced_connector	Paladin connector	04_knowledge_base/Paladin connector

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