Changelog

2026-08-23 15:01 [progress]

Initialized PMA tracking and drafted the plan for resolving the business-plan P0 findings. No business-plan narrative was changed in this phase.

2026-08-23 15:04 [progress]

PLAN-001 was approved and implementation of the business-plan P0 corrections started.

2026-08-23 15:27 [decision]

Completed BIZ-001 and PLAN-001. The business-plan package now treats Core sourcing as a gated candidate, calculates margins from YBO net revenue, reconciles funding and contingency, replaces the unsupported market headline with a reproducible range, and controls EU compliance per SKU. Unavailable supplier, laboratory/counsel, customer, and monthly cash-flow evidence remains an explicit external release gate.

2026-08-23 15:29 [progress]

Claimed BIZ-002 and drafted PLAN-002 to define target customer roles, an 8–20 m / 26–65 ft provisional commercial vessel envelope, segment-specific offers, exclusions, and validation gates. No business-plan content was changed pending approval.

2026-08-23 15:42 [progress]

Revised draft PLAN-002 following user feedback. The proposed coverage now extends to 50 m through project-based zone distribution and adds a human-in-the-loop remote/uncrewed vessel electrical-infrastructure solution. Autonomous navigation and safety-critical propulsion/steering control remain outside the initial offer.

2026-08-23 15:44 [progress]

PLAN-002 was approved and implementation of the target-customer, vessel-envelope, larger-yacht zone-distribution, and remote-vessel solution updates started.

2026-08-23 15:55 [decision]

Completed BIZ-002 and PLAN-002. The plan package now distinguishes customer, buyer, user, and channel roles; defines standardized 8–20 m, engineered 20–24 m, and project-based 24–50 m yacht coverage; and adds an order-triggered Remote Vessel Infrastructure solution for compact human-in-the-loop electrical operations. Navigation/communications equipment replacement, autonomous navigation, and propulsion/steering control remain outside the initial claim boundary. Existing SAM and base financial figures were not expanded without evidence.

2026-08-23 16:24 [progress]

Claimed BIZ-003 and drafted PLAN-003 to add an internal completion checklist to the existing open-question pair and link it from the business-plan pair. No business-plan content was changed pending approval.

2026-08-23 16:30 [progress]

PLAN-003 was approved and implementation of the bilingual internal completion checklist and business-plan links started.

2026-08-23 16:32 [decision]

Completed BIZ-003 and PLAN-003. The existing open-question pair now begins with an eight-item bilingual internal completion checklist covering supplier, product, economics, cash-flow, compliance, cybersecurity, market-evidence, large-yacht and remote-vessel project gates. The business-plan pair links to that source of truth. All checklist items remain open pending their stated external evidence; current use for internal discussion is unaffected.

2026-08-24 04:12 [progress]

Claimed BIZ-004 and drafted PLAN-004 to replace the paired business-plan problem statements with an evidence-qualified lifecycle view. No business-plan narrative was changed pending approval.

2026-08-24 04:17 [progress]

PLAN-004 was approved and implementation of the bilingual business-plan problem statement started.

2026-08-24 04:18 [decision]

Completed BIZ-004 and PLAN-004. The paired business plans now frame nine evidence-qualified lifecycle pain points spanning refit labor, diagnostics, unattended operation, downtime, energy complexity, documentation drift, fragmented access, tacit knowledge, and remote/uncrewed-vessel recovery. Unsupported routine-price and absolute dealer-appointment claims were removed. Source evidence is explicitly limited to problem relevance and does not establish YBO demand, target-cohort incidence, savings, or willingness to pay.

2026-08-24 04:22 [progress]

Claimed PROD-001 and drafted PLAN-005 to replace fixed-chip wireless product definitions with supplier-neutral BLE, EU-433, EU-868 and US-915 regional radio profiles. No product-plan narrative was changed pending approval.

2026-08-24 04:24 [progress]

PLAN-005 was approved and implementation of the supplier-neutral regional radio product matrix started.

2026-08-24 04:30 [decision]

Completed PROD-001 and PLAN-005. The paired product plans now define BLE 2.4, EU-433, EU-868 and US-915 as controlled radio profiles instead of binding Air or Tag to one semiconductor. Air compares EU-433/EU-868 and US-915/BLE-only launch paths; Tag uses BLE plus an EU-868 or US-915 long-range profile while keeping PHY and silicon open. Shared application/security/bridge layers are separated from profile-specific RF hardware, antenna, firmware, labeling and conformity evidence. Open-question and compliance gates now require a destination-locked profile decision. Product priority, prices, margin targets and schedule dates did not change.

2026-08-24 05:05 [progress]

Claimed BIZ-005 and drafted PLAN-006 to consolidate nine business-plan pain points into four problem clusters with direct Section 4 product-response references. No business-plan narrative was changed pending approval.

2026-08-24 05:06 [progress]

PLAN-006 was approved and implementation of the concise bilingual problem-to-product map started.

2026-08-24 05:09 [decision]

Completed BIZ-005 and PLAN-006. The paired business plans now consolidate nine pain points into four problem clusters: installation/change cost; electrical state, diagnosis and unattended operation; operational/service continuity; and remote/uncrewed recovery. Each cluster links directly to its Section 4 product response, while the evidence paragraph retains all sources and validation boundaries in a shorter form. Eye and Tag remain staged options rather than being presented as responses to validated core problem clusters. Sections outside the problem statement did not change.

2026-08-24 05:11 [progress]

Claimed BIZ-006 and drafted PLAN-007 to replace the refit-preordered narrative with evidence-gated refit and new-build entry routes. The proposal adds an explicit new-build comparison against conventional wiring, extends Studio's production reuse and handover targets, and defines an OEM pilot scorecard. No business-plan or product-plan narrative was changed pending approval.

2026-08-24 05:13 [progress]

Expanded draft PLAN-007 to cover zone-distribution optimization, total installed cost and environmental protection for new builds. The planned comparison separates module IP rating, qualified connections and final installed-system protection, and does not claim that conventional relay/fuse cabinets cannot be protected. No business-plan or product-plan narrative was changed pending approval.

2026-08-24 05:25 [progress]

PLAN-007 was approved and implementation of the refit/new-build dual-entry narrative, OEM production solution and installed-protection evidence gates started.

2026-08-24 05:30 [decision]

Completed BIZ-006 and PLAN-007. The paired business plans now treat refit and new-build/OEM front-fit as evidence-gated parallel entry routes and define a repeatable OEM Production solution using Core HD/S/M, Key/Air, Studio and Hub/Mate. A six-factor comparison against conventional relay/fuse and bespoke point-to-point architecture covers distribution, model/options, environmental protection, commissioning, handover and total installed cost. Module IP rating is explicitly separated from qualified connections and final installed-system protection. Studio now targets reusable model/option templates, per-hull manifests, end-of-line evidence and controlled as-built packs; M-02 and the open-question pair define route-specific pilot scorecards. No market-model file, arithmetic, pricing, funding, schedule or vessel-size boundary changed. Focused structure, terminology and git diff --check verification passed.

2026-08-24 06:01 [progress]

Claimed BIZ-007 and started approved PLAN-008 to reorganize the paired business-plan Section 4 into an explicit six-part solution chapter. The change is structural and preserves the approved product, scenario and evidence boundaries.

2026-08-24 06:07 [decision]

Completed BIZ-007 and PLAN-008. Section 4 of the paired business plans is now an explicit solution chapter organized as overall architecture, new-build/OEM, refit, large-yacht zone distribution, remote/uncrewed vessels, and product matrix/boundaries. Section 3 now links each problem cluster to the relevant solution subsection. All eight product lines, the six-row OEM comparison, staged-product status, bundles, non-goals and installed-protection/evidence qualifications remain present. No product, price, market, financial, schedule, compliance or vessel-envelope claim changed. Focused bilingual structure, anchor, table and git diff --check verification passed.

2026-08-24 06:45 [progress]

Claimed BIZ-008 and started approved PLAN-009 to distinguish core, project-expansion and strategic markets and to replace absolute competition claims with official-source-qualified positions and measurable YBO comparison hypotheses.

2026-08-24 06:50 [decision]

Completed BIZ-008 and PLAN-009. The paired business plans now label 8–20 m refit and standardized 8–24 m OEM front-fit as initial core routes, 20–50 m engineered/zone work as project expansion, and remote/uncrewed plus later class-qualified small-commercial variants as strategic options. The competition section now acknowledges capable incumbent platforms, corrects PowerPlex and Victron characterizations, avoids absolute lock-in or response-impossibility claims, and frames YBO's compound differentiation as a benchmark/pilot hypothesis supported by official vendor links. Cohorts, vessel envelopes, market arithmetic, product scope, pricing, financials, schedule and compliance remain unchanged. Focused bilingual, table, source-link and git diff --check verification passed.

2026-08-24 06:58 [progress]

Claimed BIZ-009 and started approved PLAN-010 to clarify that refit coverage spans 8–50 m, split between standardized 8–20 m delivery and engineered 20–50 m zone projects including cabin distribution and helm electrical/control-panel modernization.

2026-08-24 07:02 [decision]

Completed BIZ-009 and PLAN-010. The paired business plans now define one 8–50 m commercial refit envelope with two delivery modes: standardized scoped or whole-boat work for 8–20 m, and engineered zone refits for 20–50 m. The latter explicitly includes accommodation/cabin distribution, helm electrical distribution and control-panel modernization, lighting, deck-service and navigation/communications power circuits. Helm work is limited to non-safety-critical electrical interfaces; propulsion, steering and other safety-critical vessel control remain excluded. Customer-cohort dimensions, market arithmetic, product definitions, prices, financials, schedule and compliance did not change. Focused bilingual, six-row cohort, table, terminology and git diff --check verification passed.

2026-08-24 08:36 [progress]

Claimed BIZ-010 and drafted PLAN-011 for a Chinese internal PPT build guide. Investigation found that the 12-section business plan is an appropriate source of truth but needs a shorter decision narrative, page-level source mapping, evidence labels and an appendix boundary before slide production.

2026-08-24 08:42 [progress]

PLAN-011 was approved and implementation of the Chinese internal PPT build guide started.

2026-08-24 08:47 [decision]

Completed BIZ-010 and PLAN-011. Added a Chinese source-controlled internal PPT build guide with an 18-slide decision narrative, a 12-slide appendix map, page-level messages, visual recommendations, canonical source mapping and discussion prompts. The guide defines evidence-status labels, commercial-priority colors, content-density limits, an asset backlog, a source-of-truth matrix, a build workflow and a pre-export checklist. It preserves standardized 8–20 m versus engineered 20–50 m refit delivery, staged product priorities and the existing wireless, ingress-protection, helm, navigation/communications and remote-operation boundaries. Existing business, product, market, commercial, compliance and assumption source files did not change. Focused structure, link-target-file, terminology, Markdown-table and whitespace verification passed.

2026-08-24 14:05 [decision]

Unified refit coverage as a single 8–50 m envelope with no length-based tiers (commit 4112795, interactive session). The former 8–20 m standardized versus 20–50 m engineered split was removed from the paired business plans, product plan, market model, commercial model and open questions; whether a boat receives the standard bundle or a project quotation is now decided by the electrical survey and zone-refit triggers, not by length. This supersedes the delivery-mode split recorded under BIZ-009/PLAN-010.

2026-08-24 14:13 [decision]

Removed the OEM front-fit route (commit 33d479f) and reverted that change (commit 8c34ec7) within the same session after the user clarified that YBO does pursue the new-build front-fit market; the objection was to supplying white-label/OEM products to third parties, not to the route itself. Net effect on content: none; recorded here so the two commits are traceable.

2026-08-24 14:16 [decision]

Restored new-build front-fit as an initial route sold under the YBO brand (commit 552611e): 8–24 m standard design-in, 24–50 m project-based, with explicit "no white-label/OEM supply" statements in the business plans, open questions and commercial model. Sourcing-side "OEM" wording was replaced by "contract manufacture / manufacturing partner"; the word OEM survives only in the negation statements and a competitor quotation. The market model keeps the new-build segment (SAM €18–98 M, base €46 M). This supersedes the "new-build/OEM front-fit" framing recorded under BIZ-006/PLAN-007 and the initial-core/project-expansion hierarchy assumed by BIZ-010/PLAN-011.

2026-08-24 14:27 [progress]

Claimed BIZ-011 and drafted PLAN-012 to reconcile the PMA task, plan and changelog records with the unified 8–50 m refit coverage and the YBO-branded new-build front-fit route, and to commit the outstanding tracking files and PPT build guide. No source-file content was changed pending approval.

2026-08-24 14:52 [decision]

Completed BIZ-011 and PLAN-012. Appended dated supersession notes to BIZ-006, BIZ-009, BIZ-010, PLAN-007, PLAN-010 and PLAN-011 without rewriting their history; recorded the three interactive decisions of 14:05–14:16 with commit references; removed the visual-system section from the Chinese PPT build guide on user instruction and renumbered its sections; verified the guide against the current business plan (18 core slides, 12 appendix rows, no length-tier or OEM front-fit wording, all cross-document anchors resolve). Committed the guide and all outstanding tracking files in one commit; git diff --check passed.

2026-08-24 14:55 [progress]

Claimed BIZ-012 and drafted PLAN-013 to bring AC under YBO system management as an engineered solution on branded components: P4 redefined as "YBO AC" with an AC panel-build layer (existing revenue bridge) and an AC automation layer (Core outputs driving contactors and shunt-trip breakers; shore, generator, inverter/charger and solar interfaces; Studio-defined source priority and interlocks). No source-file content changed pending approval.

2026-08-24 15:12 [decision]

Completed BIZ-012 and PLAN-013. The planning package now covers the complete on-board electrical system, DC plus AC: P4 is redefined as "YBO AC — AC Integration and Automation Solution" with a panel-build layer (T0R revenue bridge, unchanged) and an automation layer (T1, first delivery on the demo boat M10–12) in which Core channels drive DC-coil contactors and shunt-trip breakers inside branded AC boards, Hub reads AC metering, inverter/charger, solar and generator state, Studio defines source priority, interlocks and load shedding, and Mate logs every transfer. Boundaries recorded in both languages: YBO does not manufacture AC switchgear, chargers, inverters, generators or solar controllers; sources are never paralleled; hardware-interlocked transfer, RCD/ELCI and overcurrent protection stay on the AC board; generator start/stop is a request to its own controller. Executive summary, architecture, refit and new-build solutions, product matrix, bundles, revenue streams, compliance matrix, open questions and the PPT guide were updated; market model, financial figures and schedule end date are unchanged.

2026-08-24 15:20 [progress]

Claimed BIZ-013 and drafted PLAN-014 to add AC current sensing and AC presence/voltage sensing as system feedback: branded CTs and isolated transducers on existing Sense/Core M inputs, published like DC channel telemetry and used as the read-back for contactor commands. No source-file content changed pending approval.

2026-08-24 15:30 [decision]

Completed BIZ-013 and PLAN-014. YBO AC Layer 2 now includes AC current and AC presence/voltage sensing as system feedback: branded split-core CTs and isolated voltage transducers or voltage-monitoring relays on existing Sense (or Core M) inputs report per-feed AC current and per-source/per-contactor presence, voltage and frequency on the YBO bus with the same telemetry model as DC channels, confirm every contactor command within the read-back window, and drive local AC alarm rules on Sense. Sense gained the AC input types and alarm rules; the business plan states that AC feeds and sources are shown, alarmed and logged like DC; open question P4-9 records the sensing-route decisions; the compliance matrix notes CT secondaries and transducer outputs are SELV on the DC-side routes. Accuracy is stated as monitoring grade, not billing grade. No new hardware SKU, price or schedule change.

2026-08-24 16:20 [progress]

Claimed RESEARCH-001 and drafted PLAN-015 for a Chinese, source-traceable product-matrix report covering CZone and four additional representative marine digital-switching and vessel-control platforms. Initial official-source review confirms current public product material for CZone, Garmin EmpirBus, Maretron/Carling MPower, E-T-A PowerPlex and Victron, but not a defensible public global market-share ranking. The proposal therefore treats them as a five-platform benchmark set, gives CZone the deepest model-level coverage, labels Victron as an adjacent energy/control platform, and makes lifecycle and evidence gaps explicit. No competitor report or business-plan content was changed pending approval.

2026-08-25 00:00 [progress]

PLAN-015 was approved and implementation of the Chinese five-platform marine digital-switching product-matrix report started.

2026-08-25 04:10 [progress]

Expanded RESEARCH-001 and PLAN-015 on user instruction from a core-model comparison to an industry-research document suite covering all publicly documented products in the selected marine intelligent-electrical platforms. The revised deliverable is a cross-vendor report plus five vendor appendices. CZone, Garmin EmpirBus/digital switching, Maretron MPower and E-T-A PowerPlex receive complete platform inventories; Victron receives its complete marine-electrical family and public model-series inventory. Unrelated Garmin categories and non-marine application material remain out of scope.

2026-08-25 04:23 [decision]

Completed RESEARCH-001 and PLAN-015. Added a 1,149-line Chinese industry-research suite comprising a normalized five-platform report and separate full public-product appendices for CZone, Garmin EmpirBus/digital switching, Maretron MPower, E-T-A PowerPlex and Victron Marine. The report explicitly treats the vendors as representative leading benchmarks rather than an unsupported global market-share ranking. It inventories current model families, public variants, part numbers, direct accessories, software, configuration and cloud services within the approved platform boundaries; distinguishes marine, RV/specialty, legacy and discontinued products; records PowerPlex final-order and final-delivery dates; and labels Victron as an adjacent energy/control platform. Table-shape, local-link and whitespace verification passed. Sixty-two of 71 unique official URLs returned 2xx directly; eight Garmin/E-T-A pages were browser-resolved behind bot protection, and the CZone Portal is an explicitly account-controlled endpoint.

2026-08-24 17:34 [progress]

YBO AC was restated as a sense-and-control-only boundary and its interface specified. P4 now opens with a non-negotiable clause that no YBO hardware carries AC load current or AC potential, with the demarcation at the terminal block; Layer 1 changed from AC panel build to an AC design & commissioning service whose board is built and signed off by a partner workshop or licensed electrician, which removes LVD scope from the YBO side across the compliance matrix. The interface was then specified: a latching-relay selection baseline (24 VDC coil, two-pole mandatory, single-coil toggle, two verified candidates and one flagged unverified), a non-negotiable SSR exclusion for source transfer, Core pulse-output mode with a firmware-enforced conduction limit, a Studio pulse channel type whose retry reads state before pulsing, and a three-layer AC sensing structure (Sense digital inputs for Hub-independent safety judgements, a Modbus acquisition module for per-circuit telemetry, auxiliary contacts on automated circuits) that supersedes the analog-CT route from PLAN-014 and states explicitly that current confirms a closed circuit but never an open one. No financial figure, schedule or product ID changed; the revenue-bridge magnitude review from the Layer 1 re-scope remains open.

2026-08-25 08:20 [progress]

Claimed RESEARCH-002 and drafted PLAN-018: investigated the certification frame for consumer-class non-core equipment on yachts of 24 m and above (flag yacht codes, class essential/important/non-important service split, IEC 60092-507, EMC zones, IACS E26/E27 and ISM cyber) from primary sources; findings reported to the user, report write-up pending approval.

2026-08-25 08:50 [decision]

Completed RESEARCH-002 and PLAN-018. Added the Chinese research report on certification requirements for consumer-class non-core equipment on yachts of 24 m and above. Key findings: CE product law is length-independent while the RCD/ISO 10133/13297 frame ends at 24 m; REG, Malta and RMI yacht codes hand the electrical installation to classification-society rules and make class a hard gate for commercial yachts; class rules require product/type-approval certificates only for essential, important and emergency services (DNV lists the main lighting system as important and navigation lights as emergency), while technical, environmental and EMC requirements apply to all equipment; IEC 60092-507 is the 24–50 m installation standard; IEC 60533 EMC zones make IEC 60945 relevant only for bridge/antenna-area equipment; IACS UR E26/E27 is non-mandatory guidance for yachts and IMO MSC.428(98) applies through ISM to ≥500 GT commercial yachts. The report maps every YBO line to certificate-required / not-required, lists boundary cases and recommends a v1 scope limited to non-important services on classed yachts. No controlled planning document was changed.

2026-08-25 12:36 [progress]

Claimed RESEARCH-003 and drafted PLAN-019: surveyed, from official vendor pages, suppliers worldwide of CAN-controlled solid-state smart power distribution modules comparable to the Senptec KM3258 reference module (Senptec product list and Chinese peers, global commercial-vehicle Tier-1 and catalogue PDMs, off-highway controllers, motorsport/aftermarket PDMs, marine/RV digital switching beyond RESEARCH-001). Findings reported to the user; report write-up pending approval.

2026-08-25 12:42 [decision]

Completed RESEARCH-003 and PLAN-019. Added a Chinese, source-traceable global supplier-landscape report for low-voltage intelligent PDMs using Senptec KM3258 as the public comparison baseline. The report distinguishes productised direct alternatives, China-based candidates, automotive Tier-1 zonal/eFuse platforms, adjacent custom PDU manufacturers, marine digital-switching competitors, and open-market motorsport products. It identifies E-T-A, MTA, GINSIN, Enovation Controls, Würth Elektronik ICS, and MRS Electronic as the first RFQ pool; maps candidates to Core S/M/HD; finds no public standard module that meets the complete Core HD requirement; and records contact order, RFQ questions, sample verification, cost gates, and evidence gaps. No approved Core specification or supplier selection changed. Table-shape, local-link, external-link, and whitespace verification passed.

2026-08-25 13:17 [decision]

Extended RESEARCH-003 and PLAN-019 with the companion appendix bizplan/research/06a-senptec-class-pdm-supplier-inventory.md. Using the Senptec KM2210 reference board as the comparison point, it inventories about 120 CAN-controlled solid-state or hybrid smart power distribution products from 90+ vendors in five groups (Chinese commercial-vehicle peers, global commercial-vehicle Tier-1 and catalogue PDMs, off-highway mobile-machine controllers, motorsport/aftermarket PDMs, marine/RV digital switching beyond RESEARCH-001), records Senptec's public product line and company facts, and compares the closest matches against the KM2210 on channel mix, 12/24 V support, inputs, CAN dialect, local logic, ingress rating, manual bypass, public pricing and low-volume availability. Key findings: no overseas catalogue module combines 12/24 V, a 22-channel three-tier mix with a 5 A small-load tier, per-channel current sensing and an IP-rated housing; the closest purchasable matches are E-T-A SCS200/SCS1000, Enovation IX3212, Carling CLTM12-S, Trombetta 12-output, Infinitybox NGX and Blink Marine PC10; at least 15 Chinese vendors publish comparable products, with Alson the only one naming marine as a target market; automotive Tier-1 zone controllers remain OEM-only; and manual bypass is a near-universal marine requirement. The 06 report gained a cross-reference to the appendix; no controlled planning document changed.

2026-08-25 14:20 [decision]

Completed RESEARCH-004 and PLAN-020. Added the Chinese full-retention supplier appendix bizplan/research/06b-china-intelligent-pdm-supplier-inventory.md, correcting the earlier shortlist bias without changing RFQ priorities. It preserves 20 Chinese-owned manufacturers with verified low-voltage intelligent-distribution or near-direct product/technology evidence, separately identifies ACTIA's China operation, and retains all discovered zonal-controller, traditional fuse/relay-box, high-voltage PDU/BDU, component/engineering, patent, ambiguous-name, and weak-evidence leads. Newly surfaced high-relevance evidence includes MIND's eFuse and ring-redundant distribution products, ZWELEC's CAN smart fuse boxes, Inner Mongolia First Machinery Hongyuan's low-voltage intelligent-distribution R&D, and the previously omitted Molead and TOSUN entries. Reports 06 and 06a now link to the China appendix and explicitly state that their three-vendor and 15-vendor China sections are filtered views, not complete inventories. Table-shape, local-link and whitespace checks passed; 73 of 82 external URLs returned HTTP 200 directly, while eight official sites/large PDFs timed out in the scripted check and one site returned a redirect but remained identifiable through browser/search review. No supplier was selected and no product specification or RFQ was changed.

2026-08-26 08:43 [decision]

Completed RESEARCH-005 and PLAN-021. Added the 300-line Chinese report bizplan/research/07-marine-vs-automotive-power-distribution.md, explaining why marine and automotive low-voltage distribution differ and why fuses, breakers, relays/contactors, electronic protection and manual fallback coexist. The report corrects the premise that current automotive production has universally eliminated conventional fuses/relays, separates source/feeder conductor protection from branch electronic protection, compares twelve architecture dimensions, documents three reference topologies and maps twelve load classes to suitable switching, protection and fallback layers. Corrected the paired business and product plans so Core replaces most eligible branch fuses/control relays rather than every protection or switching device; independent battery/source and zone-feeder protection remains selected against conductor ampacity and prospective fault current; critical loads retain local/manual recovery; and Core HD direct switching is gated by current, inrush, thermal, reverse-energy and fault-interruption evidence. Also corrected the AC SSR rule to identify fail-short as a credible hazardous semiconductor failure mode rather than the only failure mode. Table-shape, local-link, bilingual-boundary, whitespace and git diff --check verification passed. Sixteen of 22 unique external URLs returned 2xx/206 directly; six ISO/FORVIA pages returned scripted 403 responses but were browser-resolved during research.

2026-08-26 16:49 [progress]

Claimed RESEARCH-006 and drafted PLAN-022 to survey open-source PDMs, the actual content of Tesla's "open-source" releases, and vendor high-current solid-state switch reference designs as the PCB reference for a 100 A / 200 A single-platform variant pair. No report, product or business-plan content was changed pending approval.

2026-08-26 16:58 [progress]

PLAN-022 was approved with the report language confirmed as Chinese; implementation of the open-source PDM and high-current switch reference report started.

2026-08-26 17:02 [decision]

Completed RESEARCH-006 and PLAN-022. Added the Chinese report bizplan/research/08-open-source-pdm-and-high-current-switch-reference.md, which establishes that no public open-source PDM exceeds 26 A per channel (dingoPDM-Max) and that Tesla's Roadster release is documentation and CAN databases under a disclaimer rather than an open-source power-distribution design, while the Cybertruck 48 V design document remains private. The report documents the gate-driver-plus-parallel-TOLL-MOSFET pattern of the Infineon 12 V HC-PDU (231 A) and 48 V battery-switch (300 A) reference designs and the TI TPS121x/TIDA-020065 smart-fuse designs as the technical basis for a single PCB with 100 A and 200 A BOM variants (80 V MOSFETs, back-to-back common-source, pre-charge, TVS/active clamp, shunt plus coreless-Hall sensing, press-fit bus bar for 200 A), gives a PCB checklist and validation plan, and maps the platform onto the Core HD boundary set in PLAN-021 without changing any approved specification. Report 07 §10.3 now cross-links to it. Verification passed for table shape, local links, whitespace and git diff --check; 64 of 69 unique URLs returned 2xx/206 by script and the remaining five were read through the research fetch tool.

2026-08-26 17:03 [decision]

Reconciled two RESEARCH-006 drafts against the approved PLAN-022 interpretation. The canonical deliverable is bizplan/research/08-open-source-high-current-pdm-pcb-reference.md (512 lines), where 100 A and 200 A are continuous total platform input ratings, the control/communications layer is common, and the power board, copper busbar, terminals, sensor range and thermal assembly are separately qualified. The broader 08-open-source-pdm-and-high-current-switch-reference.md draft is retained with a supersession notice because its single-channel and shared-current-PCB premise conflicts with the approved scope; its extra part-number and teardown leads require re-verification before design use. Report 07 now links to the canonical report. Canonical-report table shape, local links, whitespace and git diff --check passed; 42 of 43 external URLs returned 2xx/206 directly and the official Tesla legal page was browser-resolved despite scripted 403.

2026-08-26 17:13 [progress]

Claimed RESEARCH-008 and drafted PLAN-024 after the user fixed the platform envelope at 200 A total input, 46 output channels and a 100 A per-channel ceiling. The plan proposes a standalone report 09 on the channel-tier architecture (two candidate 46-channel mixes, 12/24 V device strategies, SPI daisy-chain control budget, sealed-connector and stud plan, loss/thermal budget, CTRL/PWR/BUS partition) built on the canonical report 08, and lists the product-plan implications as open decisions. No report or controlled document was changed pending approval; PLAN-023 remains pending in parallel.

2026-08-26 17:26 [progress]

PLAN-024 deliverable renumbered from report 09 to report 10 on the user's instruction; report 09 is reserved by other work in progress. Still awaiting approval.

2026-08-26 17:34 [decision]

Completed RESEARCH-007 and PLAN-023. Added the independent Chinese report bizplan/research/11-high-current-pdm-platform-and-bth50015-reference.md; number 11 avoids the report 10 reservation made concurrently by PLAN-024, and reports 07–10 remain untouched by this task. The report independently verifies six source-available hardware references, Tesla's official open-source and Model 3 electrical-reference boundaries, Infineon and TI reference designs, and high-current PCB construction sources. It concludes that BTH50015-1LUA supports 12 V at the nominal lower limit but is a conditional 32–35 A branch switch, not a 100 A / 200 A main-path device; its 90 A minimum short-circuit threshold does not replace conductor-matched branch protection, and its off-state body diode does not provide reverse-current isolation. The proposed platform shares the control/communications layer while qualifying separate 100 A and 200 A busbar, terminal, sensor, protection, and thermal assemblies. Table shape, loss calculations, URL reachability, whitespace, and git diff --check passed; 24 of 25 unique official URLs returned HTTP 2xx directly, and the Tesla legal page was independently browser-resolved after a scripted HTTP 403.

2026-08-27 20:08 [progress]

Claimed PROD-002 and drafted PLAN-025 to expand the placeholder Air (P5) and Key (P6) sections of the paired product plans into benchmark-backed target specifications (switch form factors, coin-cell and kinetic power options, battery budget, acknowledgement/latency/security behaviour, bridge capacity and no-Hub fallback; keypad electrical envelope, bus profiles, key technology, per-key read-back states, night mode, Studio semantics, mounting and ingress targets) and to update OPEN-QUESTIONS P5/P6 accordingly. No controlled document changed pending approval.

2026-08-27 20:25 [decision]

Completed PROD-002 and PLAN-025. Expanded §P5 YBO Air and §P6 YBO Key in bizplan/PRODUCT-PLAN.md and PRODUCT-PLAN.md from five-row placeholders into target specifications (t). Air: Air 2 / Air 4 form factors; end-user-replaceable CR2450 (EU 2023/1542 Art. 11 applies from 18 February 2027, before the M14 launch) plus a battery-free kinetic evaluation SKU; a ≥3-year battery budget behind the ≥2-year public claim; ACK-within-100 ms and read-back-only LED behaviour, ≤150/300 ms press-to-light targets, 30-minute heartbeat supervision; device-unique-key AES-128 CCM authentication with replay rejection and a ≤60 s physical pairing window; three gestures; bridge NVM binding so Hub loss does not affect Air; bridge capacity, external-antenna option, audit forwarding and range-planning rules. Key: Key 4 / Key 8 with 8–32 V single-cable supply, ≤5 mA standby / ≤60 mA full backlight; YBO CAN FD primary with Core-resident binding, RS-485 Modbus RTU slave with Hub or Core HD as master; ≥1 M-operation silicone/metal-dome keys with 15 mm inserts; per-key RGB states including a pending state that mirrors the control-plane doctrine; red night mode with boat-wide day/night; Studio per-key semantics; 52 mm hole-saw mounting; front IP67 / rear IP54 and -25…+70 °C. Both products now carry a recommended-silicon row (candidate, frozen at the §6 item 4 M3 gate): TI CC1354P10 dual-band radio (alternate Silicon Labs EFR32FG28B322), Nordic nRF54L15 for a BLE-only switch, EnOcean PTM 215B kinetic module, NXP S32K118/S32K116 MCUs, NXP TJA1463 CAN SIC transceiver, TI LP5024/LP5012 LED drivers, TI LMR36503-Q1 / LMR36506-Q1 buck converters, all checked against official datasheets. OPEN-QUESTIONS P5/P6 (both languages) now record which items the baseline answers pending EVT verification and add four new items (radio platform confirmation, Key 12-key variant, Key N2K profile). Tiers, prices, milestones, radio-profile policy and compliance routes are unchanged.

2026-08-27 20:35 [progress]

Claimed PROD-003 and drafted PLAN-026 after the user identified that the Air section lacks a gateway carrying BLE, 433 MHz and LoRa together. The plan proposes replacing the single-profile Air bridge with a tri-radio Air Hub on the YBO CAN FD bus (CC1354P10 for BLE + 433/868/915 FSK, SX1262 for LoRa with LR1121 as alternate, S32K118 + TJA1463, one PCB with region-locked SKUs), local Tag alarm evaluation, and consistent cross-references in §3, P12, §5 and the compliance matrix. No controlled document changed pending approval.

2026-08-27 21:00 [decision]

Completed PROD-003 and PLAN-026. The single-profile Air bridge is replaced by the tri-radio YBO Air Hub in bizplan/PRODUCT-PLAN.md and PRODUCT-PLAN.md: one YBO CAN FD node carrying BLE 2.4 GHz (R1), 433 MHz FSK/OOK (R2) and LoRa 863–870 / 902–928 MHz (R3) on one PCB with region-locked SKUs (EU R1+R2+R3-868; US R1+R3-915, 433 unpopulated); RS-485 Modbus RTU slave as standard population for PLC/legacy integration, counted into the Hub/Core HD poll budget; USB-C service port; a Gateway-E variant (W5500-class SPI Ethernet + PoE PD footprint) reserved for PoE remote antenna mounting and LoRaWAN forwarding, decided at Air EVT; three antenna ports with SMA option; ≤32 switches / 128 keys and ≤64 tags; Tag alert and heartbeat-loss evaluation local to the gateway so alarms survive Hub loss; recommended silicon NXP S32K118 + TJA1463, TI CC1354P10 (R1+R2), Semtech SX1262 (R3, LR1121 alternate), THVD1450-class RS-485 and TI LMR36506-Q1, all datasheet-verified; an SX1302-class LoRaWAN concentrator is explicitly excluded and stays the T3 shore gateway. Cross-references reconciled: §3 link table and radio matrix now map EU-433 to the gateway R2 and EU-868 / US-915 to the gateway R3 with the Hub plug-in as alternative; P12 Tag receiver side moves to the gateway; §5 prices Air switch / Air Hub at $59 / $199 (t) with a $64.68–74.63 COGS ceiling; COMPLIANCE-MATRIX Air row renamed with a combined three-radio assessment note; OPEN-QUESTIONS P5 renamed bridge to gateway and added item 8 (RF co-location, airtime and RS-485 bus budget). Tiers, milestones, Tag positioning, radio-profile policy and §6 gates unchanged.

2026-08-27 21:20 [progress]

Claimed PROD-004 and drafted PLAN-027 after the user directed that the Air Hub and switches must be sellable without Core modules. The plan proposes re-hosting the gateway on ESP32-C5 (native 2× CAN FD, Wi-Fi 6, BLE; verified against datasheet v1.4 and ESP-IDF TWAI docs), adding a dedicated nRF54L15 BLE receiver, an NMEA 2000 port for third-party digital switching (PGN 127502), standalone and system operating modes, the Wi-Fi doctrine change, and the business, compliance and cost consequences. No controlled document changed pending approval.

2026-08-27 21:55 [decision]

Completed PROD-004 and PLAN-027. YBO Air is now a standalone product system: the Air Hub is re-hosted on ESP32-C5 (native 2× CAN FD — one for the YBO bus, one as an NMEA 2000 port — dual-band Wi-Fi 6, BLE 5, secure boot/key manager; C5 volume availability is an M3 gate with ESP32-C6 + MCP2518FD or NXP S32K148 as fallbacks), keeps a dedicated Nordic nRF54L15 BLE receiver because the C5 2.4 GHz radio is time-shared with Wi-Fi, and retains CC1354P10 (433/868/915 FSK) and SX1262 (LoRa, LR1121 alternate) with 2× TJA1463 and LMR36506-Q1. Two operating modes are defined in bizplan/PRODUCT-PLAN.md / .md: standalone (binds switches to third-party NMEA 2000 digital switching via PGN 127502/127501, runs Tag alarms locally, connects to Mate cloud over Wi-Fi with the Hub's mTLS/signed-OTA/no-inbound-port rules, serves a local UI) and system (YBO bus node with the Hub as uplink and UI host, Wi-Fi backup only). Platform §1 now states the Wi-Fi doctrine (Hub and Air Hub) and fixes the MCU family to S32K148 (S32K1 flagship) and S32K314 (S32K3 direction) per user decision — S32K144 is no longer used; §3 marina Wi-Fi row, §5 gateway price ($45–60 BOM / $249 MSRP, $80.93–93.38 COGS ceiling), §6 item 4 (ESP32 evaluation: no sub-GHz, C6/P4 TWAI classic-only, C5 chosen) and new item 11 (standalone actuator strategy) updated. BUSINESS-PLAN §4 Key & Air row adds the standalone entry; COMPLIANCE-MATRIX Air row adds Wi-Fi scope and NMEA 2000 certification for the gateway; OPEN-QUESTIONS P5 item 9 lists the standalone-system decisions (actuator, Hub attach rate and kit pricing, cloud onboarding without Hub, NMEA budget, C5 supply) for the M3 bundle. Tiers, milestones and Tag positioning unchanged.

2026-08-27 22:05 [decision]

Closed the standalone-Air actuator question under PLAN-027: the standalone Air kit is the gateway + switches pair only, sold without any other YBO node, and no YBO actuator node is defined; its actuation targets are third-party NMEA 2000 digital switching (PGN 127502/127501) or RS-485 Modbus devices already on board, recorded as a kit prerequisite for Studio and sales material. Updated PRODUCT-PLAN §6 item 11 and the P5 gateway modes row, OPEN-QUESTIONS P5-9 and the BUSINESS-PLAN §4 Key & Air row in both languages.

2026-08-27 22:45 [progress]

Claimed PROD-005 and drafted PLAN-028 to create a standalone product documentation package (product/index.md plus one datasheet-backed specification file per product) and to bring Core, Sense, Hub, AC interface, View, Eye and Tag to the same depth as Air and Key. No controlled document changed pending approval.

2026-08-28 00:10 [decision]

Completed PROD-005 and PLAN-028. Added the product specification package bizplan/product/: index.md / index.md (catalog, lifecycle states, conventions, sixteen-section hardware template and eleven-section software template, how-to-add rules) and twelve paired English/Chinese specifications — P01 Core (S/M/HD; vendor-base requirements and the ground-up fallback with per-tier switch classes, S32K314/S32K148, TJA1463, TLE4972 trunk sensing, DEUTSCH/AMPSEAL connectors), P02 Sense (ADS131M08/ADS1220 front end, REF200 excitation, MAX22190 digital inputs, S32K118), P03 Hub (i.MX93 with VAR-SOM-MX93/DART-MX93/UCM-iMX93 SOM candidates, Murata 2EL / NXP IW612 Wi-Fi-BLE, Quectel EG915Q/EG25-G LTE, u-blox MAX-M10S GNSS, ISO1042 isolated J1939, LTC3350 supercap, RAUC/Mender A/B), P04 AC interface (terminal-block boundary tables, Acti9 iTL / Finder 20.22 / iATL24, Eastron SDM630 / Carlo Gavazzi EM24 / Accuenergy AcuRev 2100 candidates, signal-boundary rules), P05 Air Switch and P05 Air Hub, P06 Key, P07 Studio, P08 Mate, P10 View (Riverdi 850 cd/m² bonded displays), P11 Eye (ONVIF/RTSP, NPU, Teltonika/PLANET PoE switches), P12 Tag (STM32WL55 / LR1110, LIS2DW12, BQ25120A, MAX-M10S). Every silicon figure cites an official datasheet or is marked unverified; every file quotes the governing plan and references its open decisions rather than closing them. Two datasheet-verified corrections were carried into the governing plan in both languages: Hub USB host is USB 2.0 (i.MX93 has no USB 3.0; discrete controller optional) and EnOcean PTM 215B is not recommended for new designs (successor PTM 216B). P10's CAN transceiver was aligned to the family part TJA1463. Pointers added in PRODUCT-PLAN.md / .md, docs/architecture.md and AGENTS.md. Alignment checks show identical line, table-row, heading, FR and URL sets in every language pair; package checks and git diff --check pass.

2026-08-27 23:45 [progress]

Claimed PROD-006 and drafted PLAN-029 to deepen the product package: two cross-product foundations (YBO CAN FD application protocol, Studio configuration schema) and Level-2 design annexes per product in priority-tier waves. No controlled document changed pending approval.

2026-08-28 01:30 [decision]

Completed PROD-006 wave 1 under PLAN-029. Added two cross-product foundations to bizplan/product/: X01 YBO-CAN application protocol (ISO 11898-2:2024 SIC physical layer at 500 kbit/s / 2 Mbit/s (t), node model with 8-bit IDs and 64-bit UIDs, 29-bit identifier layout PRI/FAM/SRC/DST/SUB, ten message families with payload tables, command → ACK ≤100 ms → STATE read-back ≤5 s lifecycle incl. pulse-mode rules, bus-load budget, per-node keys and signed CFG/OTA, N2K coexistence and vendor-firmware mapping, 17 conformance tests) and X02 Studio configuration schema (signed bundle/manifest with rollback, twelve top-level objects with field tables, channel/input types and protection fields, binding kinds, guardrails G-nn as validation constraints, permissions, capability discovery, deployment pipeline incl. standalone Air Hub, worked JSON examples). Added Level-2 design annexes for Core (power tree, per-tier switch stages, current-sense chain, pin budgets on S32K148/S32K314, DEUTSCH/AMPSEAL pinouts, thermal derating, protection-loop and pulse-mode firmware, EOL, BOM skeleton), Hub (SOM carrier power tree with LTC3350 hold-up, interface map incl. isolated J1939 via MCP2518FD + ISO1042, plug-in radio header, RAUC/AHAB secure boot chain, services), Sense (per-mode AFE with accuracy budget, MAX22190 DI wiring, isolation options, alarm engine, calibration) and Key (keymat/LED stack-up, LP5024 current budget, two-rail decision, per-key state machine), plus the AC board interface and commissioning pack (terminal schedule template, coil/feedback interface tables, transfer topologies, Studio mapping, commissioning checklist, handover contents, responsibility matrix). All files are bilingual and aligned; index files gained Foundations and Design-annex sections and the Level-1/Level-2 rule; Level-1 headers point to their annexes. No governing value changed. Waves 2 (Air switch/gateway annexes, Mate data model, Eye integration) and 3 (Tag) remain recorded in PLAN-029.

2026-08-29 20:19 [progress]

Claimed PROD-007 and drafted PLAN-030 to define the AC-16 reference AC board (capability envelope, YBO-side channel/input/RS-485 budget, standard BOM and enclosure sizing, AC-8/AC-24 scaling rule) as a Level-2 file under P04. No controlled document changed pending approval.

2026-08-29 21:20 [decision]

Completed PROD-007 and PLAN-030. Added the AC-16 reference AC board (bizplan/product/P04-ac-board-16.md / .md) as the sized baseline for quoting and the demo boat: 3 interlocked sources with EU 16 A / 32 A shore-inlet variants and a US region row, 16 branch circuits on 2P latching relays behind 2P MCBs with a diversity table, three-layer sensing (Accuenergy AcuRev 2100 for 16 + 2 circuits, 3 per-source meters, auxiliary contacts on all 16 branches), the YBO-side budget (one Core S as the AC node using all 22 channels; 24 digital inputs via 3× Sense 8+8 or 1× Core M with a critical-only sub-variant; RS-485 4-slave poll cycle ≈ 0.64 s at 9600 bit/s), a standard BOM with datasheet-cited DIN widths summing to ≈ 127 modules and a 6 × 24-module enclosure class (t), terminal-schedule counts, Studio mapping, the AC-8 / AC-24 scaling rule, cost classes, verification additions and desk decisions. P04 Level-1 gained the reference-board header line and variants row; PRODUCT-PLAN §P4 commercial row names AC-16 as the quoting baseline (t); index files list the board next to the commissioning pack. No YBO AC hardware SKU is created.

2026-08-31 10:25 [progress]

PLAN-029 wave 2 approved and started: Level-2 design annexes for the Air switch and Air Hub, the Mate data model and the Eye integration profile, bilingual. PROD-006 reopened to in_progress.

2026-08-31 12:10 [decision]

Completed PROD-006 wave 2 under PLAN-029. Added four bilingual Level-2 files to bizplan/product/: the Air switch design annex (event-based battery arithmetic with CR2450 pulse-capacitor sizing, EnOcean ECO 200 kinetic energy budget, NT3H2111 NFC commissioning tag, radio/pairing state machines, per-profile RF production tests), the Air Hub design annex (per-mode power budget defining the listen-standby state and recommending the LMR36510 1 A buck, pSemi PE4259 RF switching and the antenna/co-location plan resolving the fourth-radiator decision, standalone/system mode state machine, N2K PGN and Modbus register mappings, ESP-IDF dual-OTA plus coprocessor update flow, desense test matrix), the Mate data model and API annex (entity tables on a single vessel timeline, device identity and onboarding including the Hub-less gateway, MQTT topic/QoS scheme with command expiry and idempotency, REST surfaces, alarm and automation schemas, retention and GDPR classes) and the Eye camera integration profile (blessed-camera ONVIF/RTSP requirements with the ONVIF Profile S end-of-conformance date verified, discovery/provisioning, clip pipeline with the full-clip/snapshot/text upload ladder, NPU model contract, camera whitelist test protocol, PoE accessory checks). Level-1 headers and both index files now link all wave-2 annexes. Package checks and pair alignment pass; no governing value changed. Wave 3 (Tag design annex) remains recorded in PLAN-029.

2026-08-31 12:20 [progress]

PLAN-029 wave 3 started and extended on user direction to cover every product: Tag design annex, Studio application-architecture annex and a short View concept design brief, bilingual. PROD-006 reopened.

2026-09-01 21:57 [decision]

Completed PROD-006 wave 3 and closed PLAN-029: every product now has a Level-2 file in bizplan/product/. Added the Tag design annex (per-state power budget for sleep/armed heartbeat/alert burst/GNSS, nRF54L15 + SX1262 with an SX1261 EU population option, immersion-electrode geometry and comparator rules for salt and fresh water, wristband antenna detuning rule, IP68 seal and 8-bay dock concept, alert/heartbeat/pairing state machines with the gateway miss-count policy, RF and immersion production tests, decisions on EU-868 sub-band, US-915 access method and charging), the Studio application-architecture annex (offline-first PWA modules, validation pipeline with X02 guardrail codes, deploy state machine confirmed through X01 CFG STATUS with the standalone gateway path, controlled document generation, virtual-boat simulator scope, new-build production mode, signing keys and permissions, local store and N = 10 cloud versions) and the View concept design brief (pre-trigger only: N2K LEN and backlight arithmetic from the Riverdi 7" and 10.1" datasheets, buy-vs-build option table, Hub software reuse) — all bilingual and aligned. Level-1 headers and both index files link the new files; the index wave note states that all products are covered. Package checks and pair alignment pass; no governing value changed. Outstanding: PLAN-024 (46-channel platform) remains a draft awaiting approval.

2026-09-07 14:17 [progress]

Completed the source-collection investigation for conventional yacht electrical circuits up to 24 m. Added bizplan/research/yacht-circuit-source-catalog.md, ten archived PDFs, a 52-page selected-drawing pack containing 45 source pages, provenance/checksum and page-map files, and an Oceanis 361 pilot panel schedule. Six core vessel samples span approximately 7.4–22.6 m; incomplete/mislabeled mirrors and source conflicts are explicitly qualified. Original-file integrity, extracted-page mappings, local links, table structure and git diff --check passed. Vessel-wide circuit/input analysis and controlled specification changes remain outstanding under yacht-circuit-evidence-20260907T1402Z; existing product specifications and pending RESEARCH-008 / PLAN-024 were not changed.

2026-09-07 16:47 [progress]

Completed the approved yacht-circuit quantitative analysis and concrete specification proposal. Added a 251-record circuit inventory, panel summaries, input-budget scenarios and source-domain inventory, plus bizplan/research/yacht-circuit-demand-analysis.md. Reconciled protection classes and shared paths, preserved Lagoon/Bertram source conflicts, and proposed revised S/M current mixes, S16 DI, explicit supply-domain counting and parameterized AC reference designs. New capacities remain engineering targets; controlled product specifications and PLAN-024 are unchanged pending proposal review. CSV arithmetic, current-class allocation screens, archive integrity, local links, Markdown tables and git diff --check passed.

2026-09-07 16:58 [progress]

Delivered the requested optimized yacht-module architecture in bizplan/research/yacht-optimized-module-solution.md. Recommended one common Core 22 power/control design (6×30 A + 16×15 A, 24 DI, one DC supply domain, 100 A aggregate qualification target) plus Sense 8+8, with explicit retained essential/heavy circuits and SELV-only AC control. A reproducible standard-library calculation assigns all 151 selected DC paths: 120 outputs across nine proposed nodes and 31 external paths. Six candidate strategies expose node-count, utilization and additional-design tradeoffs; no universal cost optimum or thermal qualification is claimed. Source conservation, channel/current-class and reserve checks, AC budgets, CSV/table structure, local links, archive integrity and git diff --check passed. This refines the proposal; controlled product specifications and pending PLAN-024 are unchanged.

2026-09-07 20:32 [progress]

Refined the optimized yacht-module proposal for the explicit lighting-PWM versus ordinary-ON/OFF requirement. The 22-output target now separates eight PWM-capable positions (2×30 A + 6×15 A) and fourteen switch-only positions (4×30 A + 10×15 A). Updated the allocation calculator and CSVs to qualify proposed output modes: 27 PWM lighting groups and 93 steady supply groups across nine nodes. Corrected the previous inability to allocate three 20 A lighting branches to the low-current-only PWM bank. Defined steady-switch reuse, distinct one-shot coil commands, lamp-interface compatibility and lighting grouping limits. Corrected allocation, source identity, reserves, local links, Markdown tables and git diff --check passed. This updates the solution proposal only.

2026-09-07 20:46 [progress]

Updated the current yacht distribution proposal to the user-preferred specialized family: Light8 PWM, Switch16 ON/OFF, Sense8+8 acquisition and optional Control24 SELV interfaces. Added bizplan/research/yacht-modular-distribution-solution.md, a reproducible allocation script and three CSV schedules; marked the common-Core proposal as a historical alternative. The same 151 selected paths reconcile to 27 lighting, 93 ordinary and 31 retained external paths. Nine Light and nine Switch modules provide 216 positions; increased node count, one remaining S358 helm switch position and high-current spare limits are explicit. Channel/mode/current checks, path conservation, CSV structure, document links/tables, AC resource arithmetic and git diff --check passed. Controlled product specifications and pending platform decisions were not changed.

2026-09-07 20:58 [progress]

Reopened yacht lighting sizing after the user challenged eight-channel capacity and extended source research through 50 m. Added five builder-authored PDFs totaling 174 pages, a 28-page electrical/lighting extract pack, provenance/checksum/page-map records, 37 verified local lighting-function records and an explicitly synthetic three-cabin design budget. S358 operation text identifies 11 illumination/backlight groups; two older Bertram cabin sheets show 23 local switched groups behind two referenced feeds. Prior feed-level PWM allocations are now marked insufficient to freeze Light8 sizing. Full 45–50 m dimmer/circuit schedules remain unavailable; briefs are not presented as wiring diagrams. Archive hashes/page counts, page mapping, CSV arithmetic and links/tables passed. Extract review found 24 pixel-identical low-resolution renders and four Azimut pages with at most 1/255 sample differences. Text differs only in soft-hyphen normalization and ARK displacement-symbol extraction; the ARK page renders match. These extraction limitations do not affect the cited circuit counts. git diff --check passed. Controlled product specifications remain unchanged.

2026-09-07 23:25 [progress]

Refined the yacht distribution design to two 24-output / 125 A aggregate targets: Light24 (20×5 A + 4×10 A PWM) and Switch24 (8×5 A + 12×15 A + 4×30 A ON/OFF). Added bizplan/research/yacht-24-channel-125a-power-spec.md and marked the earlier Light8/Switch16 sizing as historical. Defined a proposed continuous thermal qualification condition, single-source supply and external load-return arrangement, 24 DI, concurrent-load examples and protection coordination. Verified arithmetic, local links, Markdown tables and git diff --check; hardware performance and whole-vessel fit remain unvalidated. Controlled product specifications remain unchanged.

2026-09-07 23:33 [progress]

Added the vehicle PDM product-family proposal and two CSV matrices: PDM-L24-125, PDM-S24-125, PDM-S28-200, IO-D16 and IO-A8D8. The 28-output / 200 A mix adds four 30 A outputs to S24 while retaining 24 local DI. Documented independent feed/aggregate-current limits, the 200 A thermal-path distinction, CAN wiring and protocol profiles, remote-input validity and local execution, shared pulse-input accounting and an eight-node qualification target. Identified the current Sense publication/binding gap rather than claiming existing plug compatibility. Channel, current, expansion, loss and traffic arithmetic plus document links/tables and git diff --check passed. Physical vehicle and timing qualification remain outstanding; controlled marine specifications are unchanged.

2026-09-07 23:39 [progress]

Applied the user-selected split vehicle PDM architecture: COM-M handles communication and normal cross-module rules; power satellites retain local protection/PWM/inhibit; IO-D16 and IO-A8D8 acquire signals. Added the architecture document and controller CSV, updated power/IO matrices and marked the integrated proposal as historical. Power modules now have zero ordinary DI and one CAN interface; COM-M has two CAN interfaces and a separate wake input. The example input count changes from 64 DI to 40 DI, retaining 8 AI. Verified current/channel and input arithmetic, dedicated-pin accounting, links/tables and git diff --check. Physical hardware, firmware and revised bus timing remain unvalidated.

2026-09-08 01:38 [progress]

Expanded COM-M specifications to three independent CAN interfaces, one RS-485, one RJ45 10/100 Ethernet target and one internal SPI expansion bus with two chip selects, retaining USB and dedicated wake. Proposed four M12 communication receptacles; distinguished connector coding from protocol/pinout compatibility. Split internal power and input traffic onto CAN2/CAN3 and updated the architecture diagram, controller CSV, source references and timing/fault requirements. Interface arithmetic, unchanged power/input resources, local links/tables and git diff --check passed. Electrical implementation and physical qualification remain outstanding.

2026-09-08 01:46 [progress]

Committed the existing yacht/PDM evidence and split-module specifications as cd6e87f on user request, retaining unrelated product work outside the commit. Normalized CSV line endings and generator output, refreshed archive checksums and verified reproduction/whitespace. Subsequently reviewed the attached S32K148 Distributed I/O Implementation Guide v0.2 in bizplan/research/s32k148-distributed-io-guide-review.md: retain CAN for ordinary modules, evaluate dedicated UART for optional fast 8 DI / 8 DO, resolve native-UART versus RS-485/USB resource conflicts, and keep conditional 10 microsecond timing distinct from full PDM/PWM updates. CRC and timing arithmetic, links/tables and whitespace checks passed; physical validation remains outstanding.

2026-09-08 01:52 [progress]

Added the S32K314 / 50 MHz LVDS attachment review. Compared its ten-node/3 m scope with the previous UART guide; checked NXP SPI limits, Lattice resource/order tables and TI high-side delay. Recalculated wire/host/diagnostic budgets and documented remote-MCU selection, return-clock, logic-fit and connector constraints. Recommended retaining the selected CAN PDM family with optional fast-I/O evaluation, including a 640-first prototype preference before cost reduction. Report links/tables and git diff --check passed. Module matrices are unchanged; no RTL, physical validation or new commit.

2026-09-08 02:03 [progress]

Refined the intelligent-PDM research for the vehicle PDM family. Added bizplan/research/pdm-industry-landscape.md (taxonomy of six PDM classes; 2025 demand volumes for China buses, off-highway, RV, US aftermarket and world vehicle production; five supplier tiers with Senptec's 2024 segment revenue as the only public pure-play data point; silicon, architecture, networking and protection trends; a standards and approvals map incl. JT/T 1512-2024, ECE R10, ISO 16750-2:2023, UN R155, ISO 13766/14982, NMEA 2000 and ABYC E-11-2025; procurement and price bands; positioning and six open decisions) and bizplan/research/pdm-vendor-product-benchmark.md with data/pdm-vendors/product-matrix.csv (62 rows: 53 vendor products from official datasheets fetched 2026-09-08 or carried from 06a/06b, 3 Tier-1 indicators, 6 YBO reference rows). Key findings: no benchmarked product combines 24-28 outputs, a 5 A tier, zero local inputs and one CAN; S28-200 sits next to Hardwire PDM28; L24-125's 125 A aggregate on a 140 A nameplate is far more generous than any lighting analogue; CAN FD appears only in four shipping products; public prices cluster at USD 45-105 per output. Corrected 06a on Bosch PBX 190 (5-16 V supply, separate 48 V bank) and Infinitybox NGX (100 A). Added pointer lines to 06/06a/06b. Verified table structure, local links, CSV shape, cited-URL reachability and git diff --check. No controlled product specification changed.

2026-09-08 03:47 [progress]

Integrated the authorized optional S32K314/LVDS prototype route into the main split-module architecture and controller/I/O matrices. Added COM-M-F and FIO-D16O16 working designations, retained all CAN-family ratings and main interfaces, separated logic-host SPI from expansion SPI, and defined ten-link/3 m targets, timing and freshness boundaries, unresolved remote/current selection, and staged prototype acceptance. Verified CSV/interface/channel arithmetic, timing calculations, local links, table structure and git diff --check. Hardware qualification remains open; no new commit.

2026-09-08 04:07 [progress]

Added per-vendor PDM product catalogues under bizplan/research/vendors/ (index plus 26 files: Axiomatic, E-T-A SCS, Enovation Controls, Carling, Trombetta/SMP, Infinitybox, Blink Marine, Würth ICS, MRS, HED, Hardwire, MoTeC, ECUMaster, AiM, Cosworth, Life Racing, HP Electronik, Bosch Motorsport, MaxxECU, Link, Haltech, AEM, Racepak, Switch-Pros, Senptec, Eco-EV). Each file lists the vendor's product families with part numbers and public specifications from official pages and text-extracted datasheets, purchase model and public prices, protocol and tool openness, and relevance to the YBO vehicle PDM family; marine platforms stay in 04a–04e. Added a vendor_file column to data/pdm-vendors/product-matrix.csv and pointer lines in the benchmark, landscape and 06 series. Corrected the Infinitybox POWERCELL NGX aggregate rating to 125 A per the official pages (the earlier 100 A figure came from a search summary) in the CSV, benchmark tables and 06a erratum. Later waves (remaining Chinese, off-highway, marine and off-road vendors) are listed in the index. Verified Markdown tables, local links, CSV shape, cited-URL reachability and git diff --check. No controlled product document changed.

2026-09-08 17:48 [progress]

Added bizplan/research/air-key-vendor-landscape.md, a category-level list of vendors and existing products for the Air Hub, Air Switch and Key lines: wireless gateways (marine digital-switching bridges and EnOcean receivers, NMEA 2000 Wi-Fi/Ethernet gateways, monitoring hubs with sub-GHz sensors, BLE and proprietary MOB receivers, docking/thruster remote receivers, vehicle and RV app bridges, LoRaWAN/BLE/433 MHz/multi-radio IoT gateways and the open-source OpenMQTTGateway precedent), wireless switches (EnOcean, ZF, Scheiber, Linptech and other kinetic lines; Shelly, Flic and Cucumber coin-cell buttons; Lutron Pico, Dockmate, Sleipner, FELL and ACR sub-GHz/BLE fobs; LoRaWAN buttons) and keypads (CZone, EmpirBus, Raymarine RMK-6, Maretron, E-T-A discontinued line, Naviop, Blink; Grayhill, EAO, APEM, HED, Murphy SK51 off-highway; motorsport rebrands traced to Blink and Grayhill; SonnePower as the first Chinese J1939/CANopen keypad line). Findings: kinetic switching is an EnOcean ecosystem outside Scheiber and Linptech; regional proprietary sub-GHz links are normal on boats; no marine product combines BLE, 433 MHz and LoRa in one head; keypad supply is concentrated on Blink Marine and Grayhill. Added a pointer in bizplan/research/vendors/index.md. Verified tables, local links, cited-URL reachability (bot-blocked and two unreachable vendor sites noted in the document) and git diff --check. No controlled product document changed.

2026-09-08 19:40 [progress]

Reorganised the Air/Key vendor research per category and per vendor on the user's instruction: added bizplan/research/air-key-vendors/ with index.md and 38 vendor catalogue files in gateway/ (19: Yacht Devices, Actisense, Digital Yacht, ShipModul, Rose Point, Siren Marine, ACR OLAS, FELL Marine, Dockmate, Sleipner, Lumitec, Milesight, RAKwireless, Dragino, Cassia, Minew, RFXCOM, Athom Homey, Theengs/OpenMQTTGateway), switch/ (10: EnOcean, ZF, Scheiber, Linptech, ILLUMRA, Shelly, Flic, Lutron, Cucumber, YoLink) and keypad/ (9: Grayhill, EAO, APEM, HED, Enovation Controls SK51, Raymarine RMK-6, SonnePower, Intellitec, ECUMaster). Each file follows the vendors/ section order (company, product families with part numbers and quoted specifications, purchase model and prices, openness, relevance to YBO, sources); multi-category vendors are cross-listed; CZone, EmpirBus, Maretron, E-T-A, Victron and Blink Marine are pointed to in 04a–04e and vendors/. The single-file landscape stays as the category overview and links to the folder; vendors/index.md pointer updated. Verified table structure, local links, cited-URL reachability (bot-blocked and one TLS-failed vendor site stated in the files) and git diff --check. No controlled product document changed.

2026-09-08 20:18 [progress]

Added a bilingual VitePress documentation site over the existing documents (task and plan 20260908-1951-docs-site). VitePress 1.6.4 runs at the repository root with srcDir: '.', rendering bizplan/ and docs/ in place; *.md files are rewritten to /… routes, a markdown-it rule re-targets relative links against the real source directory so cross-language and CSV/PDF/script links survive the rewrite, and sidebars are generated per locale from the file tree and H1 titles with (中文) / (EN) markers for pages that exist in only one language. Local search uses a CJK-bigram tokenizer and one shared index for both locales; Mermaid fences render through vitepress-plugin-mermaid; buildEnd copies the linked data and source files into the output. Raw HTML is disabled in Markdown because one tracking record contains an unclosed placeholder tag. Verified: build with dead-link checking (247 pages), browser checks of home pages, locale menu, sidebars, Chinese and English search, Mermaid SVG and asset routes, and git diff --check. No document under bizplan/ or docs/task, docs/plan changed; .gitignore now excludes node_modules/ and VitePress cache/dist.

2026-09-08 20:38 [progress]

Pruned every completed task and plan record on the user's instruction (task and plan 20260908-2038-prune-tracking-records) and rebuilt docs/task/index.md and docs/plan/index.md on the canonical PMA index templates. Retained: REPO-001 and RESEARCH-008 / PLAN-024 (pending) and the in-progress yacht-circuit-evidence-20260907T1402Z pair owned by another session. The RESEARCH-008 dependency line now notes that PLAN-023 was completed and pruned. Full content of the pruned records remains in git history before this commit; the IDs and titles are preserved here.

Pruned tasks (34):

• BIZ-001 — Resolve business-plan P0 findings
• BIZ-002 — Define target customers and vessel-size envelope
• BIZ-003 — Maintain internal completion checklist
• BIZ-004 — Refactor the business-plan problem statement
• PROD-001 — Define supplier-neutral regional radio profiles
• BIZ-005 — Consolidate and map the business-plan problem statement
• BIZ-006 — Establish refit and new-build dual-entry positioning
• BIZ-007 — Reorganize the business-plan solution section
• BIZ-008 — Prioritize market scope and qualify competition claims
• BIZ-009 — Clarify 8–50 m refit coverage
• BIZ-010 — Create the internal PPT build guide
• BIZ-011 — Reconcile tracking records with unified refit coverage and own-brand front-fit
• BIZ-012 — Add an AC integration and automation solution to the planning package
• BIZ-013 — Add AC current and AC presence/voltage sensing as system feedback
• RESEARCH-001 — Document the marine digital-switching benchmark product matrix
• BIZ-014 — Restate YBO AC as a sense-and-control-only boundary
• BIZ-015 — Specify the AC control and sensing interface
• RESEARCH-002 — Certification requirements for consumer-class non-core equipment on yachts of 24 m and above
• RESEARCH-003 — Document global suppliers comparable to Senptec intelligent PDMs
• RESEARCH-004 — Preserve the full public inventory of Chinese intelligent-PDM suppliers
• RESEARCH-005 — Explain marine versus automotive power-distribution architectures
• RESEARCH-006 — Document open high-current PDM and PCB references
• RESEARCH-007 — Write an independent high-current PDM and BTH50015 report
• PROD-002 — Specify the Air and Key human-interface product lines
• PROD-003 — Replace the single-profile Air bridge with a tri-radio Air Hub (BLE + 433 MHz + LoRa)
• PROD-004 — Make YBO Air a standalone product system with an ESP32-C5-hosted gateway
• PROD-005 — Build the per-product specification package under product/
• PROD-006 — Deepen the product package: cross-product foundations and Level-2 design annexes
• PROD-007 — Define the AC-16 reference AC board capability envelope
• pdm-industry-vendor-research-20260908T0141Z — Refine the PDM industry research and vendor product benchmark
• pdm-vendor-catalogues-20260908T0348Z — Write per-vendor PDM product catalogue documents
• 20260908-1736-air-key-vendor-landscape — List vendors and existing products for the Air Hub, Air Switch and Key categories
• 20260908-1926-air-key-vendor-catalogues — Write per-vendor catalogue files by category for wireless gateways, wireless switches and keypads
• 20260908-1951-docs-site — Build a bilingual VitePress documentation site over the planning, product and research documents

Pruned plans (34):

• PLAN-001 — Resolve business-plan P0 findings
• PLAN-002 — Define target customers and vessel-size envelope
• PLAN-003 — Maintain internal completion checklist
• PLAN-004 — Refactor the business-plan problem statement
• PLAN-005 — Define supplier-neutral regional radio profiles
• PLAN-006 — Consolidate and map the business-plan problem statement
• PLAN-007 — Establish refit and new-build dual-entry positioning
• PLAN-008 — Reorganize the business-plan solution section
• PLAN-009 — Prioritize market scope and qualify competition claims
• PLAN-010 — Clarify 8–50 m refit coverage
• PLAN-011 — Create the internal PPT build guide
• PLAN-012 — Reconcile tracking records with unified refit coverage and own-brand front-fit
• PLAN-013 — Add an AC integration and automation solution
• PLAN-014 — Add AC current and presence sensing as system feedback
• PLAN-015 — Document the marine digital-switching benchmark product matrix
• PLAN-016 — Restate YBO AC as a sense-and-control-only boundary
• PLAN-017 — Specify the AC control and sensing interface (latching relays, pulse drive, three-layer sensing)
• PLAN-018 — Write the ≥24 m non-core equipment certification research report
• PLAN-019 — Document the global intelligent-PDM supplier landscape
• PLAN-020 — Preserve the full public inventory of Chinese intelligent-PDM suppliers
• PLAN-021 — Explain marine versus automotive power-distribution architectures
• PLAN-022 — Document open high-current PDM and PCB references
• PLAN-023 — Write an independent high-current PDM and BTH50015 report
• PLAN-025 — Specify the Air and Key human-interface product lines
• PLAN-026 — Replace the single-profile Air bridge with a tri-radio Air Hub (BLE + 433 MHz + LoRa)
• PLAN-027 — Make YBO Air a standalone product system with an ESP32-C5-hosted gateway
• PLAN-028 — Build the per-product specification package under product/
• PLAN-029 — Deepen the product package: cross-product foundations and Level-2 design annexes
• PLAN-030 — Define the AC-16 reference AC board capability envelope
• pdm-industry-vendor-research-20260908T0150Z — Refine the PDM industry research and vendor product benchmark
• pdm-vendor-catalogues-20260908T0348Z — Write per-vendor PDM product catalogue documents
• 20260908-1737-air-key-vendor-landscape — List vendors and existing products for the Air Hub, Air Switch and Key categories
• 20260908-1926-air-key-vendor-catalogues — Write per-vendor catalogue files by category for wireless gateways, wireless switches and keypads
• 20260908-1951-docs-site — Build a bilingual VitePress documentation site over the planning, product and research documents

2026-09-10 01:06 [progress]

Added a manually dispatched GitHub Actions workflow that builds the VitePress site with Bun and deploys it to Cloudflare Workers static assets (wrangler.jsonc, assets-only, no Worker script). GitHub Pages was rejected because ybolab/docs is private under a free organisation plan; Cloudflare Pages was rejected because Cloudflare now directs new static sites to Workers. copyAssets now skips source files above the 25 MiB Workers asset limit, which excludes the Bertram 43 and Bertram 700 owner manuals from the published site while leaving them in the repository.

2026-09-10 01:16 [decision]

Completed 20260909-2355-manual-pages-deploy. Run 34424708536 published the site to https://ybo-docs.cfaa.workers.dev (663 assets). Smoke-tested: English and Chinese entry pages, a clean-URL content page, a PDF asset, and the 404 fallback all respond as expected. The site is served publicly without authentication, unlike the private source repository.

2026-09-10 01:46 [decision]

Completed 20260910-0135-product-tree-and-sidebar and landed steps 1 and 3 of 20260910-0137-chinese-first-docs. The corpus is now Chinese-only except bizplan/BUSINESS-PLAN.en.md: 35 English originals were replaced by their Chinese mirrors, 15 Chinese-only files lost the .zh suffix, and 473 .zh.md references were repointed. bizplan/product/ gained one directory per product line (core/, sense/, hub/, ac/, air-hub/, air-switch/, key/, studio/, mate/, view/, eye/, tag/, shared/) with filenames unchanged, so the ~1450 bare cross-references stay valid. The sidebar was removed in favour of index pages; bizplan/index.md and bizplan/research/index.md were added, and product/index.md rewritten per product line. .vitepress/sidebar.mts and .vitepress/links.mts were deleted along with the locale, rewrite and shared-search-index configuration. Remaining: 82 English research files await translation.

2026-09-10 02:17 [progress]

Translated batch 1 of 20260910-0137-chinese-first-docs: the 13 English research reports at the root of bizplan/research/ are now Chinese. Company names, model numbers, standards, interface names, units, tables, figures and link targets were preserved verbatim. Remaining: 27 files in research/vendors/ and 39 in research/air-key-vendors/.

2026-09-10 02:37 [decision]

Completed 20260910-0137-chinese-first-docs. Batches 2 and 3 translated the 27 PDM vendor catalogues and the 39 Air/Key vendor catalogues, finishing the Chinese-first conversion: every document under bizplan/ is now Chinese except BUSINESS-PLAN.en.md. 79 files were translated in total rather than the 82 estimated, because 01-market-size, 02-competitors and 03-certification-tech-trends were already Chinese without a .zh suffix. docs/ remains English per the user's decision.

2026-09-10 04:09 [decision]

Completed 20260910-0347-breadcrumb-navigation. Every page now renders a breadcrumb above its content (首页 / 商业与产品 / 产品规格 / YBO Core / P01-core), with every ancestor clickable. This required 17 new index pages — the 13 product-line directories, the three air-key-vendors/ category directories and docs/ — so no level is a dead label. .vitepress/config.mts builds the label map from the file tree at build time, reading each directory's index.md frontmatter title or H1, and a new .vitepress/theme/ injects the component into the default theme's doc-before slot. The 13 product pages are also where per-product documents are listed as they are added.

2026-09-10 04:59 [progress]

Claimed 20260910-0455-documentation-organization and prepared 20260910-0459-documentation-organization to improve documentation navigation and consistency. The investigation found 428 unresolved explicit relative paths, 52 broken rendered fragment links, two catalog links to deliberately unpublished PDF assets, obsolete language/architecture descriptions, and three completed plans with pending index markers. The existing locked-dependency build passed. Implementation awaits review of the file-level proposal; product/research content and active research ownership are unchanged.

2026-09-10 05:52 [progress]

Approved and started 20260910-0459-documentation-organization under task 20260910-0455-documentation-organization. The implementation covers navigation, reference repairs, publication notes, and tracking consistency while preserving technical claims and research decision boundaries.

2026-09-10 06:04 [decision]

Completed 20260910-0455-documentation-organization and 20260910-0459-documentation-organization. Simplified the product and Air/Key parent indexes while retaining detail inventories, added reading routes, distinguished current research from historical alternatives, and corrected repository/site guidance. Repaired 413 relative paths, 15 retired-plan references, and 52 fragment links; removed 27 obsolete mirror headers and added 55 companion-header links. Clarified repository-only storage and publisher downloads for the two oversized Bertram manuals.

Reconciled the index markers for 20260910-0135-product-tree-and-sidebar, 20260910-0137-chinese-first-docs, and 20260910-0347-breadcrumb-navigation with their completed details and existing delivery entries; historical records and active research ownership were preserved. Final build, scans of 174 rendered HTML pages and 5,683 internal link occurrences, content-preservation comparisons, inventory/state checks, local diff review, and git diff --check passed. No missing internal destinations/fragments or unreachable content pages remain. A diagram reference-format issue detected during verification was fixed. Existing build-size warnings remain; no executable code, dependency, data, archive, technical claim, commit, push, or deployment change.

2026-09-10 07:17 [progress]

Claimed 20260910-0714-distributed-core-product-family and drafted 20260910-0717-distributed-core-product-family for the requested distributed Core redesign with 27/43 outputs, ten configurable inputs, CAN/RS-485 and 18 PWM outputs. Output-count arithmetic is consistent; aggregate module currents, lighting/general-load role mapping and PWM channel allocation are not yet defined. The proposal identifies controlled-document and integration dependencies without transferring old-family ratings or commercial assumptions. No controlled product or research source document was changed.

2026-09-10 07:22 [progress]

Revised 20260910-0717-distributed-core-product-family after the user confirmed that both 27/43-output products are general-purpose models and changed the requirement to 15 PWM outputs per model with configurable switching. The exact PWM channel map and fixed-versus-selectable allocation remain open engineering decisions. Updated task dependencies and removed the unresolved role/PWM-count questions; implementation approval remains pending. Controlled product documents are unchanged.

2026-09-10 07:24 [progress]

Updated 20260910-0717-distributed-core-product-family to lock each model's 15 PWM-capable outputs to a fixed subset of its 15 A bank. Those outputs can be configured for PWM or ordinary on/off operation; the remaining 15 A outputs are on/off-only, three on the 27-output model and nineteen on the 43-output model. Higher-current outputs remain on/off-only. Recorded configuration constraints and verified the unchanged physical output totals. Physical channel numbering and proposal approval remain pending; controlled product documents are unchanged.

2026-09-10 07:27 [progress]

Claimed 20260910-0724-air-key-product-specifications and drafted 20260910-0727-air-key-product-specifications for collaborative Air Switch, Air Hub and Key specification definition. Reviewed current product targets and identified feedback/battery, kinetic capability, Modbus role, gateway power/sleep, Key night-mode and Core interface dependencies. Requested the standalone launch decision before selecting integration scope. Existing Core and yacht-research ownership and controlled product documents are unchanged.

2026-09-10 07:32 [progress]

Revised 20260910-0727-air-key-product-specifications following the requested open multi-protocol gateway direction: BLE, Matter, 433.92 MHz and an unresolved "818" frequency. Added proposed switch/remote/sensor intake, separate Matter controller/bridge/Thread-router roles, radio coexistence constraints and protocol-specific capacity/state qualification. Requested frequency and launch-geography clarification; no regional profile, universal compatibility, unlimited capacity or controlled specification change was assumed.

2026-09-10 07:36 [progress]

Updated 20260910-0727-air-key-product-specifications for the requested Europe/China/North America market coverage. Replaced the unresolved 818 MHz placeholder with a regional 868/915 MHz proposal and recorded China's distinct 433.92 MHz and 868-868.6 MHz remote-control conditions. Added official references, separate country qualification and a common-platform proposal without inheriting global transmit permissions or universal terminal compatibility. Controlled product specifications remain unchanged.

2026-09-10 07:42 [progress]

Revised 20260910-0727-air-key-product-specifications around the requested bidirectional encryption, anti-copy behavior and simpler Air lineup. Proposed BLE-only owned switches as the simplest regional hardware family, with 433.92 MHz for Europe/China and 902-928 MHz for North America as an alternative when installed coverage warrants it. Removed owned 868 MHz from the proposal baseline, separated optional gateway compatibility, and specified authenticated enrollment, per-device keys, replay prevention, retry deduplication and confirmed actuator results. No transport approval or controlled specification change was assumed.

2026-09-10 07:47 [progress]

Refocused 20260910-0727-air-key-product-specifications after the user clarified that Gateway primarily pairs with owned Air. Proposed existing Key as the four-conductor powered CAN option, Air as the wireless alternative and staged broader gateway protocols separately. Recorded provisional battery-service goals and reproducible current-budget arithmetic, with explicit capacity/test assumptions, plus the existing X01 unencrypted/unauthenticated-readback limitations relevant to the new security requirement. Controlled specifications and separately owned tasks remain unchanged.

2026-09-10 08:19 [decision]

Recorded the user's Air/Key security boundary in 20260910-0727-air-key-product-specifications: CAN requires no encryption; the objective is preventing unauthorized wireless control through Air. Superseded the proposed CAN security extension, preserved existing CAN behavior and specified Gateway admission checks for authenticated pairing, permitted actions, replay rejection and encrypted wireless results. Transport selection remains under discussion; controlled product specifications and separately owned tasks are unchanged.

2026-09-10 09:00 [decision]

Completed the authorized supplier-document delivery for 20260910-0724-air-key-product-specifications and 20260910-0727-air-key-product-specifications. Added X03 Air/Key supplier requirements with 29 traceable requirements, ten verification groups, official component references, battery and timing budgets, wireless security, DFM/DFT, identity provisioning, EOL/traceability, source-file deliverables, staged acceptance and quotation requirements. Rewrote all six Air Switch, Key and Gateway specifications/design appendices in Chinese and reconciled P5/P6 governance, open questions, navigation and scoped protocol/Tag dependency notices.

The quotation baseline recommends nRF54L15 BLE Air, powered four-conductor CAN Key, and a focused owned-Air Hub, with STM32G0B1CE recommended for the shared wired platform and TJA1463 retained for CAN SIC. Corrected Key RGB plus red/white legend channel budgeting, timeout/unknown-state behavior and unsupported telemetry claims. Broader radios, Matter, Tag and standalone third-party output remain separate expansion choices. CAN encryption was not added; final parts, radio coverage, battery-life claims and production release require the explicit supplier engineering gates.

Verification passed: whitespace, changed/new document paths and table consistency, requirement-to-test coverage, VitePress build, and 179 rendered pages with 5,730 internal links/anchors. Existing bundle-size and oversized research-PDF publication warnings remain. Core/Sense/Hub/AC product-plan sections and separately owned tasks were preserved. No firmware, fabrication, physical tests, dependency changes, commit, push or deployment.

2026-09-10 09:08 [decision]

Corrected supplier-guide placement as requested: the former combined X03 guide in shared/ is now split into air-switch/P05-air-supplier-guide.md and key/P06-key-supplier-guide.md. Air includes its Gateway; Key has its own complete requirements, chip selection, manufacturing, acceptance and quotation guide. Preserved all 29 common requirement IDs, with 22 applicable to Air and 13 to Key, including six shared IDs. Updated product inventories, governing/specification links and scoped X01/X02 references; shared/ retains protocol foundations. Product targets and hardware approval boundaries are unchanged.

Verification: all 29 original requirement IDs remain represented; each product guide maps its applicable requirements to existing test groups. The documentation build, 180 rendered pages and 5,775 internal links/anchors passed. Both product guides are published under their own product paths; the former shared guide page is absent. No commit, push or deployment.

2026-09-11 02:54 [decision]

Evaluated the Espressif ESP32-H2-MINI-1-H4S as an Air Switch platform and recorded the result in bizplan/product/switch/P05-air-switch-esp32h2-evaluation.md. The module is not adopted for the CR2450 Air: its 3.0 V supply floor sits above most of the cell discharge curve, the 0.35 A peak-supply requirement forces a reservoir whose leakage competes with the 15.22 uA three-year budget, its 7 uA deep-sleep current already consumes 46 percent of that budget, and it has no NFC for the recommended out-of-band pairing. It stays worth evaluating for the Gateway radio side, for wired or larger-battery Air variants, and as Thread/Matter prototype hardware. The recommended Air baseline remains nRF54L15; any reversal requires the measured evidence listed in the document and closure at gate D0.

2026-09-11 03:02 [BUG-P1]

Splitting X03-air-key-supplier-guide.md into air-switch/P05-air-supplier-guide.md and key/P06-key-supplier-guide.md replaced the token X03 globally, which corrupted data in five research documents: AX03… Axiomatic part numbers became A供应商指南… across 16 rows of research/vendors/axiomatic.md plus one row each in research/vendors/index.md, research/pdm-industry-landscape.md and research/pdm-vendor-product-benchmark.md, and the evidence row label X03 ARK 45 m became 供应商指南 ARK 45 m in research/yacht-lighting-demand-and-50m-evidence.md. All five files were restored and now match their committed content byte for byte; a repository-wide scan for 供应商指南 glued to a surrounding identifier returns nothing further. The split itself had no changelog entry; this records it.

2026-09-11 03:02 [progress]

Completed 20260911-0251-air-key-doc-consistency-repair and 20260911-0254-air-key-doc-consistency-repair, repairing what the Air/Key rewrite and guide split left inconsistent.

COMPLIANCE-MATRIX no longer scopes Air/Gateway as a Wi-Fi + BLE + 433 MHz + LoRa enclosure: the base product is assessed as one BLE 2.4 GHz radio plus a replaceable primary cell, with the multi-radio co-location assessment and the PGN 127502 NMEA 2000 obligation moved to the separately selected gateway expansion. Gateway NFC was reconciled with the guide's own OOB flow and the recommended silicon — the authorized tool reads the Air's dynamic OOB data, the base Gateway carries no reader (nRF54L15 provides NFC-A tag emulation only), so NFC left the Gateway structural row, EOL list, RF tuning paragraph and delivery list, and the open question moved into AIR-O-02.

Roughly thirty §n and FR-nn cross-references in X01, X02, Studio, Mate, Tag and four research files pointed into sections and IDs deleted by the rewrite; each now resolves to the section that carries the content, or to the expansion notice where the capability left the base scope. Two stale silicon statements this exposed in X01 were corrected: the device-key storage attribution no longer names ESP32-C5, and the trimmed-image rule no longer assumes a 128 KB KEY. Studio and Mate received the dated scope notice that X01, X02 and Tag already carried.

Namespaces were made unambiguous: the Air specification dropped its FR-nn aliases, its three unaliased rows became AIR-08 (dimming bound to PWM-capable channels), AIR-09 (optional double-click) and AIR-10 (retry with a reused transaction ID), and GW-05 now carries the Gateway four-wire supply, environment and branch-termination requirement. Open items are prefixed AIR-O-nn and KEY-O-nn across both guides, both specifications, the design appendices, the ESP32-H2 evaluation and OPEN-QUESTIONS. The split's unlinked "供应商指南" phrases became the linked short names Air 指南 and Key 指南, declared in each guide header. IF-01 now names the X01@2026-09-10 / X02@2026-09-10 baseline, which both base files now declare, instead of a frozen revision that does not exist, and each guide states that its sections 1, 2, 7, 8, 10, 11 and 12 are common clauses that must move together.

Verification: requirement-to-test mapping is bidirectional in both guides (Air 26 requirements / 9 tests, Key 13 / 6; a pre-existing gap where Key SYS-02 cited V-06 without V-06 listing it was closed), no §n or FR-nn cross-reference resolves to a missing section or ID, bun run docs:build and git diff --check pass. Existing bundle-size and oversized research-PDF warnings remain. Three product decisions were deliberately left open and reported instead of being decided here: the shared ≤60 mA@12 V ceiling for both Key models, whether the Gateway deep-sleep mode earns its cost, and whether the battery-versus-latency tradeoff should become an explicit AIR-O-01 criterion. No commit, push or deployment.

2026-09-11 19:50 [decision]

Created product line P09 YBO Control (working name) and completed 20260911-1930-control-platform-protocol-evaluation and 20260911-1933-control-platform-protocol-evaluation. bizplan/product/control/P09-control-protocol-evaluation.md evaluates Tuya, Matter, Thread, Zigbee, Z-Wave, HomeKit HAP, Home Assistant, plain MQTT conventions, KNX IoT and the ecosystem endpoints against three hard requirements — offline first, security isolation, local veto over remote — plus twelve derived requirements (CTL-01…12).

Recommendation, pending PRODUCT-PLAN §6 item 12: an owned local control core (Mate's ybo/v1/... MQTT topic model over mTLS on the boat broker), a Matter Bridge as the ecosystem exposure layer (bridge certified as one product; Air/Key/Core not made native Matter nodes), Home Assistant MQTT discovery as the first open integration, Thread only as a transport for third-party devices. Tuya (identity and activation owned by the Tuya cloud), Zigbee, Z-Wave, HAP and KNX IoT are not adopted as the platform. Recorded the structural limitation that a Matter or HA layer cannot tell an on-board phone from a command relayed through the ecosystem's cloud, so the helm lock can only refuse that layer as a whole and critical circuits are never bridged. Facts are dated 2026-09-11 with official URLs: Matter 1.6 (2026-06-17), CSA Adopter $7,500/yr and $3,000 per product, Zigbee 4.0/Suzi, Z-Wave 2026A, Thread 1.4, KNX IoT stack v1.0.0, EN 18031 and CRA dates.

Premise correction recorded in the document: the base Air receiver has no Wi-Fi or MQTT; those come from the P03 Hub or from the Air Hub direction in the unapproved plan 20260911-1919, so the document treats the local bridge abstractly. Also added the P09 row in product/index.md, the P9 section, T2 tier entry and §6 item 12 in PRODUCT-PLAN.md, and the P9 section (CTL-O-01…09) in OPEN-QUESTIONS.md. Air/Key/Gateway, Hub, Mate, Studio and X01/X02 documents are unchanged; CTL-O-04 records the follow-up to route Mate's remote switching through the Control policy point. No commit, push or deployment.

2026-09-11 19:53 [decision]

Completed 20260911-1916-air-key-hub-sleep-and-key-scaling and 20260911-1919-air-key-hub-sleep-and-key-scaling, applying the user's product decisions across the Air, Air Hub and Key package.

Bus. The YBO bus is now Classical CAN 2.0B at 500 kbit/s with an 8-byte payload limit; CAN FD is not used. X01's physical, data-link, bit-rate, conformance and desk-decision rows were rewritten, and a new §1.1 records that the existing §4 byte tables are the CAN FD layout: only ACK and the 8-byte HB variant fit, so CMD (16), STATE (12), TELEM (64), ALARM (16), AUDIT (32), CFG/OTA (64), the 12-byte HB and DIAG (64) all need re-layout. That re-layout — multi-frame transport, auth-tag placement and coverage, sequence and retry semantics, the §6 bus-load recomputation, the OTA block scheme and the CT-01 case — is tracked as X01-O-01, to be frozen before D1; it was deliberately not invented here. The bus rename propagated to Core, Sense, Hub, Key, View, Studio, Mate, Eye, X02 and the product plan; part-capability statements such as "S32K314 6× CAN FD", TJA1463 and MCP2518FD were left alone because an FD-capable controller runs Classical CAN.

Air Hub. The Air Gateway is renamed Air Hub and stays a separate device from the P03 Hub: air-gateway/ became air-hub/, both specification files were renamed, and the AIR-GW node class token became AIR-HUB across X01, X02, Studio, Mate, Tag and the research catalogue — 54 files. It no longer sleeps: the deep-sleep target row and mode were deleted and GW-04 now requires permanent Air reception whenever powered.

Air. ESP32-H2 replaces nRF54L15 as the first-version recommendation, and the cell changes from one CR2450 to two series AAA primary lithium cells, which resolves both battery blockers — 140–180 mΩ internal resistance keeps the 0.35 A pulse to about 0.1 V of droop with no bulk reservoir, and a buck-boost covers the full series range. The thickness target moved from ≤12 mm to ≤14 mm, the comparison budget from 400 mAh to 750 mAh, and the allowances to 28.54 µA over three years and 17.12 µA over five. H2 has no NFC, so the NFC OOB enrolment path is unavailable and moves to AIR-O-02. Air is now the only sleeping device in the family and maintains presence through scheduled intermittent contact, which AIR-O-01 records as the baseline link mode.

Key. Key count became a platform configuration rather than a fixed pair: KEY-02 targets 32 keys and beyond with Key 4/8 as the first configurations, and KEY-05 became a base-plus-per-key budget instead of one absolute ceiling. The ceilings that scale-up hits are recorded, not resolved — 160 LED channels at 32 keys against LP5024 channel and address counts, the 48-pin STM32G0B1CE's inability to carry 32 independent wake-capable key GPIOs alongside I2C, FDCAN, USB and SWD, and panel outlines per key count. Key no longer defines a sleep mode; its ≤5 mA@12 V figure became a quiescent ceiling.

Options written out. Two new comparison documents: air-hub/P05-air-hub-platform-options.md sets STM32G0B1CE + nRF54L15 against SSD202D + two ESP32-C6 and against a single BLE MCU with an SPI CAN controller, and air-switch/P05-air-switch-platform-options.md sets ESP32-H2 against nRF54L15, ESP32-C6 and CC1312R. Both record what must be settled before scoring. The SSD202D figures come from the vendor's preliminary product brief and show no CAN controller, one SPI master, −20…85 °C and a TBD power figure; the ESP32-C6 figures come from the module datasheet and are why C6 is recorded as rejected for a battery switch and appropriate for the mains-powered Air Hub. The ESP32-H2 evaluation's CR2450-era conclusion was annotated as superseded rather than rewritten, since another session owns it.

Verification: requirement-to-test mapping stays bidirectional in both guides (Air 26/9, Key 13/6), bun run docs:build and git diff --check pass, and the renamed paths resolve. Left open by design: X01-O-01, whether the Air Hub carries a display, whether its control path may run through Linux, and whether a second Linux device is acceptable beside the P03 Hub. No commit, push or deployment.

2026-09-11 20:11 [decision]

Repositioned P09 YBO Control under 20260911-1954-control-non-marine-air-positioning and 20260911-1957-control-non-marine-air-positioning after the user clarified that Mate is the marine wired internal-control solution and that Air is sold outside boats, where it drives external circuit breakers or relays through the Air Hub. P09-control-protocol-evaluation.md R0.2 now defines Control as the off-boat product form of Air (Air → Air Hub → third-party actuators), keeps the on-boat use as an optional ecosystem layer on the P03 Hub, and records the two added requirements: Air joins Matter, Apple Home and Home Assistant OS as a wireless switch, and Control may run its own cloud and interoperate with third parties in both directions.

Additions: §4.12 actuator-side integration (Matter controller role first, with Shelly Gen4 / Pro 1PM 40A Gen4 as evidence that Matter-certified relays and DIN-rail modules exist; Modbus master for industrial relays; native relay outputs as the floor; Zigbee, vendor local APIs and vendor clouds not adopted), requirements CTL-13 (confirmed read-back per actuator class), CTL-14 (Air keys as Matter Generic Switch endpoints) and CTL-15 (bidirectional interoperation gated by the local lock), the generic local lock replacing the helm lock (which stays as its marine instance), the own-cloud boundary B6, the matrix columns for actuator control and ecosystem membership, and open items CTL-O-10…15 — notably CTL-O-11, the new Wi-Fi/RS-485/relay requirement on the P5 Air Hub that its owners (task 20260911-1916) must take up, and CTL-O-12, whether the Matter controller role needs CSA software-component certification. control/index.md, the product/index.md row, the PRODUCT-PLAN P9 section and §6 item 12, and OPEN-QUESTIONS P9 were rewritten to match. Controlled Air/Key/Hub/Mate/Studio/X01/X02 documents are unchanged. No commit, push or deployment.

2026-09-11 20:05 [decision]

Recorded three Air Hub architecture answers in air-hub/P05-air-hub-platform-options.md: the Air Hub carries no display, so option B's H.264/H.265, JPEG, 2D graphics and MIPI DSI blocks are idle and their cost is itemised against other ARMv7 candidates; option B's control path runs through Linux because MQTT and the other uplink protocols are implemented there; and a second Linux device beside the P03 Hub is accepted, so folding the radio into P03 is no longer pursued.

The control-path decision has a consequence that is now stated in the document rather than left implicit: Air control is unavailable while the Air Hub's Linux is down, which departs from the family wording that configured control does not depend on Hub or cloud. It is acceptable only because Air's scope is already limited — SYS-03 restricts Air to comfort operations and X02 G-01 forbids a critical circuit bound solely to wireless_key — so the always-works path for critical circuits remains Key's wired CAN, and that dependency has to appear in sales and installation material. Watchdog and bounded recovery, an upper bound on control interruption during updates, no replay of stale commands after restart, and an unknown rather than success indication while Linux is down are required deliverables. Core behaviour is unchanged: no channel changes state because the Air Hub or its Linux is lost.

Still open: B1 versus B2, the standing-power budget, and whether option B replaces option A as the recommendation now or at D0.

2026-09-12 02:20 [decision]

Corrected the Air Hub positioning after the user restated the product model. The P03 Hub is hardware and Mate is the software running on it; the Air Hub and Air Switch form an independent product line that runs without the boat's hardware, reaches Mate over both CAN and the LAN, and hosts P09 Control off the boat with smart-home ecosystem access. The Air Hub therefore requires Linux as a matter of requirement, not platform preference: P05-air-hub.md §1 now states the product-line position and the Linux requirement, §2 records the Linux ARMv7 + two ESP32-C6 platform direction with CAN on one C6's TWAI (B1) and the STM32G0B1CE + nRF54L15 design demoted to a comparison, and §5 moves Wi-Fi/Ethernet, Matter and third-party actuators out of the extension table into the off-boat product scope owned by P09 through CTL-O-11. The platform options document withdraws the 2026-09-11 rider that questioned whether the Air Hub needed Linux, records B as the platform direction, and lists the D0 gates that remain. PRODUCT-PLAN P5 rows and the catalogue row were aligned, and the P5 target row lost its last deep-sleep clause.

The Hub/Mate consolidation plan 20260911-2016 was rewritten under the corrected model: one product, YBO Mate, keeping the P03 ID, with hardware and software as separate Level 1 records under mate/, software requirement IDs prefixed SFR-nn to avoid colliding with the hardware FR-nn, tiers, revenue lines and compliance routes preserved per half. A two-ID alternative is recorded. Awaiting approval; no Hub or Mate controlled document changed.

2026-09-12 05:40 [decision]

Completed 20260911-2014-hub-mate-consolidation and 20260911-2016-hub-mate-consolidation: the P03 Hub hardware and the P08 Mate software are now one product, YBO Mate, under the P03 ID. hub/P03-hub.md and hub/P03-hub-design.md moved to mate/P03-mate-hub.md and mate/P03-mate-hub-design.md; mate/P08-mate.md and mate/P08-mate-data-model.md became mate/P03-mate-software.md and mate/P03-mate-data-model.md; the hub/ directory and its index were removed and a single mate/index.md lists the five files. A new product entry mate/P03-mate.md states the two halves, their tiers (hardware T0; software basic T0, paid T1, fleet T2), revenue lines (one-off hardware versus subscription) and compliance routes, the fail-safe doctrine, and the relationship to the Air Hub — reached over LAN MQTT and YBO CAN, not part of Mate, able to run without it.

Software requirement IDs became SFR-01…SFR-30 so they no longer collide with the hardware FR-nn; the referrers in AC commissioning, Studio, View, Eye, P09 Control and the plan were updated, and the data model's own range citation follows. PRODUCT-PLAN §P8 folded into §P3 as a software subsection under a hardware subsection, §P8 pointers repo-wide now read §P3; OPEN-QUESTIONS P8 folded under P3 as a software subsection with its items re-keyed P3S-n, and the six documents citing P8-n items were updated. COMPLIANCE-MATRIX keeps two rows, relabelled "Mate 硬件（Hub）" and "Studio / Mate 软件与云". The catalogue carries one P03 Mate row and no P08 row. P08 is retired as a product ID; historical changelog and plan entries keep the old name as history.

Twenty-three documents changed for the path and name moves, 34 in total. Verification: bun run docs:build passes, the cross-reference checker (sections, FR/SFR/CTL/O IDs across bizplan/ and docs/) reports zero dangling references, git diff --check passes. Pre-existing oddity left untouched: a View display sentence sits at the end of the former P8 block, immediately before §P9. No commit, push or deployment.

2026-09-12 09:45 [decision]

Completed 20260912-0903-air-key-line-consolidation and 20260912-0906-air-key-line-consolidation: the wireless Air switch, the wired Key panel and the Air Hub are now one product line, P05 YBO Switch, and P06 is retired as a product ID.

product/air-switch/ became product/switch/; key/P06-key.md, key/P06-key-design.md and key/P06-key-supplier-guide.md moved in as P05-key*.md; the three air-hub/P05-air-hub*.md files moved in unchanged; the key/ and air-hub/ directories and their indexes were removed. A new product entry switch/P05-switch.md states the three records with their tier, supply, control path, MSRP, compliance route and milestone per record, the requirement-ID namespaces (AIR-nn, KEY-nn, GW-nn, shared SYS/SEC/IF, open items AIR-O-nn / KEY-O-nn / new line-level SW-O-nn), and why both supplier guides stay separate. One switch/index.md lists all twelve files. No requirement ID was renamed — unlike the Hub/Mate merge, the namespaces were already disjoint — and no target, price or open item changed value.

The Air Hub is now the hub of both halves. The user stated that Key can also attach to the Air Hub, since the Air Hub carries CAN. P05-air-hub.md §1 therefore withdraws "Air Hub 只针对无线": Air joins over BLE, Key over the hub's YBO CAN branch, and new requirement GW-06 makes a Key panel a control source under the same binding and permission check as GW-01, with its source class kept distinct from wireless_key so X02 G-01 is not weakened. GW-06 was added to the Air guide's requirement table and to the V-01 and V-07 rows, keeping the requirement-to-test mapping bidirectional. P05-key.md §1 and the product plan's path row now read: on the boat Key talks to Core directly and needs no Air Hub; off the boat it joins the Air Hub's CAN branch. Key hardware, its four functional wires and its CAN security position are unchanged. P09 gained CTL-16 (the off-boat wired input form) and CTL-O-16.

Three consequences were deliberately recorded rather than answered, as new line-level open items in OPEN-QUESTIONS P5: SW-O-01, who is the read-back authority off the boat where there is no Core to satisfy Key's FR-02/FR-03; SW-O-02, that the fail-safe argument accepted on 2026-09-11 — Air may die with the Air Hub's Linux because Key's wired CAN to Core always works — has no off-boat equivalent, so the Air Hub's Linux is a single point of failure for the wired switch too and the sales and installation material must say so; and SW-O-03, whether the Air Hub's CAN branch powers Key panels and for how many.

PRODUCT-PLAN §P5 and §P6 became one §P5 with an Air/Air Hub subsection and a Key subsection — grouped by supplier-guide scope — with every row carried over verbatim. OPEN-QUESTIONS P5 and P6 merged the same way. COMPLIANCE-MATRIX keeps its two rows, relabelled Switch · Air 开关 + Air Hub and Sense / Switch · Key, because the routes genuinely differ. The catalogue collapsed three rows into one; the root index.md product enumeration was corrected in the same sentence (it still listed the retired Hub line). 32 documents changed. Historical task and plan records keep the old names as narrative; only their link targets were repointed.

Verification: bun run docs:build passes, a link and requirement-ID sweep over bizplan/ and docs/ reports no dangling reference introduced by this change (the five pre-existing hits are absolute-path script assets and the index format examples), git diff --check passes. Pre-existing drift found and left untouched, recorded as task 20260912-0940: PRODUCT-PLAN §P5 and §6 item 4 and OPEN-QUESTIONS AIR-O-03/O-05 still carry the pre-2026-09-11 nRF54L15, CR2450, 400 mAh and ≤12 mm figures that the specifications have already superseded. No commit, push or deployment.

2026-09-13 05:05 [progress]

Completed 20260912-2057-product-matrix-diagram. The product package index now opens with a 产品矩阵 section holding two Mermaid flowcharts — the on-boat system (Switch control surfaces, Core/Sense execution and sensing, the AC control-and-detection boundary, Mate hardware plus software, Studio configuration, and the Eye/View/Tag peripheries) and the off-boat Air Hub form hosting P09 Control — plus reading notes on the Core-readback control loop, the no-YBO-AC-hardware boundary, local fail-safe behaviour and the single configuration source. Every node and edge restates PRODUCT-PLAN.md §2/§3; no product claim was added or changed. Both diagrams were parsed with mermaid 11.17.2 in a jsdom host (flowchart-v2, no syntax errors); bun run docs:build (192 pages) and git diff --check pass.

2026-09-13 03:40 [decision]

Completed 20260913-0144-product-matrix-readability and 20260913-0146-product-matrix-readability. The product matrix is now three charts — 控制与配电, 船舶主控与集成 and 船外形态 — with every node in a subgraph, no reverse edges, and labels capped at two lines. Mermaid now runs the ELK layout (@mermaid-js/layout-elk@0.2.3, registered client-side in the theme; fastdom and its promised extension are pre-bundled by Vite), renders diagrams at natural size instead of shrinking them to the text column (flowchart.useMaxWidth: false), draws SVG text labels rather than foreignObject labels, scrolls a wide diagram horizontally, and opens any diagram 1:1 in a full-screen dialog on click. Verified against the production build in a headless browser: three charts render with no syntax error, each container scrolls, the dialog opens with the diagram and closes on Escape. No product statement changed.

2026-09-13 04:55 [progress]

Completed 20260913-0445-ecosystem-access-note after the user asked whether the Hub can be reached through HomeKit and then asked for the answer to be written into the package. Added product/control/P09-control-ecosystem-access.md, a customer-facing page derived entirely from P09-control-protocol-evaluation.md §4.2, §4.6, §4.10 and §7, plus its row in control/index.md.

The page states the answer once — Apple Home is reached through a Matter bridge, not HAP, because HAP covers only Apple while one Matter certification covers Apple, Google, Alexa, SmartThings, Home Assistant, 米家 and 涂鸦 — and then separates the two products that are both called a hub: the Air Hub carries the Matter bridge (base scope for the off-boat form, an extension on the boat), while the P03 Mate Hub has no such commitment because CTL-O-01 has not frozen where the on-boat exposure layer runs. It carries the per-ecosystem prerequisites and regions, and the three limits a customer has to hear: critical circuits are never bridged; the local lock can only refuse the ecosystem layer as a whole, because Matter's sender is always the on-site ecosystem hub and the Air Hub cannot tell a phone in the house from a command relayed through HomePod or Echo; and success is shown only from a real read-back.

No product decision was made and no figure was introduced. Because P09 is T2 concept and PRODUCT-PLAN §6 item 12 is unfrozen, the header marks the page as a plan rather than delivered capability or a compatibility promise. bun run docs:build and git diff --check pass. No commit, push or deployment.

2026-09-13 05:04 [progress]

Executed the four PDM catalogue follow-up batches authorized in 20260913-0447-vendor-followup-batches. Added 31 records under bizplan/research/vendors/: 30 supplier profiles and one unresolved Tongle identity record. The catalogue now has 57 records: 56 suppliers plus the unmatched identity lead. Updated the catalogue and research entry points, preserving the earlier benchmark CSV as a historical subset.

Each new profile records dated official evidence, model-specific limits, procurement and software/protocol access, and qualification gaps. Findings include the discontinued Danfoss IOX018-130 order number; conflicting Rongtai channel totals, GINSIN MCU descriptions and ACTIA CAN counts; changed KopherBit current figures; STW detailed output groups differing from its family summary; and the distinction between relay/fuse systems, solid-state outputs and low-current dimmer control signals. Published prices are scoped to their region, variant and evidence date; placeholder prices are excluded. No supplier was contacted and no product requirements were changed.

Validation: all 31 new records have the six required sections, dated evidence and index links; local Markdown references and table structure pass. The production build passed using the pinned Node v22.23.2 image documented in the plan, after the Bun image failed because git was absent. Checked all 33 new/updated content routes and 898 rendered local links with no broken targets or fragments. git diff --check passes. Existing bundle-size and oversized Bertram PDF asset warnings remain. No commit, push or deployment.

2026-09-13 21:50 [progress]

Completed 20260913-2141-diagram-approach-comparison. Published bizplan/product/diagram-approaches.md, a side-by-side page carrying the three ways the product matrix can be drawn — Mermaid with the ELK layout as published today, a static SVG generated by the fireworks-tech-graph skill from a committed JSON definition, and a hand-designed HTML/CSS layered-card layout with bus lanes and clickable product cards. Each approach lists its maintenance cost, layout control, page weight, dark-mode behaviour and known limits, followed by a comparison table and a recommendation: overview views are a layout problem and suit the card layout, single-path detail views are a topology problem and stay on Mermaid.

Assets published under bizplan/product/diagrams/: the SVG and its source JSON, the standalone HTML prototype, and its light, dark and narrow-viewport screenshots. ignoreDeadLinks now also accepts a link whose .html target exists, because cleanUrls strips the suffix before the check and a published static asset is not a page. No product statement changed; the comparison page and the unadopted assets are to be deleted once an approach is chosen.

2026-09-13 22:40 [decision]

Completed 20260913-2233-adopt-svg-product-matrix. The user chose the fireworks-tech-graph approach from the comparison and gave three corrections, all applied: the bus lanes are gone and the diagram now carries product-to-product edges only, Studio connects to Core because Core's channels and rules are what it configures, and clicking the image opens it full size.

The product matrix section now leads with the generated SVG instead of the two on-boat Mermaid charts; the off-boat Control chart stays on Mermaid because the SVG does not cover that scenario. Reading notes gained a Studio line and a line naming what the diagram deliberately leaves out (Tag, View, the multi-circuit AC metering module, and the NMEA 2000 route to MFDs). Click-to-zoom in the theme now covers Markdown images as well as Mermaid SVGs, and skips a linked image so a link still opens.

The comparison page and the assets of the two unadopted approaches were deleted, and the ignoreDeadLinks rule added for the standalone HTML prototype was reverted with it. The diagram definition lives beside the SVG at bizplan/product/diagrams/ybo-matrix.json; it renders at standard quality because Core's four ports are taken by four edges and Key must share one, which the showcase micro-segment budget rejects. Verified in a browser against the dev server: the image reports its natural 1400×478, the dialog opens with the image and is removed on Escape, no page errors. bun run docs:build and git diff --check pass.

2026-09-13 23:15 [decision]

Completed 20260913-2310-mate-unified-and-ac-controller. Two architecture statements from the user are now drawn: P03 Mate is one product with hardware and software together, no longer a hardware Hub plus software running on it; and the AC side has its own controller that makes its own decisions, reached from Mate over RS-485 or CAN, so Core no longer drives AC contactor coils. The off-boat Control chart was redrawn with the same generator, so the product matrix now uses one drawing method and carries no Mermaid chart.

Both statements contradict controlled content that this change deliberately does not touch: PRODUCT-PLAN.md §P3 is written as two halves; §P1 Core custom requirements 8 and 9 exist only to drive AC latching relays from Core, requirement 9 being a flagged supplier-negotiation item; §P4 開關執行, 支路开关基线, 脉冲时序 and 降级行为 are written around a Core channel driving the relay directly, with priced candidates; §P4 carries the non-negotiable "YBO 无任何硬件承载交流载流或交流电位" boundary; §P7 Studio owns the pulse channel type. The product index therefore carries a warning block naming both divergences and stating that the product plan governs until the write-back happens. Three items are open and block that write-back: whether the AC controller is a YBO product, a partner product or a third-party selection; whether the no-AC-potential boundary still holds; and whether Core's pulse-output requirement is retired.

Verified in a browser against the dev server: both images report their natural 1400×478, each opens in the zoom dialog with the right file and closes on Escape, no page errors. bun run docs:build and git diff --check pass.

2026-09-13 23:55 [decision]

Completed 20260913-2312-ac-do-writeback and 20260913-2315-ac-do-writeback. The user answered the three items blocking the write-back: the AC-side controller is YBO's own and belongs to the Core line as its DO control member; the "YBO 无任何硬件承载交流载流或交流电位" boundary still holds; Core's pulse-output requirement is kept. Those answers, together with the unified Mate, are now written into the controlled package across 15 files.

Core gains a named family member, Core DO, in PRODUCT-PLAN.md §P1 and product/core/P01-core.md §2. Every electrical cell reads 待定 — no channel count, drive capability, voltage, quiescent current, enclosure or interface was invented. §P1 custom requirements 8 and 9 keep their text and requirement 9 keeps its ⚑ flag, firmware-enforced on-time limit, glitch suppression and one-channel-per-latching-circuit rule; only the carrier changed, and the entry now states the Core RFQ text must be reissued for that reason. §P4's non-negotiable boundary paragraph gained one clause placing Core DO inside it, and its 开关执行, 支路开关基线 and 降级行为 rows changed execution subject while keeping the priced Schneider iTL and Finder candidates, the 50 ms–1 s window and the 5-actions-per-minute limit. COMPLIANCE-MATRIX.md still reads "YBO 侧无 LVD 范围"; only the sentence naming the driver changed, and the Core row now covers the DO member.

Mate is one product: §P3's two #### subsections became 硬件面 and 软件面 of a single product, with every figure, tier, price and milestone kept verbatim; product/mate/index.md and P03-mate.md restated. The P03-mate-hub*.md filenames were left alone because renaming them would break ten inbound references for no reader benefit.

The plan under-scoped by two files: BUSINESS-PLAN.md and its English version also stated that Core channels drive the AC contactors and that Hub reads the metering. The verification grep caught them and both were updated together. OPEN-QUESTIONS.md P1-1e records what stays undecided for the DO member — model name, electrical envelope, tier, price, milestone and whether it reuses the Core base platform. The divergence warning is gone from the product index, and the matrix diagram now also carries the Mate → MFD link over NMEA 2000 and the ship LAN. Research reports were not touched. bun run docs:build and git diff --check pass.

2026-09-14 03:20 [decision]

Adopted the documentation standard (plan 20260913-2344-documentation-standard, task 20260913-2341) and completed all five migration phases in one pass after the owner approved the whole plan ("开始全部处理"). The standard lives at docs/documentation-standard.md: twelve document kinds, a frontmatter schema (title / kind / status / updated / version / product / level / lifecycle / evidenceDate / supersededBy / decision), lower-case kebab filenames with the P<nn>- and X<nn>- prefixes as the only exceptions, fixed product package slots (spec, design, guide, brief, evaluations), typed index tables (文档 | 类型 | 状态 | 内容), and the quality gate bun run docs:lint && bun run docs:build && git diff --check. Templates are in docs/templates/ (a full product-package/ skeleton plus report, catalog, evaluation, decision). scripts/lint-docs.mjs enforces the lint-marked rules and reports zero findings across 202 pages; the deploy workflow runs it before the build. DocMeta.vue renders the frontmatter above the H1, so status, version and date lines no longer live in prose.

Phase 3 (product packages, task 20260914-0231): every product directory now holds only slot files. Renamed onto the slot names: P04-ac-interface → P04-ac, P04-ac-commissioning / P04-ac-board-16 → P04-ac-design-*, P03-mate-hub-design → P03-mate-design-hardware, P03-mate-data-model → P03-mate-design-data-model, P07-studio-architecture → P07-studio-design, P11-eye-integration → P11-eye-design, P09-control-protocol-evaluation → control/evaluations/protocol-platforms, P09-control-ecosystem-access → P09-control-brief. The two Mate Level-1 halves were merged into P03-mate.md §3 and §4 (headings demoted; requirement IDs FR-nn / SFR-nn unchanged). P09-control.md was seeded from the evaluation's positioning chapter as a concept-stage spec without new decisions. Brief stubs were added for Core, Sense, Mate, AC, the Switch line, Air, Key, Air Hub, Studio, View, Eye and Tag (each holds only the positioning paragraph). Switch became three sub-packages air/, key/, air-hub/.

Phase 4 (research and vendors, task 20260914-0232): the 30 reports moved into research/market/, industry/, engineering/ and lost their numeric prefixes (the duplicate 08 is resolved; the older one is status: superseded with supersededBy). The PDM catalogue moved to research/vendors/pdm/ and the Air/Key categories to research/vendors/{gateway,switch,keypad}/; air-key-vendor-landscape is vendors/air-key-landscape.md. Every research and catalogue page carries frontmatter; the three engineering proposals that had been superseded in prose now say so in frontmatter.

Phase 5 (governance and root, task 20260914-0233): the nine governance files moved to bizplan/governance/ with lower-case names and version bumped where content changed today (product plan v1.2, business plan v2.1, commercial model / compliance matrix / assumptions / open questions / PPT guide v1.1); the stale "英文对应文档" sentences are gone. s7-200g2/ is refs/s7-200g2/. Navigation, the home page, docs/architecture.md and AGENTS.md describe the new tree. .vitepress/public/_redirects carries 63 redirects from every old clean URL; Cloudflare Workers static assets honour the file, to be confirmed on the first deploy.

Phase 2 (records, task 20260914-0230): RESEARCH-008 closed and PLAN-024 rejected as superseded by the Core 27 / 43 family; the yacht evidence task and plan completed (their step 4 was delivered through 20260910-0717); the malformed /root owner on RESEARCH-008 was reset so the serializer could close it. Repository hygiene (REPO-001): .editorconfig, .gitattributes, README.md added; the dead bsp-control/ ignore removed; .env.example is not applicable (no environment variables); LICENSE still needs the owner's decision.

Verification: bun run docs:lint 0 findings; bun run docs:build passes (known bundle-size warning and the two Bertram PDFs above 25 MiB skipped as before); a scan of the built site checked 6,852 internal links with no missing target and no missing fragment; git diff --check passes. No commit, push or deployment.

2026-09-14 03:20 [decision]

Completed 20260910-0714 / plan 20260910-0717 (distributed Core product family). Core is now two general-purpose output modules, Core 27 and Core 43 (working names; commercial names TBD): 1×120 A + 3×80 A + 5×50 A + 18 or 34 × 15 A, a fixed subset of 15 PWM-capable 15 A channels per model, 10 configurable local inputs (digital / voltage / resistance / 4–20 mA / 0–20 mA, one active mode each), CAN + RS-485. The old Core S / M / HD family is a labelled historical baseline in product-plan.md §P1 and P01-core.md §2; its prices, dimensions, base-platform benchmarks and evidence do not transfer. Module aggregate current, PWM channel numbering, input electrical definitions, interface profiles, the 15 A PWM device class, enclosure size and commercial names are open items (P01-core.md §15, open-questions.md P1-1f, product-plan.md §6 1f). Downstream: X01 node classes CORE-27 / CORE-43 / CORE-DO and TELEM paging; X02 class enum, engineering_review on 50/80/120 A channels, the 15 A mapping rule G-03, no half-bridge, input mode; Studio FR-02/03; Sense no longer described as absorbed by Core M; AC examples no longer count on Core M inputs (Sense carries AC acquisition); business plan (zh/en), commercial model, assumptions, compliance matrix, PPT guide and the product index updated. P01-core-design.md was rewritten around nine HP stages, BTH50015 for 15 A ON/OFF, a to-be-decided 15 A PWM device class and a five-mode input front end; the old pin, connector, thermal and BOM tables were replaced by explicit redesign items rather than invented values.

2026-09-14 03:20 [decision]

Completed 20260914-0010 (sub-GHz/LoRa selection and Air/Air Hub consistency), plan 20260913-2340 (Air documents consolidation) and 20260912-0940 (governing Air figures). Air and Air Hub are each one self-contained specification (switch/air/P05-air.md, switch/air-hub/P05-air-hub.md, nine parts each) replacing eight files; the deviation from the package slots is recorded in docs/decisions/2026-09-14-air-single-file-spec.md with a 2026-12-31 sunset. Every requirement ID of the old files survives (ID-by-ID diff: none lost; one added, AIR-O-09). The three drift defects are repaired by applying the recorded 2026-09-11/12 decisions rather than by new choices: Air first-version MCU is ESP32-H2 with nRF54L15 as the alternate, Air Hub's platform direction is Linux SSD202D + 2×ESP32-C6 with its design content rewritten for Linux, and the ≤15 mA / ≤30 mA power target is superseded by the 125–210 mA@12 V order of magnitude. The governing figures in product-plan.md §P5 and §6 item 4 and in open-questions.md AIR-O-03/05/07 now match (ESP32-H2, 2×AAA, 750 mAh, ≤14 mm). sub-GHz and LoRa: candidates with original-vendor data are recorded for both products (TI CC1312R and CC1352P7 from TI, Semtech SX1262 and LR1121 from Semtech; STM32WLE5 and EFR32FG28 listed with product URLs because the ST and Silicon Labs sites could not be fetched in this session), split by the two possible positionings; the positioning itself, whether sub-GHz/LoRa are added alongside BLE or remain a conditional replacement, is the new open item AIR-O-09, not decided here. Doc-table layout (task 20260913-0329, plan 20260913-0331): the markdown renderer wraps every table in .vp-table, tables keep real table layout with a 6.5em column floor inside a scrolling wrapper, and the no-sidebar content column is widened to 1104 px; screenshot verification is recorded in the task.

2026-09-14 03:45 [progress]

Completed 20260914-0317-site-explorer-theme (plan 20260914-0318, alternative A). The site now navigates like a file manager: .vitepress/site-tree.ts walks the file system at config time and produces one tree of every published page (folder labels from each index.md title, page labels from frontmatter title, order following the directory's own index tables), and that tree feeds the VitePress sidebar, the breadcrumb labels and a generated docs/sitemap.md (238 pages, rewritten on every build). The sidebar shows 商业与产品 / 治理文件 / 产品规格 / 研究报告 / 供应商目录 / Project tracking at the top level with the second level open and deeper or large folders (the four vendor categories) collapsed until entered; the current page's ancestors open automatically. Layout: 320 px tree, min(1680px, 100vw) page width, 1100 px content column beside the outline; the earlier no-sidebar width overrides were replaced. Badges for kind and status in the tree are deferred as the plan states; kind and status remain visible in DocMeta and the sitemap. The markdown emoji shortcut rule is disabled so datasheet figures such as <3 mA no longer render as ❤️ (found on the vendor pages during screenshot review; 0 hearts in the built site now). Navigation gained a 站点地图 entry; AGENTS.md, docs/architecture.md and docs/index.md describe the generated sidebar and sitemap.

Verification: screenshots of a product spec at 1440 px and 1920 px, a vendor record, the home page and the sitemap (tmp/shots/); the first 1440 px capture showed the tree clipped because the default theme derives the sidebar width from the layout maximum, fixed by capping that variable at the viewport width. bun run docs:lint 0 findings; bun run docs:build passes; git diff --check passes. No commit, push or deployment.

2026-09-14 03:45 [progress]

Added bizplan/research/market/iaa-transportation-2026/: the full IAA TRANSPORTATION 2026 exhibitor directory (Hannover, 2026-09-14 to 09-20) captured from the Corussoft EventGuide backend behind exhibitors.iaa-transportation.com — 1365 exhibitors across 12 hall rosters with country, stand, website and profile, 92 registered products, distribution statistics and a 43-company shortlist of electrical, electronics, harness and body-electronics exhibitors relevant to Core. Raw exports and the retrieval script are archived under bizplan/research/data/iaa-transportation-2026/. One platform demo record (IAA Marketing Hub DEMO) was excluded from the 1366 raw rows. Task 20260914-0332, plan 20260914-0336.

2026-09-16 06:30 [decision]

Rebuilt the docs site on Astro 7.3.2 + Starlight 0.42.0 with the Cloudflare adapter, replacing VitePress 1.6.4. Starlight pages stay prerendered, so the 289 static pages keep the previous cost profile as Cloudflare assets, and a route opts into on-demand rendering in the Worker with export const prerender = false — which is why the framework changed at all. The 287 Markdown pages were never moved: a plain Astro glob() loader sources them in place from bizplan/ and docs/, because Starlight's own docsLoader() hard-codes its glob base to src/content/docs. git diff --name-only <base> HEAD -- bizplan docs is empty for every workstream branch; the only content file edited in the whole migration is the root index.md, rewritten into Starlight's splash form with its copy preserved character-for-character.

Two defects that a passing build could not see were found and fixed. Astro does not rewrite relative Markdown links, so 215 of 288 pages emitted in-site hrefs that 404'd while every URL still resolved — an mdast plugin now maps each .md link through the collection's own id rule, 1271 links rewritten, and the four remaining .md hrefs are external GitHub citations. Astro's heading slugs differed from VitePress's on 1952 of 2408 headings, killing 16 in-page anchors on business-plan.md and business-plan.en.md and every external bookmark to a numbered heading; VitePress's slug rule was transcribed out of the old build and the ids are now byte-identical. Smart punctuation was corrupting the documented quality-gate command (git diff --check rendered with an en dash on 7 pages), the P10 View inch marks and a company name, and the GFM autolinker ran past an unbalanced ) and killed three external links including the ONVIF Profile T compliance citation.

Accepted, ruled drift: the body heading now outranks a diverging frontmatter title on 25 index pages — restoring descriptive prose the leading-heading strip was deleting, at the cost of a longer <title> on those pages; sidebar groups cannot be links, so each directory contributes its index page as the group's first child; GFM task-list checkboxes render as real inputs; external links no longer open in a new tab.

Search is a deliberate, evidence-backed regression. Pagefind replaces the VitePress MiniSearch bigram index: as shipped, Chinese mean recall@10 is 0.737 against MiniSearch's 0.854. An oracle rerank of Pagefind's own candidate set caps at 0.836, which proves parity is unreachable by tuning, and ~93% of the loss is ranking rather than recall. Keeping MiniSearch would have meant a hand-built Search component tracking Starlight's styling, keyboard behaviour and i18n across every upgrade — the liability this migration exists to reduce. The frozen 24-query set, both baselines, the runners and the 384-point ranking sweep are preserved at scripts/search-eval/ so a re-evaluation starts from data. Note the metric understates both arms: a 37-document ground truth caps at 0.270 by arithmetic.

The quality-gate command is unchanged — docs:* stayed canonical and now points at Astro, with docs:build carrying the sitemap prebuild. scripts/lint-docs.mjs was never modified. scripts/check-build.mjs survives the migration and asserts the Pagefind index, _redirects bytes and the copied assets, each a silent failure that ships a site which renders perfectly and is broken; it builds dist/ itself rather than asserting against whatever is on disk.

Task 20260915-1901, plan 20260915-1901. Delivered as BKD campaign l1-5k89db54-20260915190438 across four workstreams and 44 issues.

2026-09-21 17:15 [progress]

Closed the Astro migration follow-ups. Every page is now served at a slashless URL with no redirect: 31 directory URLs were still emitted with a trailing slash in about 9900 in-site hrefs, each costing a hop, and are now slashless at every source; all 291 sitemap URLs answer 200 without a redirect. site is set, so sitemap.xml and canonical links are live. The deploy workflow pins the wrangler that generates the Worker config. Three malformed external links were repaired, and lint-docs.mjs now rejects bare HTML tags in prose, which Astro renders as nothing. The site has a placeholder icon, external content links open in a new tab as they did under VitePress, and the heading-anchor label is translated. Search was re-measured on the weights actually shipped: Chinese recall@10 is 0.774, not the 0.737 recorded at decision time, and the evaluation record was corrected. Task and plan 20260921-1659.

2026-09-22 07:40 [decision]

Completed task 20260921-1700 and plan 20260921-1701. The Switch line now uses one document model for all three products: each of Air, Key and Air Hub carries a brief, a Level 1 spec whose chapter 3 is the functional behaviour ID table, a Level 2 design appendix and a supplier guide, and the clauses common to the three guides live once in the new line-level bizplan/product/switch/P05-switch-guide.md. Air and Air Hub were split back from their single files onto the standard slots (content moved by chapter, no value changed); decision 2026-09-14-air-single-file-spec is superseded by 2026-09-22-switch-four-slot-model.

Key was normalised onto the same skeleton and its contradictions resolved against the governing records: the CAN FD / 2 Mbit/s sentences were replaced by the X01 Classical CAN decision, the sleep wording in the design appendix, guide and product-plan.md §P5 was reworded to a non-sleeping panel (task 20260911-1916), and the ≤60 mA@12 V backlight ceiling moved from the design appendix and governance into the spec. The Key FR-nn requirements were renumbered into KEY-08…17 with the full mapping in the spec change log; X01, X02 and the open questions were updated to the new IDs. Stale Hub (Mate) and Air 指南 references were removed, and 34 inbound section references in governance, shared, Mate, Studio, Control, Tag and research were repointed at the file that now holds the content.

Verified: every requirement, open-item and verification ID present before is present after (FR-nn only through the mapping row); no unit-bearing figure in a design or guide file is a Level 1 target absent from its spec; bun run docs:lint (222 pages, 0 findings), bun run docs:build and git diff --check pass.

2026-09-22 08:30 [decision]

Completed task 20260922-0746 and plan 20260922-0747. The Mate package now presents the same four registers as the Switch line. P03-mate.md (R0.3) is one Level 1 document with one eleven-chapter sequence in which the hardware face and the software face sit side by side; chapter 3 holds FR-01…22 as a table with a verification column and SFR-01…30 grouped as before, wording and numbering unchanged. The spec now states the 2026-09-13 single-product decision instead of "two halves", replaces "2× CAN FD" with the X01 Classical CAN decision, records the Level 1 / Level 2 disagreement on the third CAN controller as open item hardware 14, and rewrites the stale P8 / P06 / P7 and OPEN-QUESTIONS P3-n / P3S-n citations.

The chip candidate table moved from the spec into P03-mate-design-hardware.md §2 (R0.2, with MCP2518FD and S32K116 rows added from the design text); the CAN FD wording in the design (block diagram, pin budget, circuit list, EOL row) was replaced by Classical CAN 500 kbit/s. P03-mate-design-data-model.md (R0.2) got the standard relations list and change log, its spec citations repointed, and four software rows that cited hardware FR-07/08/10/12 by mistake corrected to SFR-. The brief was written in full from the spec.

Inbound references in X01, X02, Studio, View, Eye, Control, Tag and the product plan were repointed by chapter mapping; product-plan.md §P3 "2× CAN FD" became Classical CAN; the leftover P05-key.md FR-10 citation in X01 §9 became KEY-05.

Verified: every FR/SFR ID present before is present after (52/52); remaining figures in the design appendices are datasheet values, rails, budgets and EOL limits; lint 222 pages, 0 findings; build and git diff --check pass. Not done: other packages (Sense, View, Core, Tag) still say "CAN FD" in their own datasheet rows and diagrams; that is outside this task.

2026-09-22 20:22 [decision]

Completed task 20260922-0818 and plan 20260922-1707. Added the Air evaluation page bizplan/product/switch/air/evaluations/ti-cc2340-touch-battery.md and its row in the Air package index. The page compares TI CC2340R5/R53, CC2652R7, CC2674R10/P10 and CC2755R10 with the current ESP32-H2 and nRF54L15 figures, records the TI CC3301 Wi-Fi companion as an Air Hub / Mate candidate only, splits radio + MCU SoCs into those without and with an on-die capacitive-touch peripheral, adds external touch ICs, verifies Zigbee / Matter / BLE support per candidate from vendor SDK and CSA records, and compares Li-FeS2 AAA, alkaline AAA, CR2450 and Li-SOCl2 cells against the 750 mAh budget. No Level 1 value or design-appendix recommendation changed; recommendations are recorded for AIR-O-01, AIR-O-02 and AIR-O-05.

2026-09-23 11:28 [decision]

Completed task 20260922-2048 and plan 20260922-2048. The Air battery baseline returns to a single CR2450 fed directly (no buck-boost), reversing the 2026-09-11 move to 2×AAA; the reason is that the evaluated SoCs run from 1.7–1.9 V with ≤11 mA radio peaks, not that the battery data changed. Because the ESP32-H2 cannot run from a coin cell, the first-version platform is now nRF54L15 with TI CC2755R10 as the alternative. P05-air.md R0.5: CR2450, thickness back to ≤12 mm, 400 mAh budget (15.22 µA / 9.13 µA), child-resistant compartment in AIR-01, coin-cell transport and 16 CFR 1263 / IEC 62368-1 under AIR-O-06, AIR-O-02 and AIR-O-05 reworded. P05-air-design.md R0.2: platform table A nRF54L15 / B CC2755R10 / C ESP32-H2 (rejected) / D ESP32-C6, new diagram, 400 mAh table, coin-cell electrical rules (10 µF input, ~100 µF low-leakage storage, TX cap at low battery, 3.0/2.4/2.0 V test points). Guide R0.2 (V-08, §7), brief, package index, line spec R0.4, line brief, line index, H2 evaluation note, product plan v1.3 §P5 and §6, open questions v1.2 items 3–4, and the Tag design cross-reference updated. All AIR-nn and AIR-O-nn IDs unchanged. Lint 223 pages 0 findings; build and git diff --check pass.

2026-09-25 09:39 [decision]

Completed task 20260925-0931 and plan 20260925-0931. Added the Air Hub evaluation page bizplan/product/switch/air-hub/evaluations/industrial-linux-and-radio.md and its row in the package index. Under the owner's new inputs (one Linux SoC plus one radio, industrial-grade silicon, two single-radio variants: 2.4 GHz with BLE / Zigbee / Thread selected by firmware image, and sub-GHz LoRa / 433 MHz), the page compares Allwinner, Rockchip and SigmaStar industrial SoCs (only RK3506J and T113-i combine −40…+85 °C with native CAN; both need external DDR), records the LCSC DDR3L prices that make memory the largest base-board item and the Forlinx FET3506J-C module route, lists 2.4 GHz candidates (EFR32MG21/MG24, CC2674, CC2652, CC2755R10, nRF54L15, nRF52840, ESP32-C6) against host-stack maturity, sub-GHz candidates (SX1276/78, SX1262, LLCC68, LR1121, STM32WLE5, CC1312R, CMT2300A, CC1101, Si4463) with OOK support, and a per-variant BOM. P05-air-hub-design.md R0.2: §2.5 main-controller row adds RK3506J as the alternative. The spec, including its platform row, single model and environment row, is unchanged; the two variants and the industrial-grade requirement need their own task.

2026-09-25 09:51 [decision]

Completed task 20260925-0942 and plan 20260925-0942. Owner decisions: split the Air Hub into two models, move the main controller to industrial-grade silicon, make 433 MHz compatible with third-party OOK remotes, and make LoRa standard LoRaWAN. P05-air-hub.md R0.5: models Air Hub (one 2.4 GHz radio, BLE / Zigbee / Thread by signed firmware image, GW-07) and Air Hub LR (LoRaWAN multi-channel gateway, EU868 / US915 SKUs, GW-08; 433.92 MHz OOK receive limited like wireless_key and never bound to critical circuits, GW-09); main controller is an industrial (−40…+85 °C) Linux SoC with native CAN, reference RK3506J, implemented chip-down or as an industrial module (FET3506J-C), chosen at D0; B1 and the SSD202D temperature gap removed; IP uplink is Ethernet and Wi-Fi becomes an extension; AIR-O-03 and AIR-O-09 reworded, new AIR-O-11…13. Design R0.3 (option D, chip-down vs module table, Air Hub LR radio: SX1302/SX1303

• 2×SX1250 and CMT2300A, EFR32MG21 recommended for Air Hub, two firmware chains), guide R0.2 (V-11, V-12, per-model EOL and quotation), brief, package index, evaluation page note, line spec R0.5 and brief, line and product indexes, product plan v1.4, open questions v1.3, compliance matrix v1.2 (new Air Hub LR row), and a Tag cross-reference note (Air Hub R3 now read as Air Hub LR; Tag values unchanged, access-mode alignment under AIR-O-12). X01 / X02 not changed: the OOK source class still has to be added to X02.

2026-09-25 10:19 [decision]

Completed task 20260925-1017 and plan 20260925-1017. The shared Air Hub / Air Hub LR base board gains one ESP32-C6-MINI-1 as the Wi-Fi uplink over ESP-Hosted (SDIO or SPI; SPI when an eMMC core board occupies the single SDMMC), with its BLE and 802.15.4 disabled; the Air Hub functional radio stays EFR32MG21. P05-air-hub.md R0.6 (uplink Ethernet or Wi-Fi, three firmware chains in SEC-05 / §6 / AIR-O-03, two 2.4 GHz radios in §7), design R0.4 (Wi-Fi row, diagram, roles, coexistence and PTA note, recovery), guide R0.3, brief, package index, product plan, open questions and compliance matrix updated. Correction: the evaluation page and design appendix gave 88 CNY for FET3506J-C; 88 CNY is FET3506J-S and FET3506J-C is at most 138 CNY batch, tax included. The evaluation page now lists Forlinx and MYIR RK3506J modules and FET113i-S with sources, and its BOM is recomputed per model and per implementation (Air Hub about $33–57, Air Hub LR about $45–78 at 1k).

2026-09-25 15:48 [decision]

Completed task 20260925-1547. Added bizplan/product/switch/air/evaluations/nrf54l-tiers-matter-footprint.md: the nRF54L15 / L10 / L05 memory tiers (identical radio, power, NFC and packages), the BLE-only firmware and partition estimate per tier, Nordic's nRF Connect SDK 3.0.0 Matter over Thread memory table and memory map for nRF54L15 (Light Switch release 706 KB ROM, 169 KB RAM; DFU secondary slot in external flash unless image compression is used), and the feasibility and certification notes for building Matter on Zephyr. Listed in the Air package index; AIR-O-03 cites it for the tier and dual-image conditions. No Level 1 value changed. Lint 225 pages 0 findings; build and git diff --check pass.

2026-09-27 18:18 [progress]

Completed 20260927-1650-docs-table-rendering. A Sätteri hast plugin (src/table-wrapper.ts) wraps every content table in div.table-wrap, which replaces the table itself as the scroll box. Tables now have an outer border, a shaded header, zebra rows, row hover, column separators, horizontal scroll shadows, a sticky header inside tables of more than 30 rows (capped at 80vh), and a content-sized layout for tables of six or more columns so prose columns no longer collapse (mean exhibitor-table row height 182 px to 80 px). Tables wider than the content column get a full-screen button that reuses the diagram zoom dialog. No Markdown source changed; 890 of 890 built tables are wrapped. Checked in Playwright screenshots in both themes; lint, build and git diff --check pass.

2026-09-27 18:30 [decision]

Completed task 20260927-1640 and plan 20260927-1640. The Air Hub spec no longer names one reference platform. P05-air-hub.md R0.7 defines three axes (platform H1–H14: SSD202D, RV1103G1, RV1106G3, RK3506G2, T113-S3 / S4 / i, NUC980, STM32MP135, RK3506J core board and chip-down, MA35D1; CAN source: SoC-native, SPI MCP2518FD or the ESP32-C6 TWAI; radio R0–R8 for Air Hub, where R0 lets the uplink ESP32-C6 carry BLE, and L1–L7 for Air Hub LR) and 30 named combinations (AH-01…18, LR-01…12) with device grade, capability and a 1k BOM range (Air Hub from about $18–30 plus the SSD202D price to $56–71). New requirements: GW-10 (any CAN source, no receive loss at full bus load, bounded BUS-OFF recovery), GW-11 (ESP32-C6 as CAN controller: authenticated Linux-only frames, no network-originated CAN, declared outage on C6 reset), GW-12 (proprietary LoRa star for Air Hub LR). Host software is stated as Rust, which removes the Node.js-based ARMv5 exclusion. Design R0.5 (option E, CAN sources, star network, C6 roles; the SSD202D "vendor documentation missing" reason withdrawn: datasheet V0.4 and product brief are public), guide R0.4 (V-13 CAN source, V-14 star network, per-combination quotation), two new evaluations (platform-combinations.md, lora-star-vs-lorawan.md), Ebyte ECK30 rows in the 2026-09-25 evaluation, decision 2026-09-27-air-hub-platform-combinations (H1–H6 below the family −25 °C rule, sunset 2027-03-31), line spec R0.6, product plan v1.5, open questions v1.4, compliance matrix v1.3, package and line indexes and the brief updated. Findings: NUC980 128 MB parts (NUC980Dx71Yx) reached last-order date 2026-07-31; Tag's 2–5 s heartbeat exceeds the EU868 1 % device duty cycle at SF7 under either LoRa form and is flagged under AIR-O-12. Lint 227 pages 0 findings; build and git diff --check pass.

2026-09-27 18:55 [decision]

Completed task 20260927-1829 and plan 20260927-1829. Archived 34 datasheets for the chips in the Air Hub platform combinations under refs/datasheets/air-hub/ (excluded from the website) with manifest.csv, SHA256SUMS and a README; about 98 MB. Sources: manufacturer sites where scripted download works (TI, Silicon Labs, Espressif, Nuvoton, NXP), otherwise the LCSC datasheet mirror or labelled third-party mirrors (SSD202D, RV1103 / RV1106, T113-i, MA35D1). Not retrieved: T113-S4, Corecell module. Correction: the Air Hub docs called nRF54L15 Zigbee support experimental; the nRF Connect SDK Zigbee R23 add-on has been production-ready for nRF54L15 since v1.0.0 (2025-07-07), ships an NCP sample and the ZBOSS NCP Host package, and nRF54L15 holds CSA Zigbee R23 compliant-platform certificate ZIG25035ZCP27505-24 (2025-12-10); zigbee2mqtt's ZBOSS adapter is still experimental. Spec R0.8 (R5 row, AH-16 now with nRF21540 at $42.1–54.1, AIR-O-11), design R0.6 (§2.5), platform-combinations.md (new §7.1 comparing EFR32MG21 and nRF54L15 on the hub side; the QFN nRF54L15 tops out at +7 dBm) and industrial-linux-and-radio.md updated. Datasheet checks confirmed RK3506G2 TA −20…+80 °C, RK3506J −40…+85 °C and MA35D1 4×CAN FD. Lint 227 pages 0 findings; build and git diff --check pass.

2026-09-27 19:05 [progress]

Fast-path fix in bizplan/product/switch/air/evaluations/esp32h2.md §6 and §7: the page still said X01 requires CAN FD (29-bit ID, 2 Mbit/s data phase, BRS) and therefore ruled out the TWAI as a CAN controller. X01 has been Classical CAN 2.0B at 500 kbit/s without BRS since 2026-09-11; the page now says the TWAI frame format matches and that a radio chip acting as the Air Hub CAN controller must meet Air Hub GW-10 / GW-11.

2026-09-28 00:26 [progress]

Air design appendix R0.3 (fast path, one page): §2.3 now states the sub-GHz devices in use across the line (Tag: Semtech SX1262; Air Hub LR: SX1302/SX1303 concentrator, Corecell module or SX1262 / LLCC68 / SX1276 star, plus CMT2300A for 433.92 MHz OOK; Air: none fitted), and the BLE + sub-GHz overlay candidate changes from CC1352P7 to its successor CC1354R10 (datasheet SWRS266B) with its limits recorded: one radio core time-multiplexed by DMM, no LoRa, two antennas, no NFC, and the +14 dBm sub-GHz peak on an end-of-life CR2450. No Level 1 value changed.

2026-09-28 00:38 [progress]

Completed task 20260928-0032. Added bizplan/research/engineering/wireless-soc-catalog.md, a reference catalogue of mainstream wireless SoCs, companion ICs and transceivers by vendor (Espressif, TI, NXP, Nordic, Silicon Labs, ST, Semtech and others) with sleep current, radio current, supply range, memory, security and notable peripherals per device, a table of what YBO products use today, and a by-purpose shortlist. Figures come from the datasheet revisions named in each row; cells that could not be fetched are marked as not verified. Listed in the engineering index. No product requirement changed. Lint 228 pages 0 findings; build and git diff --check pass.

2026-09-28 09:06 [decision]

Completed task 20260928-0836 and plan 20260928-0836. Key gains a BLE service link for configuration, diagnostics read-out and firmware update, and its MCU changes from STM32G0B1CE to the pre-certified ESP32-C6-MINI-1 module. Control stays wired: KEY-18 forbids any load command from the wireless interface, KEY-19 keeps the radio off outside a service window of at most 10 min opened by a physical action, KEY-20 holds the wired timing during service, and SEC-01 / SEC-02 / SEC-04 cover pairing, link protection and revocation. The owner accepted a relaxed static current, now ≤20 mA at 12 V (was ≤5 mA), because Key is permanently powered. Each Key unit carries at most 8 keys, the number the module's 22 GPIOs and one 36-channel LED driver hold without an expander while the second TWAI and an RS-485 UART stay reserved; more keys come from combining units, each its own CAN node, which replaces the former "32 keys and more on one platform" target. The legend backlight is driven per zone and the LED driver becomes LP5036. Key moves from the non-wireless compliance row to RED with EN 18031. P05-key.md R0.3, design R0.3, guide R0.4 (new V-03), brief, package index, new evaluation key/evaluations/wireless-service-mcu.md (options, static budget, wired-bus comparison, LCSC prices, unit key count), line spec R0.7 and line index, compliance matrix v1.4, product plan v1.6, open questions v1.5 (KEY-O-09…KEY-O-11), both business plan variants and the Sense citation updated. Rejected or deferred: ESP32-H2, nRF54L15 with an SPI CAN controller, STM32G0B1CE with a BLE module, TI CC2745R10-Q1 / NXP KW45, and digital outputs on Key (the request was for per-key status LEDs, already covered by KEY-04). Existing requirement IDs are unchanged. Lint 229 pages 0 findings; build and git diff --check pass.

2026-09-28 09:09 [decision]

Completed task 20260928-0908 and plan 20260928-0908, amending the uncommitted Key R0.3. Key now scales with expansion units instead of one MCU per eight keys: a base unit (ESP32-C6-MINI-1, CAN, BLE service link, up to eight keys) carries up to four expansion units (eight keys each, an I2C I/O expander with interrupt and a 36-channel LED driver, no MCU) for 40 keys on one CAN node; additional base units remain for panels that are far apart or must not depend on each other. New requirement KEY-21: loss of an expansion unit or a bus fault must not disturb the base unit's keys or CAN control, must not create key events, and marks the missing keys unavailable. Design §2.2 gives the expansion bus rules (position-coded addresses, ≤0.3 m, 100 kHz, bus switch so a stuck bus can be isolated, enumeration against the configuration) and the cost comparison at 40 keys: about 22 USD for five base units against about 7.8–9.5 USD for one base and four expansion units (LCSC retail). Guide V-06 adds expansion bus fault and hot-plug tests. Brief, indexes, line spec, product plan, open questions (KEY-O-11) and the evaluation page follow. Lint 229 pages 0 findings; build and git diff --check pass.

2026-09-28 09:20 [progress]

Corrected the Key expansion limit written earlier the same day (uncommitted R0.3). I2C address options were checked against the datasheets: LP5036 and IS31FL3236A four each, AW9523B four, TCA9555 eight. On one shared bus the base unit's own LED driver takes one address, so address pins alone allow three expansion units (32 keys), not the four (40 keys) stated before. The design now puts an 8-channel I2C switch (TCA9548A, LCSC 0.70 USD) on the base unit, one expansion unit per channel: up to eight expansion units and 72 keys, identical expansion boards with fixed addresses, and per-port isolation of a stuck bus. Spec, design §2.2, guide, brief, indexes, line spec, product plan, open questions and the evaluation page state eight units and 72 keys as the design target, with the practical ceiling (5 V rail current, harness count, polling latency, single point of failure) left to KEY-O-07 and KEY-O-11.

2026-09-28 [progress]

Fast-path documentation change. platform-combinations.md §2 now explains the three RK3506 variants from their Rev 1.1 datasheets: RK3506G2 (QFN128, 128 MB DDR3L in package, TA −20…+80 °C), RK3506B (FBGA333L, external DDR, TA −20…+80 °C, listed by Rockchip as an audio application processor, LCSC $4.96) and RK3506J (same FBGA333L, TA −40…+85 °C, A7 up to 1.2 GHz). RK3506B gets no combination: it has the G2 temperature grade but needs BGA and DDR routing, and costs more than RK3506J on LCSC. Correction: RK3506G2 and RK3506J were listed at 1.5 GHz; the J datasheet gives 1.2 GHz and the G2 datasheet gives no maximum. RK3506B datasheet added to refs/datasheets/air-hub/.

2026-09-28 13:32 [decision]

Completed task 20260928-1330 and plan 20260928-1330. Key R0.3 had been committed as 68fc761 in the meantime, so this change is recorded as Key spec R0.4, design R0.4, guide R0.5, line spec R0.8, product plan v1.7 and open questions v1.6. Key now has two expansion paths that can be used together. I2C expansion units (no MCU, behind the 8-channel I2C switch, up to eight) serve boards inside one assembly; the harness rule is 0.3 m without measures and about 2 m with shielded twisted pair and reduced speed, the latter an estimate to be measured. CAN expansion units (a small CAN MCU, a transceiver and an LED driver, up to 16 as a design target, bus up to 20 m) sit on an internal CAN bus driven by the ESP32-C6's second TWAI controller through its own transceiver. New requirement KEY-22 keeps the internal bus and the YBO CAN apart in controller, transceiver and connector; expansion units are not X01 nodes and the base unit is the only gateway. KEY-21 now covers both paths. New open item KEY-O-12 covers the internal CAN protocol, enumeration, bit rate, connector keying, MCU selection and expansion firmware; galvanic isolation is an option for separately powered panels. RS-485 and I2C bus extenders were compared and not adopted. Costs per eight keys (LCSC retail): I2C unit 0.85–1.26 USD, CAN unit 1.7–2.0 USD, base unit about 4.4 USD. Spec, design, guide, brief, indexes, line spec, product plan, open questions and the evaluation page updated. Lint 229 pages 0 findings; build and git diff --check pass.

2026-09-28 13:34 [progress]

Key R0.4 (still uncommitted), fast path: the legend backlight is one group per board, not per zone. The owner stated that each board, base unit and expansion units alike, carries keys, one RGB status LED per key and a single backlight that lights the labels in dim light. KEY-04 and the §2 lighting row say so; design §5 gives 24 RGB channels plus one backlight group of two to four channels (white, and red for night mode) per eight-key board, 26–28 of the 36 channels of one LP5036; product plan, open questions, brief and the evaluation page follow.

2026-09-28 23:19 [progress]

Pinned the Deploy workflow runner to ubuntu-26.04 instead of ubuntu-latest, so the image no longer changes underneath the release job when GitHub moves the ubuntu-latest label.

2026-09-29 00:12 [progress]

Claimed 20260929-0012-air-lock-nrf54l15 and drafted its plan: lock nRF54L15 as the first Air SoC and record CC2652R7 and CC1354P10 as compared and rejected. No specification was changed pending approval.

2026-09-29 00:16 [decision]

Completed 20260929-0012-air-lock-nrf54l15. Air spec R0.6 locks nRF54L15 (QFN48) as the only first-build SoC for Air 2 / Air 4 on 1×CR2450; the first build ships BLE firmware only while storage and the update layout are reserved so Zigbee or Matter firmware can run on the same hardware later. CC2755R10 is no longer an alternate. Design appendix R0.4 adds TI CC2652R7 and CC1354P10 to the compared platforms as rejected: CC2652R7 is not cheaper once NFC and storage are counted, draws about twice the RF current, cannot hold a Matter image with an update slot and lists no secure boot; CC1354P10 only adds sub-GHz, which Air does not fit, and its +20 dBm PA cannot run from a coin cell. nRF54L15 volume price remains open under AIR-O-03.

2026-09-29 00:27 [progress]

Claimed 20260929-0027-air-86-enclosure-and-peripherals and drafted its plan: move the Air outline to the 86-type wall plate and lock the peripheral circuit. No specification was changed pending approval.

2026-09-29 00:31 [progress]

Claimed 20260929-0031-air-433-encrypted-variant and drafted its plan: an Air 433 variant on nRF54L15 plus CMT2300A using the Air Hub encrypted 433 MHz link. No specification was changed pending approval.

2026-09-29 00:40 [decision]

Completed 20260929-0011-air-hub-two-tier-ssd202d (plan of the same ID; it superseded 20260928-2344-air-hub-first-build-rk3506j-cc1354p10, closed after the owner dropped RK3506J and CC1354P10). The owner set the Air Hub entry price to 59 USD instead of 249 USD, which caps landed cost at 19.18–22.13 USD under the product plan §5 rule. Air Hub spec R0.9 now has two products: Air Hub (AH-19: RV1106G3 chip-down with SPI NAND, SSD202D as the interchangeable alternate; ESP32-C6 as Wi-Fi uplink, BLE radio for Air, configuration channel and CAN controller; CMT2300A, 59 USD) and Air Hub Pro (AH-20: RK3506J stamp-hole core board with native CAN; EFR32MG21 for BLE / Zigbee / Thread by image; ESP32-C6 as Wi-Fi uplink and configuration channel; CMT2300A, 119 USD). RK3506 is used only as a stamp-hole core board because the SoC carries no storage; Forlinx FET3506J-S, Vanxoak HD-RK3506J and MYiR MYC-YR3506J are the sources. Air Hub LR is withdrawn with GW-08, GW-12 and V-14. GW-09 is now an adaptive 433 MHz link on both products: YBO devices use per-device keys, AES-128-CCM and a frame counter so recorded frames are rejected; third-party fixed-code and learning-code devices are learned, received and transmitted as a lower-trust source that cannot bind critical loads, with transmit shown as "sent, unconfirmed". New GW-13 covers the ESP32-C6 configuration channel over Wi-Fi and BLE. BOM (1k, LCSC retail): Air Hub 25.8–40.6 USD, over its cap everywhere (gap 3.7–21.4; 1.7–14.9 after a ≤4 USD connector-plus-enclosure target), recorded in spec §2.1 and AIR-O-03 rather than closed by a price rise; Air Hub Pro 34.6–46.7 USD against a 38.68–44.63 cap. CC1354P10 was compared with EFR32FG28 on 2.4 GHz (TI SWRS267B, Silicon Labs Rev 1.1) and then rejected on price (10–14 USD, time-shared bands); the comparison is kept in the platform evaluation §7.2. The Tuya ZS3L module (EFR32MG21 F768) was reviewed and not used. AIR-O-11 is closed; AIR-O-12 is now the Tag receiver question; AIR-O-13 covers the 433 link specification and a 315 MHz variant. Design appendix R0.7, guide R0.5, brief, index, the three evaluation pages, switch line spec R0.9, brief and index, product index, product plan §P5 / §5 / radio table, open questions v1.7, compliance matrix v1.5 and the wireless SoC catalogue follow. Air's 433 variant is out of scope; P12 Tag and Air references to Air Hub LR are tracked in 20260929-0037-tag-receiver-after-air-hub-lr-withdrawal. Lint 229 pages 0 findings; build passes.

2026-09-29 01:00 [decision]

Completed 20260929-0027-air-86-enclosure-and-peripherals. Air spec R0.7 moves the outline to the 86-type plate (86×86 mm, ≤12 mm) on a back plate with 60 mm fixing holes for an 86-type box, adhesive or panel screws, with a clip-on front module so the battery is changed without removing the back plate; new AIR-12 defines a local factory reset (hold keys 1 and 2 while inserting the battery for ≥5 s) that erases only the Air's own credentials, while re-joining still needs the hub's authorized window. Design appendix R0.5 locks the peripheral circuit: 32 MHz and 32.768 kHz crystals, internal DC/DC, P-MOSFET reverse protection, low-leakage storage capacitor, SAADC internal VDD measurement, PCB inverted-F antenna, NFC loop, one red/green LED and tactile switches. Guide R0.3 adds the matching tests and replaces the obsolete D0 RF comparison with an nRF54L15 board demonstration.

2026-09-29 01:03 [decision]

Completed 20260929-0031-air-433-encrypted-variant. Air spec R0.8 adds an Air 2 433 / Air 4 433 model on a separate board with a single TI CC1310 (433.92 MHz, China and Europe first) as a YBO-class device of the Air Hub 433 MHz link: per-device key by ECDH over 433 authenticated with a battery-compartment pairing code inside the hub's authorized window, AES-128-CCM on every frame, persisted counters so recorded frames are always rejected, and results protected the same way (new AIR-11). AIR-O-09 is closed; new AIR-O-14 freezes the link parameters with the hub, CC1310 to CMT2300A interoperability, the 433 battery budget and antenna range. The BLE model stays nRF54L15 alone. Design appendix R0.6 records CC1310 against CMT2300A plus HC32L130 and CC1312R, a no-continuous-receive power rule and the key and counter handling; guide R0.4 adds the 433 tests.

2026-09-29 02:55 [decision]

Completed 20260929-0235-air-hub-entry-adds-efr32mg21. The owner compared entry Air Hub variants (adding EFR32MG21 with and without the 433 MHz link, and without the ESP32-C6) and chose to add EFR32MG21 and remove the 433 MHz link ("去掉433"). Air Hub spec R1.0: both products now carry EFR32MG21 for Air's BLE with Zigbee / Thread images (GW-07 on both); the ESP32-C6 is Wi-Fi uplink and configuration channel on both and CAN controller on the entry product, and no longer Air's radio. The 433 MHz link (GW-09, CMT2300A) is Air Hub Pro only. Entry BOM 27.8–43.2 USD (+1.7–2.9); against the 59 USD cap the gap is 5.7–24.0, or 3.7–17.5 with the connector plus enclosure at 3–4 USD; recorded, not closed by a price change. The BOM difference to Air Hub Pro narrows to 3.5–6.8 USD; Pro pricing is to be revisited with core-board quotes. Design appendix R0.8, guide R0.6, brief, index, platform evaluation §8.4 and §10, switch line spec R1.0, brief and index, product plan, open questions, compliance matrix and wireless SoC catalogue follow. Air's 433 variant still names "Air Hub" as its hub; aligning it to Air Hub Pro is added to 20260929-0037-tag-receiver-after-air-hub-lr-withdrawal.

2026-10-06 04:50 [decision]

Completed 20261006-0315-air-hub-reference-board-and-schematics. The owner asked for the Air Hub hardware plan, component lists and schematics with the Vanxoak core board for the Pro, then moved the entry product to an SSD2351 core board ("用SSD2351核心板") after RV1106G3 was found at 22.67 USD @30 on LCSC (5.56 USD @100 on 2026-09-29). Air Hub spec R1.1: AH-19 is now platform H15, the MYZR SSD2351 stamp-hole core board (SSD2351D 128 MB or SSD2351Q 256 MB, single 3.3 V supply, rated −20…+70 °C) with an external RMII PHY; EFR32MG21 and the ESP32-C6 (Wi-Fi, configuration, CAN) are unchanged. Entry BOM restated from the part list as 28.4–35.4 USD, gap to the 59 USD cap 6.3–16.2 (4.3–9.7 with connector plus enclosure at 3–4 USD). New Level-2 page P05-air-hub-design-reference-board.md holds the pin allocation of both core boards, the power tree, the part lists and the schematic previews; design appendix R0.9 moves the 5 V buck to LMR36520 (2 A) because LMR36506-Q1 (0.6 A) is below both boards' 5 V peaks, the 3.3 V rails to TPS62A02 and the PHY to DP83825I. Guide R0.7, package and line indexes, line spec R1.1, product plan, open questions and both evaluations follow; the 2026-09-27 temperature decision is amended for H15 (no margin at 60 °C ambient until a written chip grade and the thermal test exist). KiCad 10 projects were generated outside this repository under /srv/ybo/switch/air_hub/ and /srv/ybo/switch/air_hub_pro/ (the superseded SSD202D socket design moved to air_hub_r0_ssd202d/); both pass ERC and a pin-by-pin netlist check against the generator's intended connections. Not verified: core-board prices in writing, the SSD2351 chip datasheet and temperature grade, the CMT2300A RF network topology (placeholder), footprints and layout.

2026-10-06 06:00 [progress]

Completed 20261006-0452-air-hub-pro-first-board after the owner said to start with the Pro ("可以开始先做pro"). Schematic corrections shared by both boards: the CMT2300A RF network now follows data-sheet figure 2 (it was a placeholder order), LMR36520 uses the table 8-1 values (10 µH, 2 x 4.7 µF input), and the DP83825I strap defaults were checked against tables 6-9 to 6-11. Air Hub Pro has a first routed board in /srv/ybo/switch/air_hub_pro/: 110 x 92 mm, 4 layers (outer routing, In1 GND, In2 +3V3), project-local land pattern for the Vanxoak core board, script placement plus Freerouting. KiCad DRC: no unconnected items, no clearance or short errors, no schematic-parity differences; warnings only. Gerbers, drill, position file and renders are exported. Not proven by this board: RF trace impedance and matching (autorouted), the board outline (no enclosure yet), the core-board land pattern against the vendor DXF. Reference-board page R0.2 records the board and these limits.

2026-10-06 08:35 [progress]

Completed 20261006-0822-air-hub-emc-safety-certification. The owner asked whether Air Hub can pass EMC testing and safety certification and for certification in the product specification. New evaluation evaluations/emc-safety-certification.md: the design is not ready for testing as it stands but shows no blocker in principle. A design-rule pre-compliance run on the Air Hub Pro first board gave 87 findings (no EMI filter at the harness terminal, Ethernet and USB pair skew and layer changes, reference-plane gaps, ESD parts away from connectors, buck input loop); the review adds a 600 W input TVS against Core's 6.6 kW part, no ESD protection at the SMA port, two chip-down transmitters without module certificates, the EN 300 328 power-spectral-density limit that keeps EU BLE advertising and 802.15.4 below the part's +20 dBm, and FCC 15.203 on the detachable 433 MHz antenna. Electrical safety is low risk (8–32 V DC only). Air Hub spec R1.2 adds REG-01…05 and AIR-O-14 and restructures §7 around the standards per market; guide R0.8 adds V-15 pre-compliance and V-16 formal testing; reference-board page R0.3 lists the fixes. No schematic or board change was made: the fixes alter the BOM and need the owner's choice of certification path. Not verified: standard versions, limits and port classification (a lab's test plan), module certificates, test cost and schedule.

2026-10-06 12:45 [decision]

Completed 20261006-1156-air-hub-highest-certification-level. The owner decided to develop Air Hub to the highest certification level with chip-down radios ("按最高级别产品认证要求开发 用芯片不用模组"; read as EFR32MG21 and CMT2300A chip-down, the ESP32-C6 stays a pre-certified module). Spec R1.3: the development level is the strictest of EN 301 489-1 / EN 55035 / EN IEC 61000-6-2, IEC 60945 and IACS UR E10 (ESD ±8 kV contact / ±15 kV air, 10 V/m, EFT ±2 kV / ±1 kV, 10 V conducted), ISO 7637-2 level IV and ISO 16750-2 load dump test A on the supply, IEC 60945 emission limits as a requirement, CB report plus NRTL listing and V-0 materials for safety, new REG-06 marine environment; AIR-O-14 records chip-down and one reverse-polarity SMA and keeps markets, the lab plan, class type approval and ignition protection open. Schematic of both boards: 5 kW input TVS, time-lag fuse with DC rating, −60 V reverse-polarity FET, common-mode choke and pi filter, RC termination of the RJ45 shield, ESD suppressor at the 433 MHz port. Entry BOM restated as 30.1–37.1 USD (gap 8.0–17.9). Air Hub Pro board revision B (110 x 102 mm) was re-placed and re-routed; KiCad DRC is clean. The EMC rule check still returns 87 findings and a score of 0: the schematic gaps are closed, the remaining findings come from automatic placement and routing (pair matching, layer changes, return paths, buck input loop). A manually laid-out board is required before any pre-compliance scan. Not verified: every added part value on the bench, the chosen levels against a lab's test plan.

2026-10-09 11:25 [decision]

Completed 20261009-1106-air-hub-mini-esp32c6. The owner asked for a third, smaller Air Hub that uses only an ESP32-C6-MINI-1, an EFR32MG21 and a LAN port, and decided that it keeps CAN, that existing prices stay, that EFR32MG21 switches function by signed image with the ESP32-C6 as the flashing channel, and that Wi-Fi stays ("1，需要带 2，不变 3，通过软件切换不同的功能，c6做刷机通道 4，保留"). Air Hub spec R1.4 adds Air Hub Mini (AH-21, platform H16, 49 USD): ESP32-C6-MINI-1 as the only controller without Linux, EFR32MG21 for Air's BLE with Zigbee / Thread images flashed by the C6 (GW-07), W5500 for Ethernet, the C6's Wi-Fi as second uplink, Wi-Fi and BLE as configuration channel, TWAI as CAN controller. New §2.5 lists what the Mini provides and does not provide (no local MQTT broker, no Matter controller, no P09 hosting, no 433 MHz; Zigbee / Thread host capacity on the C6 is unproven and not committed). New GW-14 replaces the Linux / C6 separation of GW-11 on this product: CAN frames only from the authorisation path, network and configuration inputs parsed in tasks with no CAN interface, secure boot, flash encryption, signed OTA with anti-rollback, locked debug and download modes, bounded reset with declared outage. New open item AIR-O-15. "Air Hub needs Linux" in §1 is now limited to Air Hub and Air Hub Pro. BOM by the reference-board method: electronics 16.8 USD (Air Hub 23.1), total 23.8–30.8 against a 15.93–18.38 cap, over by 5.4–14.9 (3.4–8.4 with connector plus enclosure at 3–4 USD); recorded, not closed. Design appendix R1.0 (§3.1 task-domain isolation, flashing, W5500 in MAC raw mode, memory and pin limits), reference-board page R0.5 (§2.4 pin allocation of the MINI-1 module, 21 of 22 GPIO used, marked unverified; §6.1 BOM), guide R1.0 (GW-14 tracing, V-03 CAN injection from the network side, V-13 outage), brief, index, platform evaluation §8.5, line spec R1.2, indexes, product plan, open questions v1.8, compliance matrix v1.6 and the wireless SoC catalogue follow. No schematic or board was generated. Note: the product plan §5 row still carries the earlier Air Hub figure 28.4–35.4 while the spec has 30.1–37.1 since R1.3; left unchanged here. Lint 231 pages 0 findings; build and git diff --check pass.

2026-10-09 11:35 [decision]

Completed 20261009-1114-air-hub-mini-wroom-module. The owner moved Air Hub Mini from the ESP32-C6-MINI-1 module to ESP32-C6-WROOM-1 ("用ESP32-C6-WROOM-1模组"). Air Hub spec R1.5: the Mini uses ESP32-C6-WROOM-1-N8 (8 MB flash, 23 GPIO with IO14 not brought out, −40…+85 °C only, 18.0 × 25.5 × 3.1 mm, LCSC 3.07 USD @1.3k). The pin table in the reference-board page R0.6 is redone from the WROOM-1 pin table (UART CTS moves to IO10; IO11 and the IO15 strapping pin are spare), still marked unverified. WROOM-1 gives one GPIO more than MINI-1; the practical gain is the 8 MB flash for two OTA slots plus both EFR32MG21 images. BOM: electronics 17.0 USD, total 24.0–31.0, over the 49 USD cap by 5.6–15.1 (3.6–8.6 with connector plus enclosure at 3–4 USD). Design appendix R1.1, guide, platform evaluation §8.5 and the product plan follow. Air Hub and Air Hub Pro keep ESP32-C6-MINI-1. Lint, build and git diff --check pass.

2026-10-12 23:15 [decision]

Completed 20261012-2303-air-hub-lock-rk3506g-rk3506j. The owner dropped the SigmaStar path and locked the Linux Air Hub products on RK3506 stamp-hole core boards ("抛弃ssd202d方案，锁定3506g和 3506j方案，分别是128+256 或者256+256，另外一个是esp32-c6 作为主控的方案"). Air Hub spec R1.6: Air Hub (AH-19) moves from the SSD2351 core board to an RK3506G core board (new platform H17, Vanxoak HD-RK3506G-128F256LW, 128 MB + 256 MB NAND, −20…+70 °C, native CAN); Air Hub Pro stays on the RK3506J core board (256 MB + 256 MB NAND); Air Hub Mini is unchanged. H1, H2 (SSD202D) and H15 (SSD2351) are marked dropped and kept as evaluation records. The two Vanxoak boards are pin-compatible, so both products share one baseboard, with the 433 MHz link unpopulated on Air Hub. CAN on Air Hub is now native, the ESP32-C6 is Wi-Fi uplink and configuration channel only, and GW-11 has no selected product left. The owner also asked whether a Wi-Fi + Bluetooth combo module could replace the ESP32-C6 (saving about 1–1.5 USD) and kept the C6 ("保留C6"). The RK3506G board has no published price; with a placeholder of 8.5–12.4 USD the Air Hub BOM is 31.4–42.3 USD, over the 59 USD cap by 9.3–23.1 (previously 30.1–37.1 and 8.0–17.9). Design appendix R1.2, reference-board page R0.7, guide R1.1, platform evaluation §8.6, switch line spec R1.3, product plan v1.8, open questions v1.9 and the temperature deviation record follow. No schematic or PCB was regenerated: the SSD2351 schematic project is superseded and its five diagrams are no longer referenced. Lint, build and git diff --check pass.

2026-10-13 01:50 [progress]

Completed 20261013-0905-air-hub-shared-carrier-and-mini-board after the owner's design updates (Air Hub on an RK3506G core board sharing the Pro carrier, Air Hub Mini on ESP32-C6-WROOM-1-N8, no ignition protection and no class type approval) and the request to handle the PCB and schematics. Checked the vendor's RK3506G pin table against the J table: 8 of 128 pins differ (FSPI 40–45 and USB OTG0 ID / VBUSDET 57–58 are NC); the carrier uses only pin 58 (VBUS sense), harmless on the G board per the vendor's USB note. The shared carrier is now one generator with two variants: air_hub_pro (433 MHz link fitted, HD-RK3506J-256F256LI) and air_hub (25 link parts DNP, HD-RK3506G-128F256LW); both pass ERC and the netlist check with identical nets, and the Pro board was re-placed and re-routed on the new netlist with a clean DRC. The abandoned SSD2351 project moved to air_hub_r1_ssd2351/. New air_hub_mini project: WROOM-1 symbol and land pattern, W5500 per its data sheet, EFR32MG21 with flow control plus reset and bootloader pin driven by the C6, TJA1463 with pulled-up mode pins; the netlist check caught and fixed a short of the Ethernet pairs to 3.3 V from a power-symbol stub; first board 90 x 80 mm, 4 layers, DRC clean; EMC rule check 72 findings of the same layout-driven classes as the Pro board. Reference-board page R0.8 records all of it. Not verified: the WROOM-1 land pattern against the Espressif footprint, the W5500 magnetics connection against the WIZnet reference, the Gecko bootloader entry pin, RK3506G device-mode USB without VBUSDET.

2026-10-13 02:30 [progress]

Completed 20261013-0200-air-hub-hardware-handover-package. The owner asked for drawings to hand the Air Hub boards to hardware engineers. Package at /srv/ybo/switch/handover/air-hub-2026-10-13/ (workspace, not in this repository): block diagrams and power trees for the shared Linux carrier and the Mini (SVG, PNG, JSON source), schematic PDFs, the three KiCad projects with their project footprints, board renders, layer PDFs, Gerbers and drill archives, position files, BOMs with the DNP column, pin maps (core board to carrier net with the HD-RK3506G differences; WROOM-1 to Mini net), datasheets and the governing documents, plus an English README that states what was verified (ERC, netlist check, DRC, pin-table comparison) and what the engineers must do (manual layout, land-pattern checks against vendor files, bench verification of datasheet-derived circuits, core-board vendor confirmations, production connector, pre-compliance). Guide R1.2 adds §8 with the package contents and the work order in Chinese.

2026-10-14 00:36 [decision]

Completed 20261014-0022-air-hub-unify-esp32-c6-mini-module. The owner asked for one ESP32-C6 module across the Air Hub family and chose ESP32-C6-MINI-1-N4 ("用Mini-1-N4") after comparing MINI-1-H4 and WROOM-1-N8. Air Hub spec R1.7: Air Hub, Air Hub Pro and Air Hub Mini all use ESP32-C6-MINI-1-N4; the Mini moves back from WROOM-1-N8 (4 MB flash, 22 GPIO, 13.2 × 16.6 mm). Because 4 MB cannot hold two full application images with a Matter bridge, the Mini uses an updater image plus a single application: the application reboots into the updater, which downloads, verifies and writes the application; the application updates the updater. Costs recorded: control is unavailable for minutes during an update, no previous application is kept on the device, and the stock ESP-IDF anti-rollback may not support this layout (AIR-O-15). The Mini has no freely usable GPIO left (only the IO15 strapping pin). Mini BOM: electronics 16.8 USD, total 23.8–30.8, over the 49 USD cap by 5.4–14.9. Design appendix R1.3, reference-board page R0.9, guide R1.3, platform evaluation §8.5 and product plan v1.9 follow. The WROOM-1 Mini schematic, first PCB and handover material of 2026-10-13 are marked superseded and were not regenerated. Lint, build and git diff --check pass.

2026-10-15 00:03 [decision]

Completed task 20261014-2350: the Air Hub documents now follow the schematics, boards and handover package of 2026-10-14. Spec R1.8: supply 12/24 V nominal, 9–36 V continuous (decision record 2026-10-14-air-hub-supply-9-36v); core boards fixed to Vanxoak HD-RK3506G-128F256LW (Air Hub, −20…+80 °C per the data sheet) and HD-RK3506J-256F256LI (Air Hub Pro), other boards kept only as evaluation records. Design appendix R1.4, guide R1.4 and the platform and EMC evaluations follow. Reference-board page R1.0 is rewritten against the hardware: carrier and Mini pin tables, K7805-2000R3 5 V module on the carrier, long-press reset, choke wiring, part list, 6-layer boards (carrier rev C, Mini rev B) with ERC/DRC/SPICE/EMC-check results, and new schematic and PCB images. The earlier claim that the Mini hardware was still on WROOM-1 is corrected. Open for the hardware owner: the 33 V stand-off TVS conducts below 36 V and must be replaced (AIR-O-04); the carrier PCB render predates the K7805 change.

2026-10-21 15:14 [progress]

Completed task 20261020-2336-key-wiring-box-external-buttons: Key Box 36, a control box for 36 external bicolour marine pushbuttons (Key Box 18 = the same board half fitted). Four TE AMPSEAL 35 headers (one colour each), 4 x TIC12400 inputs on a 10 V VS rail (only IN0–IN9 sink current, so one chip per connector), 9 x NCV7240B low-side outputs in one SPI chain (72 lamp / general outputs), YBO CAN (TJA1463) plus isolated NMEA 2000-ready CAN (ISO1042), LM74800 with a 34.2 V clamp, ESP32-C6-MINI-1. Spec, design appendix and guide R0.6 and the brief carry the box (KEY-23…KEY-28, KEY-O-13, pin table, enclosure about 204 x 134 x 38 mm). In /srv/ybo/switch: schematic ERC 0, PCB 180 x 110 mm, 4 layers, DRC 0 unconnected / clearance / short; colour-keyed header, plug and enclosure models (CadQuery, outline only, not tooling data) with ray-traced renders and STEP exports; handover package key-2026-10-14 refreshed. Open: AMPSEAL pin-1 orientation against a sample, TIC12400 inputs above VS on the bench, N2K stack and certification, isolation creepage, enclosure sealing and tooling.

2026-10-22 20:10 [decision]

Completed task 20261014-1417-business-plan-consistency-refresh (plan approved 2026-10-22 after a second pass focused on the P05 Switch line). Business plan v2.2 (zh and en in lockstep): Hub replaced by Mate and the Hub and Mate matrix rows merged; the "Key and Air" row rewritten as the Switch line (Key, Key Box 36, Air, Air Hub Mini / Air Hub / Air Hub Pro with prices); Control (T2) and View (T3) added and every matrix row carries its tier; Studio worded as governed open access and the one-hour handover marked as a target; Air Hub and Air Hub Mini cost gaps disclosed in §11 with a new risk 9; refit bundle prices and the EUR 2,400 ASP marked as carried over from the retired Core prices; one staffing statement, with Switch firmware and Air Hub host software recorded as not yet staffed; a current-status note at M1; funding figures and header aligned. Product plan v1.10: P5 Air Hub rows state the current three products, USB-C PD plus M8 9–36 V supply and commercial IP54; Key Box 36 added by role with a link to the Key spec; §1 MCU, wireless and Mate rows, T0/T1 tiers, staffing, §3 links and the regional radio matrix follow the Switch line; §5 cost rows updated and Key Box 36 added as TBD; §6 items 3 and 4 updated; a note defines remaining "Hub" mentions as the Mate hardware side. No product-package file changed. Follow-ups not done: Hub references in open-questions.md, compliance-matrix.md and ppt-build-guide.md, and AIR-O-09 still listed as open in open-questions.md.

2026-10-23 11:30 [decision]

Completed task 20261022-0322-key-box-n2k-connector. Key Box 36 CAN2 (ISO1042, isolated) leaves the box through a front-mount M12 A-coded 5-pin male socket on the lid (NMEA 2000 Micro-C: 1 shield, 2 NET-S, 3 NET-C, 4 NET-H, 5 NET-L), wired to header J7 in the isolation island; no termination in the box; the bus side is powered from NET-S. Spec, design appendix, guide R0.7 and the key-box README carry it; the enclosure model and renders show the socket.

2026-10-23 11:30 [decision]

Completed task 20261022-0420-key-box-rs485-analog-inputs (spec, design appendix and guide R0.8, brief updated). Key Box 36 now has:

• RS-485 (THVD1406, non-isolated) on UART0 at J2 29-32 / 34.
• Eight software-configurable analog inputs (0-190 Ohm or 4-20 mA, TIC12400 ADC plus a 74HC595 mode latch on IO8) on J3 / J4 30-35, with a 24 V loop supply (LM51551 boost with pass-through above 24 V).
• Two 1 A high-side outputs (TPS2H160-Q1 B) on J2 35 / J4 29; three AUX inputs.
• Board monitoring: INA186 box current, two NTCs, the 3.3 V rail.
• A 5 A box power path (6.3 A fuse, IPB200N25N3 D2PAK, VPROT plane).

Button behaviour (KEY-23, KEY-31): momentary short-press / long-press / hold-to-run / interlocked; latching keys act only on a position change.

The MCU changed to ESP32-C6-WROOM-1-N8 (8 MB flash, 23 GPIO): DO_EN moves to IO10 and IO11 is spare. Key 4 / 8 panels stay on MINI-1-N4. RESET / SERVICE buttons and the status LED move to the PCB top side; there is no lid button. SERVICE short press opens the BLE service window; holding it for 10 s or more is factory reset (SEC-04).

PCB (180 x 110 mm, 4 layers) results:

• Schematic ERC 0; DRC 0 unconnected / clearance / short with schematic parity 0.
• Seven nets were hand-routed after Freerouting. C3 is now 0402.
• The antenna keepout and the CAN2 island no-pour rule now apply to the inner planes as well.
• Floating outer-layer heavy-current pours were removed; the generator is fixed for both.

Open: the Q1 clamp SOA at 5 A against a 200 V / 350 ms load dump (KEY-O-13, D1); the service window without opening the lid (KEY-O-09); bench checks of the TIC12400 inputs above VS and of the analog-input calibration; the WROOM-1-N8 price is unverified.

2026-10-23 12:00 [progress]

The ESP32-C6-WROOM-1-N8 price was verified by the owner at about USD 3, about USD 0.9 below the MINI-1-N4 LCSC price. The Key Box 36 cost estimate in the design appendix drops to about CNY 1065.

2026-10-23 12:30 [progress]

Key Box 36 analog-input limits written into the spec (§2.1) and design appendix (§2.3): no 0–5 V / 0–10 V voltage mode, no senders above 190 Ω (e.g. 240–33 Ω), sampled once per 5–10 ms scan. The hardware README now has DO_EN on IO10 (was IO14), the same limits, and two more bench items (VLOOP at 200 mA and ALOOP short hiccup, high-side outputs with inductive loads).

2026-10-23 17:00 [progress]

Key Box 36 cost: the owner verified compatible AMPSEAL-type connectors (four sets of headers, plugs and terminals) at about CNY 120 in total. The design appendix keeps the TE genuine estimate (about CNY 600, box about CNY 1105, 36-key system about CNY 1725) and adds the compatible case: box about CNY 625, 36-key system about CNY 1245 (about 35 per key). Task 20261023-1233 also moved the Key Box PCB to 6 layers (about CNY 25 more, not verified) after the 4-layer flow left 49 items on its first try.

2026-10-23 19:10 [progress]

Key Box 36 power modules (task 20261023-1233, owner confirmed): +5V now comes from a Mornsun K7805T-1000R3 SMD module and the box input range becomes 9-32 V (panels stay 8-32 V); the TIC12400 VS stays on the LM317L because the K7809 needs 13 V in. The transmitter loop supply is a Mornsun URB2424YMD-6WR3 isolated module (fixed 24 V / 250 mA, 0V tied to GND), replacing the LM51551 boost and BOOST_OFF. The TPS2H160 gets the 1k || BAT46W GND network. Spec §2.1 and KEY-17, design appendix §2.3, guide V-11 and the board README are updated; the box cost estimate becomes about CNY 1140 genuine / 660 with compatible connectors (module prices not verified).

2026-10-24 00:20 [decision]

Air BLE first version is the Raytac AN54LV-P15 certified module (task 20261023-2353, owner decision 2026-10-22/23); the chip-down nRF54L15 QFN48 design becomes the cost-down variant with switch condition AIR-O-15. Spec R0.10 (§1, §2, §7 module-based certification path, AIR-O-03, AIR-O-15), design appendix R0.8 (§2.1 module row, AN54LQ-P15 fallback, Ebyte E73-2G4M54LP(15) set aside for lack of module certificates; §3 host circuit and antenna keep-out; §5 per-build key and LED pins), guide R0.5 (§2, §5, §6, §7), the Air index and the product-plan / compliance-matrix one-liners are updated. Both boards exist in the switch workspace (air-mod/, air/) with ERC 0 and DRC 0 errors.

2026-10-24 19:20 [decision]

Completed task 20261023-1233. Key Box 36 board regenerated with the ADS7038 and its AVDD / DECAP / DVDD capacitors fixed next to the ADC (C623 had been placed about 25 mm away), the URB module holes at the recommended 1.5 mm, and 3D models for both Mornsun modules. The 6-layer flow left one unconnected item (U1 pin 12, VFET), joined by hand; DRC with schematic parity reports 0 errors and 0 unconnected items. Every BOM line now has a manufacturer and MPN; generic passives, the LED and the 0.1 % resistors also carry LCSC codes (BOM gains Manufacturer and LCSC columns). The board has not had a human layout review or a prototype run; the README lists the open review items.

2026-10-24 20:15 [decision]

Completed 20261024-2000: Air Hub and Air Hub Pro now use radio modules instead of chip-down radios. 2.4 GHz is the RF-star RF-BM-MG24B2 (EFR32MG24, +19.5 dBm, PCB antenna); 433 MHz on Air Hub Pro is the HopeRF RFM310-433S2. The carrier was regenerated and rerouted (DRC clean, 128 parts instead of 164); spec R1.15, design appendix R1.10 and reference board R1.7 carry the new costs (Air Hub $35.8-45.0, Pro $43.3-48.6). The Air Hub Mini is handled separately by the owner.

2026-10-24 22:10 [decision]

Air Hub Mini power review (task 20261024-2200, owner decision 2026-10-24). Off-the-shelf 3.3 V modules were checked against the Mini input range (5 V USB through a Schottky up to 36 V M8, 53 V TVS clamp, 0.56 A peak): Mornsun K7803 parts need at least 6 V, the K7803JT-500R3 gives 0.5 A, the TI TPSM365R6 0.6 A, so the discrete LMR36520 stays. The Mini M8 input switch (LM74502, DMN6040SSDQ, two capacitors, VBUS divider) becomes a 60 V Schottky diode-ORed with the USB Schottky: M8 supplies the board whenever it is connected, USB-C 5 V only without M8; the Linux carrier keeps USB-C priority. Spec R1.17 (§2.3, §2.4, GW-05), design appendix R1.12 and reference board R1.9 are updated; the board drops from 52 to 47 placed parts. The Mini generators also moved to their own tools/mini/ set in the switch workspace.

2026-10-24 21:15 [decision]

Completed task 20261024-2130: the Air Hub / Air Hub Pro Linux carrier revision D part reduction approved by the owner. The USB-C path uses a B360A Schottky instead of the LM74800 ideal diode (a 5 V-only USB source without M8 no longer runs the board; bench item), the CAN transceiver is the 3.3 V TCAN3413 (not SIC), the long-press reset, RECOVERY / MASKROM keys, power and CAN LEDs, debug and SWD headers and the SDIO_CLK 0 R are gone (test pads instead), and the Air Hub variant leaves the Ethernet block unfitted (Wi-Fi only). Placed parts drop from 127 to 103 (Pro) and 122 to 71 (Air Hub); per-board parts at 100 pcs fall from $52.28 to $48.24 and $42.69 to $37.15. The Pro board was rerouted with DRC 0. Spec R1.18, design appendix R1.13, reference board R1.10, guide R1.10, the EMC evaluation and the product plan are updated.

2026-10-24 22:45 [progress]

Completed task 20261024-2230: Air Hub Mini enclosure concept (PC/ABS V-0 base and lid, about 97 x 86 x 24 mm, USB-C in the back wall, M8 socket in the left wall, light pipes and a silicone PAIR key) modelled in OpenSCAD under tools/mini/enclosure/, with four renders and base / lid STL files in air-hub-mini/enclosure/. Reference board R1.11 shows the 3D board view and the enclosure views.

2026-10-24 23:40 [progress]

Completed task 20261024-2330: the Air Hub Mini PAIR key and SYS / RADIO LEDs move to the right board edge (EVQ-P7A01P side-push key, APA1606 right-angle LEDs) and the enclosure becomes a plain rectangular box with a flat, unpierced lid, bottom screws into lid posts, and the key cap and light pipes in the right wall. DRC 0, EMC 0 errors; per-board parts $18.13. Spec R1.19, design appendix R1.14, reference board R1.12.

2026-10-24 23:50 [progress]

Completed task 20261024-2345: the Air Hub Mini enclosure concept is restyled as a black set-top box (one-piece shell with matte top and gloss sides, 12 mm corner radius, inset rubber foot, no visible seam or screw from above), and the board outline gets 7 mm corner radii. DRC 0, EMC 0 errors. Reference board R1.13.

2026-10-25 00:00 [progress]

Completed task 20261025-0000: the Air Hub Mini USB-C, PAIR key, LEDs and M8 socket now sit on one side (left board edge, one enclosure wall); the USB pair runs straight on L1 without vias. DRC 0, EMC 0 errors. Reference board R1.14.

2026-10-24 23:49 [decision]

Completed task 20261024-2230 (Air Hub / Air Hub Pro PCB layout, appearance design and handover update). The revision D Linux carrier was re-placed for the enclosure: 110 x 102 mm became 104 x 90 mm, the RF-BM-MG24B2 moved to the middle of the right edge (antenna end flush, about 75 mm from the ESP32-C6 antenna), the PAIR key, the two LEDs and the service pads are grouped in the lower right corner, and RMII TXD0, REFCLK and CLK50 are kept on L1 (locking all RMII lines to L1 left 8 of them unrouted). The board was rerouted: DRC 0 unconnected, 0 errors, 0 schematic-parity issues; SPICE 22/22; EMC pre-check 58 findings with 23 errors (was 24): 8 RJ45 pin-field plane gaps, 11 RMII / PHY-control return vias, 2 I/O filter false positives, buck harmonics and the USB_CON_DP layer change. A CadQuery enclosure appearance model was added (industrial style, light grey PC/ABS base, dark grey lid, about 112 x 96 x 26 mm, side-wall RJ45 / RP-SMA / USB-C / M8, light pipes and silicone PAIR key, lid screws through the PCB mounting holes, wall ears; Air Hub variant with blanked RJ45 / SMA) with renders, assembly STEP and a board / enclosure interference check (0 overlaps); the OpenSCAD concept was retired. Reference board R1.15 (section 7.3 layout zones, enclosure and renders), guide R1.11 (section 8 now points to the product directories instead of the stale handover/air-hub-2026-10-13 package) and the EMC evaluation were updated.

2026-10-25 00:10 [progress]

Completed task 20261025-0010: the two Air Hub Mini LEDs become one right-angle RGB status LED (Kingbright APFA3010LSEEZGKQBKC, red IO11, green IO6, blue IO7) behind a single light pipe. DRC 0, EMC 0 errors; per-board parts $18.22. Reference board R1.16, spec R1.20, design appendix R1.15.

2026-10-24 23:57 [decision]

Completed task 20261024-2357: on the owner's request the Air Hub / Air Hub Pro enclosure appearance model was restyled as a black set-top box (one-piece shell with R12 corners, matte top and gloss sides, nothing but the logo, two pinhole light pipes and a flush PAIR disc on the top; recessed base plate with gasket, rubber ring and screws from below; about 112 x 97 x 27 mm, no wall ears). The board corners were rounded to R6 to fit the shell's inner corners (DRC 0, EMC unchanged). Reference board, guide and product READMEs updated.

2026-10-25 02:47 [decision]

Key Box 36 part-count reduction (task 20261024-2322): output drivers move from 9 x NCV7240B to 9 x TLE75008-ESD (42 V clamp, VS from the 10 V rail, VDD 3.3 V); the 131 input / output ESD capacitors become 30 four-way 10 nF CA0612 arrays (inputs 15 nF -> 10 nF, ESD test to confirm); the 10 V rail uses an LM317 in DPAK; the loop supply becomes URB2424YMD-10WR3 (24 V / 416 mA). The AD74412R analog front end was evaluated and rejected by the owner: with the datasheet circuit it saves about 12 parts and adds about 13 USD per box. Spec R1.0, design appendix R1.0 and guide V-11 updated; PCB regeneration in progress.

2026-10-25 15:50 [progress]

Completed task 20261024-2322 (Key Box 36 part-count reduction). Schematic regenerated (ERC 0); BOM down from 443 to 357 parts, every row with manufacturer and MPN. The routing flow left 6 unconnected nets (5 after refine); they were fixed by hand (TLE75008 VS pin, ADS7038 AIM6, TPS2H160 HS_SEL, VFET pour, DI29, LR6), giving DRC 0 unconnected and 0 errors with schematic parity. Board exports, enclosure renders, STEP files, README and datasheets updated.

2026-10-25 18:29 [decision]

Air Hub / Air Hub Pro I/O grouped by wall (task 20261025-0012): putting every connector in one wall was dropped because the core board has its USB pins on the bottom edge and RMII on the left edge, so a left-wall USB-C would cross the RMII fan-out. Implemented the approved fallback: left wall M8 + RJ45 only, front wall USB-C + PAIR side key + one RGB status LED (APFA3010 on core pins 72-74, replacing the two blue LEDs), RP-SMA in the rear wall. Board rerouted: DRC 0, EMC 22 errors (was 23), enclosure interference 0; +$0.26 per board. Reference board R1.18, specification R1.21.

2026-10-25 00:30 [decision]

Recorded the Air Hub Mini controller alternatives in the design appendix §3.1: ESP32-C5-WROOM-1 (dual-band Wi-Fi 6, CAN FD, mass production; a worthwhile upgrade pending the owner's decision) and ESP32-S31-WROOM-3-N16R16V (pre-release, 2.4 GHz only, not for the Mini). The ESP32-C6-WROOM-1-N8 stays the current choice.

2026-10-28 17:30 [progress]

Completed 20261028-1730-air-hub-mini-esp32-c5-board. The Air Hub Mini board is regenerated with the ESP32-C5-WROOM-1-N8R2, because no N8 order code exists. Results: DRC 0 and EMC 0 errors. Per-board parts cost $19.25 at 100 pcs, with the module estimated at $4.2. The Mini sections of the reference board page (R1.19) carry the new pin map, BOM row and cost ($16.7 electronics, $22.4–27.7 landed).

2026-10-28 18:00 [decision]

Completed 20261028-1709-air-hub-esp32-c5-module. Air Hub and Air Hub Pro move their Wi-Fi link to the ESP32-C5-WROOM-1-N4, and the Air Hub Mini controller is the ESP32-C5-WROOM-1-N8R2 (owner decision 2026-10-28). The Air Hub spec (R1.22), design appendix (R1.17), guide (R1.13), reference board carrier sections (R1.20), EMC evaluation, Switch line pages and governance files are updated. Cost estimates use distributor prices, since there is no LCSC listing: Air Hub $31.6–41.0, Air Hub Pro $41.2–46.7 (mostly within the ceiling), Air Hub Mini $22.4–27.7. New item AIR-O-16 covers:

• quotes;
• chip revision ≥ v0.2 for the SDIO slave;
• ESP-Hosted over SDIO on the RK3506;
• 5 GHz under EN 301 893 with DFS (5150–5350 MHz stays off until on-vessel use is confirmed);
• the carrier re-layout.

The carrier pin assignment is a documentation proposal. The Linux carrier schematic and PCB still use the C6.

2026-10-28 18:20 [decision]

Completed 20261028-1704-governance-sync-switch-rev-d. Governance files now match Air Hub rev D with the ESP32-C5, the Air module first build and Key Box 36 R1.0.

• Business plan zh/en v2.3: the §10 status note covers the Air Hub enclosure design and the C5 Wi-Fi, Key Box 36 R1.0 and the Air AN54LV-P15 module build. §11 costs: Air Hub $31.6–41.0, Air Hub Pro $41.2–46.7 (mostly within the ceiling), Air Hub Mini $22.4–27.7.
• Product plan v1.11: the Key Box 36 cost row reads spec R1.0, BOM not yet totalled; the Air row notes the module build.
• Compliance matrix v1.7: Key row covers Key Box 36 and its extra interfaces; Mate row is no longer labelled Hub; the withdrawn Air Hub LR row is moved out of the table into a note; remote-vessel row and quote list name Mate.
• Open questions v1.10: AIR-O-03 rewritten to the current state; AIR-O-09 marked closed 2026-09-29; CTL-O-01 and field-wiring item 2 name Mate.
• PPT build guide v1.2: product references to Hub now read Mate.
• Wireless SoC catalog: Air Hub row updated to the EFR32MG24 module and the ESP32-C5.

2026-10-28 21:15 [progress]

Air Hub Mini order code changed from ESP32-C5-WROOM-1-N8R2 to N8R8 at the owner's request. The two have the same footprint and pins, and the board is regenerated. Results: DRC 0; EMC 14 findings with 0 errors. Per-board parts cost $19.55 at 100 pcs (module estimated at $4.5). Reference board R1.21: $17.0 electronics, $22.7–28.0 landed. Task 20261028-1709 had already completed, so this task also changed N8R2 to N8R8 and 2 MB to 8 MB PSRAM in the Mini text of the spec (R1.23), the design appendix (R1.18), the guide (R1.14), the certification evaluation, product-plan, open-questions and the wireless SoC catalog.

2026-10-28 21:40 [progress]

Follow-up to 20261028-1709. The Linux carrier schematic has been revised for the ESP32-C5-WROOM-1-N4; ERC passes on both Air Hub variants. The reference board §2.3 now gives the as-drawn pins:

• SDIO on IO7–IO10, IO13 and IO14 to core-board pins 34–39, with the pull-ups listed;
• UART0 to UART4;
• EN on pin 122 and GPIO28 on pin 81;
• GPIO25 and MTDI pulled up for rising-edge SDIO.

The board will grow to 104 x 97 mm and the enclosure about 7 mm deeper; the PCB is not yet re-routed. Governance Mini cost follows the N8R8 change: $22.7–28.0.

2026-10-28 22:00 [progress]

Follow-up to 20261028-1709. The Air Hub / Pro carrier with the ESP32-C5-WROOM-1-N4 is re-routed and rendered.

• Board 104 x 97 mm; enclosure 112 x 104 x 27 mm with 0 interference.
• ERC and DRC have 0 errors. EMC: 60 findings, 22 errors (same set as before), 25 warnings, 13 info. SPICE: 22/22.
• Parts per board at 100 pcs: Pro about $48.6, Air Hub about $37.5.
• Peak +3V3 load is about 0.68 A, set by the C5 5 GHz TX at 403 mA.

Updated:

• reference board §3, §6, §7 and §7.3 (R1.23);
• guide §8 (R1.15);
• EMC evaluation;
• spec AIR-O-16 (R1.25).

2026-10-29 05:10 [decision]

Completed 20261029-0443-switch-key-box-and-panel-deferral. On the owner's instruction, Key Box 36 is now the first-release wired Key product (T0, price to be set) and is listed on the Switch index, line spec (R1.6), line brief, Key index and product overview. The Key 4 / Key 8 panels and both expansion units are not designed yet and are deferred. Their requirements stay in the Key spec (R1.1) as future design input, and the workspace base board is a placeholder. Also updated: Key guide (R1.0, quote covers only Key Box 36), Key design (R1.1), business plan zh/en v2.4 (Switch row), product plan v1.12 (Key section, cost row) and open questions v1.11.

2026-10-29 06:17 [decision]

Completed 20261029-0614-switch-product-priority-order. On the owner's instruction, the Switch products follow one order: Key Box 36 (T0), Air, Air Hub Mini, Air Hub Pro (T1). Air Hub Mini is the hub that launches with Air; Air Hub Pro follows and brings the local broker, Matter controller, P09 Control host and 433 MHz; the standard Air Hub (RK3506G) stays as a later option without a milestone (decisions 1a, 2a). Updated: product plan v1.13 (T1 row, Switch order, staffing, M13–14), business plan zh/en v2.5 (Switch row), Switch spec R1.8 (product table reordered), Switch brief and index, Air Hub spec R1.26 (§2.1 order) and Air Hub index.