20260913-2315-ac-do-writeback Write the Core DO and unified Mate decisions back into the controlled package

• status: completed
• createdAt: 2026-09-13 23:15
• approvedAt: 2026-09-13 23:40
• relatedTask: 20260913-2312-ac-do-writeback

Context

• What was decided (user, 2026-09-13). The AC-side controller is YBO's own and belongs to the Core line as its DO control member; the no-AC-potential boundary still holds; Core's pulse-output requirement is kept. Combined with the earlier statement that Mate is one product, four things now differ from the controlled package.
• Why this is a relabelling, not a new specification. Nothing about the DO member's electrical envelope was stated — no channel count, current rating, price, milestone, enclosure or MCU. The decisions change who owns the AC DO function and which product executes it, and both are statements the package already makes about Core S/M/HD; they move to a named family member.
• The pulse requirement is the reason this matters commercially. PRODUCT-PLAN.md §P1 item 9 is flagged ⚑ and reads as a supplier-negotiation gate: firmware-enforced on-time limit, power-up glitch suppression, one channel per latching circuit. It is priced into the Core RFQ. Keeping it while moving its carrier means the RFQ text changes but the requirement does not weaken.
• The AC compliance position does not move. COMPLIANCE-MATRIX.md row "YBO AC" reads "YBO 侧无 LVD 范围：YBO 无任何硬件承载交流电位或载流". Because the DO member still only drives DC coils and reads dry contacts across the terminal block, this row stays true; only the sentence naming the driving product changes.
• Sizing. Governance: PRODUCT-PLAN.md, COMPLIANCE-MATRIX.md, OPEN-QUESTIONS.md. Product package: product/index.md, product/core/ (2 files), product/ac/ (3 files), product/mate/ (4 files), product/studio/P07-studio.md, product/control/P09-control-protocol-evaluation.md, product/switch/P05-air-hub.md. Six research reports also mention Core-driven latching relays; they are historical records under architecture.md and are not rewritten.

Proposal

A. Recommended: relabel ownership and execution subject, invent nothing

A1 — Core gains a named family member.

Document	Change
PRODUCT-PLAN.md §P1 family table	Add a fourth row, Core DO — 交流侧 DO 控制成员, positioned as: drives the DC coils of the AC panel's contactors and latching relays, makes its own switching decisions, reached from Mate over RS-485 or CAN. Every electrical cell reads 待定 — no channel count, rating, dimension or quiescent figure is written
§P1 custom requirement 8	Coil driving moves from "Core 通道" to the DO member; the terminal-block boundary sentence is unchanged
§P1 custom requirement 9 (⚑)	Pulse-output mode is kept verbatim and re-attached to the DO member; the flag and the firmware-enforced on-time limit stay
§P1 family topology paragraph	One sentence placing the DO member beside S/M/HD
product/core/P01-core.md, P01-core-design.md	Same member added at Level 1 and named in the design appendix; design values left 待定
product/index.md catalogue row P01	家族描述 gains the DO member

A2 — P04 changes execution subject, not boundary.

Document	Change
§P4 开关执行	Subject becomes the Core DO member; the terminal-block interface, coil types, surge ratings and de-energised default state stay
§P4 支路开关基线	The latching-relay baseline and the priced Schneider iTL / Finder candidates stay; "由一路单极性 Core 通道直接驱动" becomes the DO member's channel
§P4 脉冲时序, 降级行为	Same substitution; the 50 ms–1 s window, 5 actions/minute and the power-loss state-retention behaviour are unchanged
§P4 边界——不可协商	Unchanged, with one clause added stating the DO member is inside this boundary
product/ac/P04-ac-interface.md, P04-ac-board-16.md, P04-ac-commissioning.md	Same substitution wherever a Core channel is named as the driver
COMPLIANCE-MATRIX.md YBO AC row	"（Core 驱动接触器/分励脱扣断路器）" becomes the DO member; the "YBO 侧无 LVD 范围" verdict is unchanged

A3 — Mate becomes one product.

Document	Change
PRODUCT-PLAN.md §P3	Heading and the two #### subsections merge into one product section; hardware and software rows stay as rows of one table, keeping every figure, tier, price and milestone verbatim
product/mate/	index.md and P03-mate.md restated as one product. P03-mate-hub.md and P03-mate-hub-design.md keep their filenames — renaming them would break 10 inbound references for no reader benefit — but their headers stop calling Mate two halves
product/switch/P05-air-hub.md, product/control/P09-control-protocol-evaluation.md	References to "硬件 Hub" as a separate product are restated as Mate
product/studio/P07-studio.md, §P7	The pulse channel type now configures the DO member; the retry-reads-state-first rule, 5 s confirmation window and ≥12 s interval are unchanged

A4 — Tracking.

OPEN-QUESTIONS.md gains one item: the DO member's electrical envelope, tier, price and milestone are undecided, and the Core RFQ text must be reissued because requirement 9's carrier changed. The divergence warning in product/index.md is removed.

B. Alternative: hold the write-back until the DO member is specified

Leave the warning block in place and revisit when channel count, ratings and tier exist. Keeps the package internally consistent with one clearly marked exception, at the cost of leaving four documents stating something the user has already overruled — including a ⚑ supplier-negotiation item that feeds the Core RFQ.

C. Rejected: specify the DO member now

Writing a channel count, current rating, tier and price would put invented figures into a governing document. The package's own rule is that every value is either quoted from the plan, marked (t), or carries a datasheet source.

Scope

14 files: 3 governance, 11 in the product package. No figure is introduced; every new cell is 待定 or quotes an existing value. Research reports are untouched.

Verification

1. grep for a general-purpose Core channel driving AC coils → verify: no hit outside research/.
2. grep for Mate presented as two halves → verify: no hit outside research/ and historical task/plan records.
3. Pulse-output requirement still present and still flagged → verify: §P1 item 9 and §P7 both name the DO member.
4. COMPLIANCE-MATRIX.md still states "YBO 侧无 LVD 范围" → verify: row text unchanged apart from the driver name.
5. bun run docs:build and git diff --check → verify: both pass.
6. The warning block is gone from product/index.md → verify: page renders without it.

Open Items

• The DO member's model name. The diagram currently says P01 Core DO; a marketing name may differ.
• Its tier. Core S/M/HD are T0; P04 AC automation is T1. If the DO member is T0 it enters the critical path and the staffing table in §2 needs a line.
• Whether it reuses the Core base platform or is a separate design — this decides whether the Core sourcing gate in §P1 covers it.

Outcome

Option A was implemented. 15 files changed, one more than planned.

• The plan under-scoped by two files. BUSINESS-PLAN.md and BUSINESS-PLAN.en.md also stated that Core channels drive the AC contactors and that Hub reads the metering; the verification grep caught them. Both versions were updated together, as architecture.md requires shared business-plan claims to stay aligned.
• Nothing was specified for the DO member. Its row in the §P1 family table and in P01-core.md §2 reads 待定 for channel count, drive capability, voltage, quiescent current, enclosure and interface. OPEN-QUESTIONS.md P1-1e records the undecided envelope, tier, price, milestone and base-platform reuse, and states that the Core RFQ text must be reissued because requirement 9's carrier changed.
• The boundary and the pulse requirement survived intact. §P4's non-negotiable paragraph gained one clause placing Core DO inside it; requirement 9 keeps its ⚑ flag, its firmware-enforced on-time limit, its glitch suppression and its one-channel-per-latching-circuit rule; COMPLIANCE-MATRIX.md still reads "YBO 侧无 LVD 范围".
• Mate is one product. §P3's heading and the two #### subsections became 硬件面 and 软件面 of one product; product/mate/index.md and P03-mate.md restated; filenames left alone as planned.
• Research reports were not touched.

Verification: no general-purpose Core channel drives AC coils anywhere outside research/; Mate is not presented as two halves outside the P05 Switch line (where the phrase means Air and Key); the pulse requirement is present and flagged in both §P1 and §P7; the compliance verdict is unchanged; the divergence warning is gone from the product index; bun run docs:build and git diff --check pass.