AI Compliance for AI Teams — Explained With Real Examples and CLI Commands

Most AI compliance documentation assumes you already know what you need to prove, who you need to prove it to, and which regulations apply to your system.

This section doesn't assume that.

These pages explain the real problems, the real risks, and exactly what SpanForge does about each one — in language that works for engineers, CTOs, and compliance buyers.

Start in 30 seconds

pip install spanforge

# Scan your training data for PII
spanforge validate --dataset data.jsonl --pii-check

# Build and export an audit trail
spanforge audit export --format pdf --output audit.pdf

# Check your full compliance posture
spanforge compliance check --all

Not sure which command to run first? Use the routing guide below.

Start with the problem that's most urgent for you

"I think my training data might have PII in it"

→ How to detect PII in training data

You almost certainly have PII you don't know about. Most teams only find out during audits. This page shows you how to detect it, redact it, and prove you handled it correctly — before anyone asks.

"I need to show an auditor what my AI system did"

→ What is an AI audit trail?

Logs are not an audit trail. An audit trail is tamper-evident, cryptographically signed, and structured for regulator review. This page explains the difference and how to build one.

"We're dealing with EU AI Act requirements"

→ How to pass EU AI Act Article 10

High-risk AI obligations apply from August 2, 2026. Article 10 governs training data governance. This page breaks down exactly what's required, what auditors will ask for, and how to generate compliant evidence.

"I need to assess our overall AI compliance posture"

→ AI compliance checklist

A structured checklist across training data, audit trails, PII handling, compliance evidence, runtime governance, model documentation, and incident response — with SpanForge commands for each item.

"A customer asked about our 'compliance evidence' and I didn't know what to say"

→ What is a Compliance Evidence Chain?

A CEC is a single, cryptographically-signed document that links all your compliance artifacts — scan reports, audit logs, policy records — into a verifiable package you can hand to a regulator or enterprise buyer.

Why these pages exist

SpanForge's core docs are excellent for engineers who already know what they need.

These Learn pages exist for the moment before that — when a team is trying to figure out:

• What exactly does "AI compliance" mean for our system?
• Which regulations apply to us?
• What would a regulator actually ask for?
• Where do we start?

These are the most important questions. And they're usually the ones that don't have good answers online.

Regulations covered in this section

Next: Get running

Once you understand the problem, the quickstart gets you from install to signed audit trail in under 5 minutes.

→ Quickstart →
→ AI compliance checklist →