Data and artifacts reference

ChargeLink uses files as a primary truth surface. The files below are the first places an operator should look when reconstructing what happened during a run.

File	Primary purpose
summary.json	Run-level status summary.
session.json	Session identity and selected protocol.
protocol_summary.json	Condensed protocol behavior summary.
protocol_report.json	Detailed standards or behavior report.
protocol_session.json	Protocol session payload.
message_trace.json	Readable message trace.
trace.jsonl	Structured streaming trace.
frames.jsonl	Transport frame capture.
events.jsonl	Runtime event stream.
conformance_traceability.json	Case-to-artifact mapping for packaged execution.
diagnostics.json	Additional runtime diagnostics.
live_runtime_status.json	Current runtime status snapshot for long-lived runs.

Typical artifact roots

• artifacts/evse_runtime for live EVSE sessions.

• artifacts/evcc_runtime for EVCC sessions and backend traces.

• artifacts/evcc_campaign_runs for campaign execution.

• artifacts/protocol_qualification for qualification bundles.

• artifacts/suites for named suite outputs.

• artifacts/audit for commercialization and SBOM outputs.