Standards, protocols, and conformance position
==============================================

ChargeLink does **not** treat all protocols as one undifferentiated standards claim. The snapshot separates standards families, conformance-style packages, interoperability packages, HIL packages, and evidence add-ons.

Supported protocol families in the snapshot
-------------------------------------------
.. list-table::
   :header-rows: 1
   :widths: 20 45 35

   * - Family
     - Current snapshot position
     - What remains open
   * - ISO 15118-2 AC
     - Preserved AC EIM baseline; packaged conformance and interoperability coverage; protocol gate green.
     - Broader vendor proof and launch hardening.
   * - ISO 15118-2 DC
     - EIM and PnC baselines, realistic electrical behavior, TLS, EXI, identity binding, MeteringReceipt surfaces, packaged coverage, protocol gate green.
     - Natural cross-vendor MeteringReceipt, EMAID cleanup, broader vendor proof.
   * - DIN 70121 DC
     - Repeated live proof through SessionStop, negative matrix, conformance/interoperability packs, protocol gate green.
     - Close vendor-adapter gates and broaden partner or hardware proof.
   * - ISO 15118-20 AC
     - Live realistic EIM flows through SessionStop over TLS and native EXI, packaged interoperability and negative coverage, protocol gate green.
     - Broader vendor proof and future formal AC conformance.
   * - ISO 15118-20 DC
     - Live PnC/BPT baseline through SessionStop over native EXI and TLS, MeteringConfirmation qualification coverage, packaged conformance/interoperability families.
     - Broader vendor proof and deeper certificate scope.
   * - MCS
     - Live EVSE MCS path on shared ISO 15118-20 runtime binding, hardware profiles, bench controller, conformance/interoperability partial packs, EVCC differential matrices.
     - Claim-safe semantics, repeated physical-bench proof, broader vendor evidence, and promotion from partial to full.

How to read the package catalog
-------------------------------
- ``CL-CONF-*`` packages are conformance-oriented families aligned to the relevant standard generation.
- ``CL-INT-*`` packages are interoperability-oriented families that prove multi-vendor or multi-profile behavior.
- ``CL-HIL-*`` packages are hardware or bench proof surfaces.
- ``CL-EVIDENCE-PRO`` and ``CL-VENDOR-ADAPTERS`` add reporting or adapter capability on top of the shared runtime.

Important claim boundary
------------------------
.. warning::

   The snapshot makes a clear distinction between strong CCS protocol baselines and **claim-safe production launch**. MCS remains partially gated, and the commercial core still carries explicit cleanup requirements around first-party message models and EXI replacement.