CertifiedData.io
AI Compliance · Audit Trails

AI Compliance Logging

Compliance logging for AI systems means producing cryptographically verifiable records of what data was used, what decisions were made, and who certified the artifacts — before an auditor asks. This page explains the compliance logging architecture required by major AI governance frameworks.

Two Layers of AI Compliance Logging

Layer 1 — Training Data Logging

Compliance logs must capture the provenance of every training dataset: its origin, generation method, fingerprint, and certification status. For synthetic datasets, a cryptographic certificate serves as the primary training data log record. It binds the exact dataset bytes (via SHA-256 hash) to a timestamped, Ed25519-signed artifact that can be verified by any third party.

Layer 2 — Decision Logging

Beyond training data, AI compliance logging must capture operational decisions — how the AI system used certified artifacts, what outputs it produced, and the reasoning chain linking inputs to outputs. Decision lineage records provide the operational audit trail that complements dataset certification.

Regulatory Framework Mapping

EU AI Act Art. 12
Automatic logging of high-risk AI system events
Transparency log + certificate issuance records
EU AI Act Art. 19
10-year retention of training data documentation
Immutable certificate store with SHA-256 fingerprints
NIST AI RMF Govern 1.7
Documented AI lifecycle governance policies
Certification artifacts as policy evidence
ISO 42001 §8.4
Training data quality management records
Certified synthetic datasets with provenance records
GDPR Art. 30
Records of processing activities
Synthetic data certificates proving no real-world records used

What a Compliance Log Entry Must Include

{
  "certification_id": "uuid",
  "timestamp": "2026-03-19T00:00:00Z",
  "issuer": "Certified Data LLC",
  "dataset_hash": "sha256:a7f3...",
  "algorithm": "CTGAN",
  "rows": 100000,
  "columns": 25,
  "schema_version": "certifieddata.cert.v1",
  "signature": "ed25519:base64url...",
  "verify_url": "https://certifieddata.io/verify/uuid"
}

Each CertifiedData certification artifact serves as a compliance log entry. The dataset_hash is the fingerprint regulators will request. The signature is independently verifiable using the public key at /.well-known/signing-keys.json.

Decision Lineage Logging

AI compliance logging extends beyond datasets to operational decisions. CertifiedData's decision lineage layer records how certified artifacts were used by AI systems — linking training data certificates to model outputs via a tamper-evident, Ed25519-signed public decision log.

Decision records include the actor (agent or system), the decision label, the confidence score, and a reference to the certificate ID of the certified dataset that informed the decision. This creates an unbroken chain from raw training data to deployed AI output.