20260911-2016-hub-mate-consolidation Consolidate P03 Hub and P08 Mate

• status: completed
• createdAt: 2026-09-11 20:16
• approvedAt: 2026-09-12 05:15
• relatedTask: 20260911-2014-hub-mate-consolidation

Context

Corrected on 2026-09-12 after the user restated the model; the first draft of this plan misread "merge" and has been replaced.

• P03 Hub is hardware; Mate is the software that runs on it. Mate on the Hub talks to the Air Hub over MQTT and CAN. P03-mate-hub.md is a sixteen-section hardware record (i.MX93 Linux gateway, tier T0, MSRP $549 / $649); P03-mate-software.md is an eleven-section software record (on-boat runtime, cloud, apps, fleet; Free and basic at T0, Premium and Security at T1, €8–12 and €15–25 per month).
• Air Hub + Air Switch are an independent product line. The Air Hub runs without the boat's hardware, reaches Mate over CAN and over the LAN, hosts P09 Control off the boat, and joins smart-home ecosystems. It requires Linux. This was applied to P05-air-hub.md §1/§2/§5, the platform options document, the product plan and the catalogue on 2026-09-12; the earlier "does the Air Hub still need Linux" rider is withdrawn.
• The user's direction: merge P03 Hub and Mate into one product called Mate.

Sizing: 15 documents reference P03-mate-software*, 31 reference P03-mate-hub* or the hub/ path, 34 in the union; PRODUCT-PLAN.md mentions P3 3 times and P8 0 times. Three structures depend on hardware and software being distinguishable and must survive inside the merged product: tiering (T0 hardware and T0 basic software versus T1 paid tiers), the commercial model (one-off hardware sale versus subscription engine), and compliance (RED/CRA/EMC hardware route versus GDPR/ePrivacy/CRA software route). The fail-safe doctrine — the Hub is never a safety dependency and no channel changes state when it is lost — is unchanged by the merge.

Proposal

One product, YBO Mate, with the hardware and software as two Level 1 records under a single product entry, one directory and one index.

Item	Proposed
Product ID	Keep P03 (the T0 critical-path anchor); retire P08 as a product ID
Directory	bizplan/product/mate/ (existing); hub/ is removed after its files move
Level 1	P03-mate.md — product entry: positioning, tiers, SKUs (Hub, Hub 4G), system position, links to both halves; P03-mate-hub.md (from P03-mate-hub.md) — hardware Level 1; P03-mate-software.md (from P03-mate-software.md) — software Level 1
Level 2	P03-mate-hub-design.md (from P03-mate-hub-design.md); P03-mate-data-model.md (from P03-mate-data-model.md)
Index	One mate/index.md listing the five files with their level
Catalogue	One row: P03 · YBO Mate — 船舶主控硬件 Hub + 运行其上的 Mate 软件、云与 App
Product plan	§P3 and §P3 become one §P3 Mate section with a hardware subsection and a software subsection; tier table entries stay as they are (Hub/Mate basic T0, Mate paid tiers T1)
Compliance	COMPLIANCE-MATRIX keeps two rows, both labelled Mate: hardware route and software route
Open questions	OPEN-QUESTIONS P3 and P8 sections merge under P3 Mate, item numbering preserved with H-/S- prefixes
Requirement IDs	Hardware FR-nn and software FR-nn collide inside one product; prefix the software set SFR-nn and update the 15 referrers (X02, P09, Eye, Studio, Tag, View)
Air Hub relationship	Stated once in P03-mate.md: Mate reaches the Air Hub over MQTT (LAN) and CAN; the Air Hub is not part of Mate and runs without it

Alternative kept for the record: keep both IDs (P03 hardware, P08 software) under the single mate/ directory and catalogue entry, changing no filenames or FR IDs. Cheapest (about six files), but the product would carry two IDs, which is the ambiguity the user asked to remove.

Risks

• The SFR-nn prefix and the file renames touch 34 documents; the reference checker used for the 2026-09-11 repair must be re-run so no §n or FR pointer is left dangling.
• Mixed tiers inside one product invite reading T1 paid tiers as part of the T0 commitment; the product entry must state the tiers per half.
• The merge lands while the P09 session is active and references P03-mate-software.md SFR-18/FR-20; coordinate before renaming.
• Retiring the P08 ID orphans historical changelog and plan references; those stay as history and are not rewritten.

Scope

Recommended form: about 34 files plus the product plan, compliance matrix, open questions, catalogue, changelog and indexes. Alternative form: about six files.

Alternatives

• Keep two products and only state the runtime relationship (the first draft's option 1). Rejected by the user's direction to make them one Mate product.
• Move Mate's backend on board and demote the cloud to a relay. Not what was asked; would be a separate local-first decision with its own security review.

Annotations

• 2026-09-11: Raised after the user stated that the P03 Hub runs Mate and that P03 and Mate can be merged.
• 2026-09-12: The user corrected the model — Hub is hardware, Mate is the software on it; Air Hub + Air Switch are an independent Linux product line reaching Mate over CAN and LAN and hosting P09 off the boat — and directed the merge into one Mate product. Plan rewritten; the Air Hub Linux rider is withdrawn and the Air Hub documents already updated. Awaiting proceed on the recommended form (keep P03, retire P08, SFR-nn for software requirements) or the two-ID alternative.