20260922-0746-mate-package-document-structure Put the Mate package on the four-register model used by the Switch line

• status: completed
• priority: P1
• owner: claude/session-20260921-1700
• createdAt: 2026-09-22 07:46

Description

Follow-up to task 20260921-1700 ("处理 Mate 的吧"). The Mate package (bizplan/product/mate/) is to present the same four registers as the Switch line: customer brief, functional description with requirement IDs, target specification, development requirements. Findings and the proposal are in plan 20260922-0747.

In short: the spec is two Level 1 documents glued together (a 16-chapter hardware half and an 11-chapter software half, each with its own change log, chapter numbers restarting), so every inbound §n reference is ambiguous; the spec still describes "two halves" although the product plan decided on 2026-09-13 that Mate is one product; the chip candidate table sits in the spec while the hardware design appendix restates the same datasheet figures; the design appendix still specifies CAN FD (500 kbit/s / 2 Mbit/s) against the 2026-09-11 Classical CAN decision; and the brief is a stub with six "（待编写）" sections.

Acceptance criteria:

1. P03-mate.md is one Level 1 document with one chapter sequence; hardware (FR-nn) and software (SFR-nn) requirements each appear once, in chapter 3, unchanged in wording and numbering.
2. The chip candidate table lives in P03-mate-design-hardware.md; the spec keeps only the platform direction. No figure is set by a Level 2 page that is absent from the spec, except datasheet values and derived budgets.
3. No Mate file specifies CAN FD or 2 Mbit/s on YBO CAN; the spec records the single-product decision of 2026-09-13; the Level 1 / Level 2 disagreement on the third CAN controller is recorded as an open item, not silently resolved.
4. P03-mate-brief.md has all eight sections filled from the spec and adds no capability.
5. Every controlled Mate page follows the documentation standard: fixed-order relations list, full-width dashes, four-column ## 变更记录.
6. Inbound references that cite a section of a Mate file resolve to the chapter that now holds the content; the leftover P05-key.md FR-10 reference in X01 §9 is repointed to KEY-05.
7. bun run docs:lint && bun run docs:build && git diff --check passes.

ActiveForm

Restructuring the Mate package onto the four-register model

Dependencies

• blocked by: (none)
• blocks: (none)

Notes

• Full-tier task: five Mate files plus about 65 inbound reference lines in shared, Studio, View, Eye, Control, Switch and research pages.

• Mate is designed in-house (product plan §P3: EVT on an off-the-shelf SOM, DVT custom carrier); no supplier guide slot is created. The design appendices are the development requirements. If the carrier board is outsourced later, a -guide is added then.

• complete: Option A implemented; lint 222 pages 0 findings, build and git diff --check pass.