Release and Version Matrix

Use this page as the operator's compatibility record. The values here are those of the documented release; the values reported by your installed package are authoritative for your machine.

Documented release

Item	Documented value	How to read it on the installed machine
CLI version	`chargelink 0.5.0-rc2`	`chargelink --version`
JSON contract	`native-core-0.55`	`contract` field of any `--json` result
Integration API	`chargelink.integration.v1`, `api_version 1.8.0`	`chargelink --json integration capabilities` (embedded, no server needed)
gRPC server product version	`product_version 0.5.0-rc2`, `product ChargeLink Native` (one version for every component since 0.3.0)	`chargelink --json integration health --endpoint ...`
Binary	`pc1\bin\chargelink.exe` SHA-256 `74D121EA0938C50F2E0F093D6CF6EEE0BFC21E4D059CFDBEC726BBBBDB39162D`, reproducible build of commit `2cf6edb8`, Rust 1.97.1, dist profile	`Get-FileHash`; `manifest\reproducible-build.json`
Management API access	loopback only; bearer token in `<state-root>\api-token`, new at every start	`integration health` without a token fails with `CL-RUNTIME-001`
Canonical signals	94	`canonical_signal_count` in capabilities
Built-in profiles	64	`chargelink --json profile list`
Conformance packages	13	`chargelink --json conformance catalog`
Protocol-first inventories	ISO 15118-2: 797 bindings; ISO 15118-20: 383 bindings	`chargelink --json test protocols list`
Deterministic scenarios	10 ISO 15118-20, 12 legacy, 12 TLS campaigns	`sim iso20-catalog`, `sim legacy-catalog`, `sim tls-catalog`
Licensing contract	`chargelink-native-licensing-v1`, license schema `chargelink-native-license-v1`	`chargelink --json license status`
Runtime and artifact policies	`chargelink-native-runtime-lifecycle-policy-v1`, `chargelink-native-artifact-integrity-policy-v1`, `chargelink-native-redaction-policy-v1`	`runtime policy`, `artifacts policy`
Exit-code policy	`chargelink-native-exit-code-policy-v1`	`diagnostics exit-codes`
Package manifest schema	`chargelink-native-package-manifest-v1`	`PACKAGE_MANIFEST.json` in the package root
Documentation	this manual, generated from the help output of the same binary	footer of every page

The CLI version and the gRPC product version differ because they come from different components of the same build. Record both.

Reported claim boundaries. Integration: The integration API exposes ChargeLink engineering simulation and evidence functions. It does not itself establish accredited certification, standards-body approval, hardware validation, or vendor equivalence.

Test bindings: Execution bindings are engineering test definitions; PASS/FAIL requires live-SUT or validated replay evidence.

Conformance catalog: commercial protected package catalog only; not accredited certification or vendor-tool equivalence

Third-party compatibility

The NI VeriStand, plant-model and bench rows match the package's INSTALL-PC1.md.

Component	Validated with	Notes
Windows	Windows 11 Pro (build 26200) on the reference workstation; Windows 10/11 64-bit supported	`Get-ComputerInfo`
NI VeriStand	2024 Q4 (ClientAPI, Gateway, veristand-server); the package's `INSTALL-PC1.md` lists the expected file hashes	use this NI build; other NI VeriStand versions are not covered by this release
.NET	.NET Framework 4.8 (NI broker); .NET 10 runtime x64 (owner host; LTS until November 2028)	installed by the customer, never redistributed; tested with 10.0.10
C++ runtime	Microsoft Visual C++ 2015-2022 Redistributable x64	`chargelink.exe` imports `VCRUNTIME140.dll`
Plant model	FMI 2.0 Co-Simulation FMU (26 inputs / 18 outputs / 6 parameters) in `pc1\veristand\ChargeLink\Models` and the system definition `ChargeLink_Blank_Windows.nivssdf` in `pc1\veristand`	64 User Channels, 44 mappings; VeriStand loops placed on logical processors 10, 11 and 12 of the reference PC
TLS	rustls 0.23 with aws-lc-rs for ISO 15118-20 (TLS 1.3 only, named groups secp521r1 and x448, cipher suites TLS_AES_256_GCM_SHA384 and TLS_CHACHA20_POLY1305_SHA256); static OpenSSL 3.5.9 for the ISO 15118-2 TLS 1.2 roles and the x448 key agreement; Windows SChannel (TLS 1.2) for the ISO 15118-2 reference responder with an external EVCC	ISO 15118-20 Annex B certificate profile (ECDSA P-521, SHA-512); engineering material is generated per run and needs `--allow-engineering-tls-identity`. The ISO 15118-20 handshake offers and accepts only secp521r1 and x448; `--allow-legacy-tls-named-groups` adds secp256r1 for engineering interop
CAN adapters	Kvaser CANlib (`canlib32.dll`) for the IEC 61851-23/-24 System A lane, Kvaser Leaf v3	the adapter kinds of the scripted DC-CAN lanes (PEAK, Vector, Kvaser, SocketCAN, SLCAN, Lawicel, USBtin) are descriptors and open no hardware
OPC UA	OPC Foundation stack discovered at runtime; probe only	no endpoint opened

Protocol-to-profile check

Resolve profiles from the installed build, not from this page:

chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json profile list
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json profile show <PROFILE_ID>
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json evse external-evcc-session-policy     # the activation catalog with the exact commands per protocol

Acceptance of an installation should confirm the profiles you use, for example ISO 15118-20 DC (iso15118_20_dc), ISO 15118-20 AC and BPT, ISO 15118-2 DC and AC and DIN 70121 DC, as listed in the Profile Catalog.

Upgrade rule

When ChargeLink is upgraded, repeat at least: package hash verification; --version; license status; doctor --strict; profile list; gRPC health and session smoke; one golden run per protocol family used at the site, including the deterministic simulation hash comparison; the two Start-SeccSession.ps1 -ValidateOnly checks on the VeriStand bench when used; an artifact integrity check and a support-bundle export. Check commands copied into your own procedures against chargelink <command> --help of the new binary.