ChargeLink Documentation Logo

Overview

  • What ChargeLink is
  • Simulator roles: EVSE, EVCC, and bench-linked execution
  • Standards, protocols, and conformance position
  • Product status and claim boundaries

Getting started

  • Installation and workstation preparation
  • Quickstart: first EVSE session, first campaign, first report

Guides

  • Guide: EVSE operations
  • Guide: EVCC operations and backend orchestration
  • Guide: scenarios, campaigns, packages, qualification, and suites
  • Guide: trace, replay, diagnostics, reporting, and artifacts
  • Guide: MCS, HIL, and bench proof
  • Guide: UI and API surfaces

Reference

  • Data and artifacts reference
  • Profile catalog
  • Hardware profile reference
  • Package and suite catalog
  • API reference overview
  • chargelink-monitor
  • CLI reference
    • chargelink evse
    • chargelink evcc
    • chargelink hil
    • chargelink scenario
    • chargelink campaign
    • chargelink qualification
    • chargelink suite
    • chargelink report
    • chargelink trace
    • chargelink replay
    • chargelink lab
    • chargelink beckhoff
    • chargelink protocol
    • chargelink artifacts
    • chargelink sequence
    • chargelink macro
    • chargelink verdict
    • chargelink step
    • chargelink profile
    • chargelink template
    • chargelink library
    • chargelink batch
    • chargelink campaign-stress
    • chargelink service
    • chargelink requirements
    • chargelink backend
    • chargelink evidence
      • Reference syntax
      • Subcommands
      • map
        • CLI help
        • Production examples
      • validate
        • CLI help
        • Production examples
      • attest
        • CLI help
        • Production examples
      • sign
        • CLI help
        • Production examples
      • import
        • CLI help
        • Production examples
      • list
        • CLI help
        • Production examples
      • export
        • CLI help
        • Production examples
    • chargelink audit
    • chargelink ports
    • chargelink env
    • chargelink capture
    • chargelink ci
    • chargelink sessions
    • chargelink fault
    • chargelink network
    • chargelink fuzz
  • Glossary
ChargeLink Documentation
  • CLI reference
  • chargelink evidence
  • View page source

chargelink evidence

Map evidence, validate manifests, attest, sign, import, list, and export MCS or release evidence bundles.

Reference syntax

usage: chargelink evidence [-h]
                           {map,validate,attest,sign,import,list,export} ...

positional arguments:
  {map,validate,attest,sign,import,list,export}

options:
  -h, --help            show this help message and exit

Subcommands

Subcommand

Purpose

map

Map evidence-relevant artifacts from a run directory.

validate

Validate an evidence manifest.

attest

Create or update the attestation fields of an evidence manifest.

sign

Apply an evidence signature record.

import

Import an evidence manifest into a suite or release gate.

list

List imported evidence for a suite root.

export

Export imported evidence as a ZIP bundle.

map

Map evidence-relevant artifacts from a run directory.

CLI help

usage: chargelink evidence map [-h] path

positional arguments:
  path

options:
  -h, --help  show this help message and exit

Production examples

Generate a map from a production input.

chargelink evidence map 'artifacts/evcc_campaign_runs/cl_int_iso20_ac_negative_realistic'

Generate a second map.

chargelink evidence map 'artifacts/evcc_campaign_runs/cl_conf_iso2_dc_pnc_seed'

validate

Validate an evidence manifest.

CLI help

usage: chargelink evidence validate [-h] [--require-signature]
                                    [--require-artifacts-exist]
                                    [--no-attestation] [--allow-simulated]
                                    [--output OUTPUT]
                                    path

positional arguments:
  path

options:
  -h, --help            show this help message and exit
  --require-signature
  --require-artifacts-exist
  --no-attestation
  --allow-simulated
  --output OUTPUT

Production examples

Validate a baseline evidence manifest.

chargelink evidence validate 'validations/bench_proof/mcs_release_baseline.json' --require-signature --output 'artifacts/evidence/baseline_validate.json'

Validate the safety evidence manifest and require raw artifacts.

chargelink evidence validate 'validations/bench_proof/mcs_release_safety.json' --require-signature --require-artifacts-exist --output 'artifacts/evidence/safety_validate.json'

attest

Create or update the attestation fields of an evidence manifest.

CLI help

usage: chargelink evidence attest [-h] --reviewer REVIEWER [--status STATUS]
                                  [--notes NOTES] [--safe-stop-observed]
                                  [--fault-code FAULT_CODE]
                                  [--case-id CASE_ID] [--artifact ARTIFACT]
                                  [--output OUTPUT]
                                  path

positional arguments:
  path

options:
  -h, --help            show this help message and exit
  --reviewer REVIEWER
  --status STATUS
  --notes NOTES
  --safe-stop-observed
  --fault-code FAULT_CODE
  --case-id CASE_ID
  --artifact ARTIFACT   Relative or absolute raw evidence artifact path to add
                        to proof_bundle.artifacts.
  --output OUTPUT

Production examples

Attest a baseline MCS release proof manifest.

chargelink evidence attest 'validations/bench_proof/mcs_release_baseline.template.json' --reviewer 'qa' --status 'passed' --case-id 'mcs_dc_josev_session_contract' --artifact 'mcs_release_baseline_trace.json' --output 'validations/bench_proof/mcs_release_baseline.json'

Attest a safety manifest with safe-stop evidence.

chargelink evidence attest 'validations/bench_proof/mcs_release_safety.template.json' --reviewer 'qa' --status 'passed' --safe-stop-observed --fault-code 'hv_interlock_open' --fault-code 'over_current' --artifact 'mcs_release_safety_trace.json' --output 'validations/bench_proof/mcs_release_safety.json'

sign

Apply an evidence signature record.

CLI help

usage: chargelink evidence sign [-h] --signer SIGNER [--note NOTE]
                                [--output OUTPUT]
                                path

positional arguments:
  path

options:
  -h, --help       show this help message and exit
  --signer SIGNER
  --note NOTE
  --output OUTPUT

Production examples

Apply a signature record to the baseline manifest.

chargelink evidence sign 'validations/bench_proof/mcs_release_baseline.json' --signer 'qa' --output 'validations/bench_proof/mcs_release_baseline.json'

Apply a signature record to the safety manifest.

chargelink evidence sign 'validations/bench_proof/mcs_release_safety.json' --signer 'qa' --note 'verified on bench A' --output 'validations/bench_proof/mcs_release_safety.json'

import

Import an evidence manifest into a suite or release gate.

CLI help

usage: chargelink evidence import [-h] --suite-root SUITE_ROOT
                                  [--install-to-release-gate]
                                  [--install-root INSTALL_ROOT]
                                  [--allow-unsigned]
                                  [--require-artifacts-exist]
                                  path

positional arguments:
  path

options:
  -h, --help            show this help message and exit
  --suite-root SUITE_ROOT
  --install-to-release-gate
  --install-root INSTALL_ROOT
  --allow-unsigned
  --require-artifacts-exist

Production examples

Import a baseline manifest into the production release suite root.

chargelink evidence import 'validations/bench_proof/mcs_release_baseline.json' --suite-root 'artifacts/suites/chargelink-production-release' --install-to-release-gate --install-root 'validations/bench_proof' --require-artifacts-exist

Import a safety manifest into the production release suite root.

chargelink evidence import 'validations/bench_proof/mcs_release_safety.json' --suite-root 'artifacts/suites/chargelink-production-release' --install-to-release-gate --install-root 'validations/bench_proof' --require-artifacts-exist

list

List imported evidence for a suite root.

CLI help

usage: chargelink evidence list [-h] --suite-root SUITE_ROOT [--output OUTPUT]

options:
  -h, --help            show this help message and exit
  --suite-root SUITE_ROOT
  --output OUTPUT

Production examples

List imported evidence for the production release suite.

chargelink evidence list --suite-root 'artifacts/suites/chargelink-production-release' --output 'artifacts/evidence/evidence_list.json'

List imported evidence for a dedicated MCS qualification suite.

chargelink evidence list --suite-root 'artifacts/suites/chargelink-mcs' --output 'artifacts/evidence/mcs_evidence_list.json'

export

Export imported evidence as a ZIP bundle.

CLI help

usage: chargelink evidence export [-h] --suite-root SUITE_ROOT --output OUTPUT

options:
  -h, --help            show this help message and exit
  --suite-root SUITE_ROOT
  --output OUTPUT

Production examples

Export imported evidence from the production release suite.

chargelink evidence export --suite-root 'artifacts/suites/chargelink-production-release' --output 'artifacts/evidence/production_release_evidence.zip'

Export imported evidence from the MCS suite.

chargelink evidence export --suite-root 'artifacts/suites/chargelink-mcs' --output 'artifacts/evidence/mcs_evidence.zip'
Previous Next

© Copyright 2026, devLink AB.

Built with Sphinx using a theme provided by Read the Docs.