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 Gateway 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 Gateway 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 Gateway 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 Gateway 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 Gateway 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 Gateway) 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 Gateway, 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 Gateway, 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 Gateway, 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 Gateway 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 Gateway, 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 Gateway (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 Gateway, 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 Gateway (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 Gateway, 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-gateway/, 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.