Product status and claim boundaries

ChargeLink release and qualification flow

This site is intentionally honest about the current product position. It shows both what an operator can run today and what product management should still treat as gated.

Current strengths

  • The current CCS families are treated as protocol-qualified in the SRS: ISO 15118-2 AC, ISO 15118-2 DC, DIN 70121 DC, ISO 15118-20 AC, and ISO 15118-20 DC.

  • Package registry, standards matrices, per-case traceability, evidence export, suite orchestration, and release-candidate packaging are all first-class product surfaces in the snapshot.

  • The repo already contains a real MCS workstream: EVSE runtime, bench/HIL controller, hardware profiles, qualification packs, and EVCC differential matrices.

Still gated

  • Vendor gates for Josev, EVerest, and hardware EVCC proof are still treated as open for claim-safe production launch.

  • MCS remains in a partial or qualification-ready posture until repeated real-bench evidence and broader vendor proof are attached.

  • Commercial-core cleanup is still tracked through first-party message-model and EXI replacement milestones.

How the docs handle this

  • The guides show how to run the commands that exist today.

  • The package, suite, and standards pages show where the snapshot already has strong operator value.

  • The release, evidence, and audit pages show the specific commands that remain central to commercialization and claim-safe proof.