Skip to main content

Export Evidence in EU AI Act, AEPD, and ENS Formats

An evidence export is a file of decision events for a date range. Verdictan can also give the export in the structure of a compliance report. This article lists the report formats and the checks that you must do. Export Evidence for a Review gives the full procedure.

A compliance report organizes evidence for a review. It does not prove compliance, and it does not replace a review of your application and controls.

Select the format​

Console formatCLI valueFile contents
EU AI Act (AESIA)compliance-aesiaA JSON report in the AESIA structure
AEPDcompliance-aepdA JSON report in the AEPD assessment structure
ENScompliance-ensA JSON report in the ENS structure
All compliancecompliance-allA .tar.gz bundle with the reports and manifest.json

The same export also has the csv and json formats for decision event rows.

Request the export​

You must have exports:read and exports:write. In the Console, open Trail → Evidence exports. Set the dates, select the format, and select Request export job.

You can also use the CLI:

verdictan export-jobs create \
  --start-date 2026-09-01 \
  --end-date 2026-09-02 \
  --format compliance-all --wait --json

The export uses only the dates and the format. Filters from the Trail list, History, or Inbox do not apply. Both dates are included.

Verify the file​

Read the completed job:

verdictan export-jobs get --job-id JOB_ID --json

Calculate the SHA-256 of your file. Then compare it with the integrity.artifact_sha256 value of the job. Do not compare it with manifest_sha256. For an All compliance bundle, also compare the archive with the inventory from GET /v1/exports/jobs/{job_id}/manifest.

A matching digest proves that your file is the recorded artifact. It does not prove that you selected the correct dates or organization.

Know what the export contains​

These exports contain decision events only. Administrative changes come from Trail export. History content and Inbox decisions are separate records.

The file contains operational metadata. Keep it only in a location that you are permitted to use.

Next steps​