9 destinations

CAN Isolated Changelog

Dated documentation and validation changes for the unreleased CAN Isolated pilot, kept separate from future hardware and firmware releases.

A dated record of CAN Isolated documentation and validation changes. Documentation versions do not imply a manufactured hardware revision or released firmware.

2026-08-27 · documentation v0.2

  • added the documentation hub, controlled-bench Quick Start, compatibility matrix, firmware/download status and this changelog;
  • marked every host path pending until traceable DVT evidence exists;
  • made the absence of firmware binaries, USB identity and recovery images explicit;
  • linked the public eight-gate validation ledger and vendor-neutral buyer guides;
  • kept public checkout closed and retained the distinction between targets and claims.

2026-08-27 · validation record v0.1

  • published an eight-gate release ledger for supplier identity, traceability, isolation, compatibility, capture integrity, shipping, pilot reliability and commerce;
  • recorded four official supplier contact routes and two Taobao marketplace leads as screening evidence only;
  • recorded that no usable quotation, approved supplier, sample or completed release gate exists.

2026-08-26 · planning baseline v0.1

  • defined the first pilot target as an isolated USB-C Classical CAN interface with a local analysis workflow;
  • set public sales behind product, supplier, payment, legal, shipping and support evidence gates;
  • identified target Windows, Linux and macOS paths without claiming tested compatibility;
  • defined public documentation for Quick Start, Compatibility, Firmware, Changelog, open-source notices, safety and troubleshooting.

Fields required for a future product release

Hardware Commercial product name, hardware revision, supplier and batch traceability.
Firmware Version, source tag, binary hash, build method, licences and recovery path.
Compatibility Named host, driver/backend, application, bitrate cases, evidence identifiers and known limits.
Documentation Document version, effective date, safety boundary, superseded pages and migration notes.
Commerce Legal operator, final package, price, stock, dispatch route, policies and payment/refund evidence.

What this log will not hide

Failed tests, narrowed claims, withdrawn firmware, supplier changes and incompatible revisions will be recorded with their effect on buyers. A later date or higher version number does not turn an unverified target into evidence.

Read status before version

Use the validation ledger for gate state and the firmware page for downloadable artifacts. This changelog records change; it does not certify a release.