VR2R-0528
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Bi-directional SerDes for Scale-Up - Line hint:
657
Context Before
This gives rise to the engineering problem of ensuring that a clean signal can be received at either end of the wire because two signals sent in opposite directions over the same copper wire will superpose to form a composite signal that is different from the intended transmitting signal.
In optics, bidirectional interconnect can be achieved by integrating an optical circulator to a transceiver as discussed in our TPUv7 article ↗ published late last year. The circulator works by routing the inbound and outbound signal onto separate paths ↗, ensuring no overlaps between both at the photodiode receiver. Bidirectional interconnect is, however, much trickier in the copper domain. A circulator cannot be used as copper cables are linear transmission lines, which means that the inbound and outbound signals will be summed at the receiver through superposition. The receiver at each end of the copper wire therefore needs a mechanism to separate the local TX from the local RX.
Evidence
The solution to this problem is the use of a hybrid at each end of the wire. Without a hybrid, there will be self-interference at the local RX because both the local TX and local RX are being transmitted along the same wire:
Context After
B0+A0=BA0
An inverted copy of the local TX must therefore be generated at the local RX for proper echo cancellation:
② Atomic Claim
The described simultaneous bidirectional copper link uses a hybrid at each end of the wire to suppress self-interference.
- Epistemic Mode:
ASSERTED - Mapping Status:
PARTIAL
③ Semantic Frame
{
"frame_type": "CLAIM_ONLY",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"reason": "HYBRID_CIRCUIT_NOT_CANONICALIZED_IN_SOURCE_CLAIM",
"statement": "The described simultaneous bidirectional copper link uses a hybrid at each end of the wire to suppress self-interference."
}④ 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
The described simultaneous bidirectional copper link uses a hybrid at each end of the wire to suppress self-interference.
V2 Semantic Frame Draft
{
"frame_type": "CLAIM_ONLY",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"reason": "HYBRID_CIRCUIT_NOT_CANONICALIZED_IN_SOURCE_CLAIM",
"statement": "The described simultaneous bidirectional copper link uses a hybrid at each end of the wire to suppress self-interference."
}V2 Revision Metadata Draft
{
"epistemic_mode": "ASSERTED",
"mapping_status": "PARTIAL"
}⑥ 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 才是正式決策。