[Decision] sync-in warehouse drivers (epic #31763, ADR-0153 P3): who builds the Snowflake and BigQuery plugin drivers, and where #32066

triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

Filing gate: ④ coordination node. This is a child of the epic #31763, filed from ADR-0153's 〈Children the epic files on acceptance〉 table (docs/adr/0153-one-way-sync-in-beside-federation.md, merged in #32014). domain:spec#2 asked triage to file it (mailbox comment 6760065220). ⛔ Not a claim.
Business reason: inherited from #31763 (p1). Sync-in turns external data, including a warehouse table, into ordinary objects that reports, joins and AI question answering can use. Every gap it closes (G1–G9) was measured in #31778.
Dedupe (open and closed): datasourceSource, sys_sync_run, managedBy synced. Only #31763, #31778 and #31780 match, and none of them is this child. New.
Part of #31763.
Reader: the maintainer. Triage carries the answer.
class: c · type: Decision

维护者速读

要你定一件事： Snowflake 和 BigQuery 的数仓驱动谁来做、放在哪里。

• ADR-0153 的子卡表写明，这两个驱动不放在本仓（裁决 6731568115）。每个驱动是独立的插件包，用一致性测试套件里的窗口读取用例验证，各约 2–3 个 agent 日。
• ADR 原文：“Who builds them is the maintainer's call when this row is filed.” 这张卡就是这一步。
• 它们排在 P2 engine 之后，所以现在定下来不会挡住任何事。

选项：

• A（推荐）： 先只做一个驱动（按首个客户需要，Snowflake 或 BigQuery），放在一个新的独立仓。engine 落地后再立卡，归一个新的 repo:* 车道席位。
• B： 两个都做，各放一个独立仓，engine 落地后一起立卡。
• C： 先不做。等有客户提出再立卡，其余 P2/P3 照常推进。

不定会怎样： 不影响 P2/P3 的其他子卡。只是 engine 落地后，数仓这一行没有人接。

Scope (ADR-0153's P3 warehouse drivers row)

Snowflake and BigQuery plugin driver packages, outside this repository, verified by the conformance kit with the windowed-read cases (D1). Each package declares its own change.

Generated by Claude Code