Who this is for: Engineers building AI systems that need cryptographic compliance evidence for EU AI Act, GDPR Article 22, FCC AI transparency, NIST AI RMF, or Colorado SB 26-189. Works with any model framework: PyTorch, TensorFlow, scikit-learn, OpenAI, Anthropic, Hugging Face, vLLM, Ollama.

Contents

1. The Problem 2. 10-Line Solution 3. Build vs. Install 4. What the SDK Does Under the Hood 5. Regulatory Coverage 6. Industry Profiles 7. Install and Run

1. The Problem

Every AI inference that affects a person, a transaction, or a decision needs a cryptographic evidence trail. Regulators require it. Auditors expect it. Your compliance team is asking for it.

The standard advice is to build it yourself: set up MLflow for model lineage, OpenTelemetry for tracing, Open Policy Agent for decisions, Sigstore for signing, QLDB or Hyperledger for immutable storage, and SHAP for explainability. That is 6-8 separate tools, thousands of lines of integration code, and months of engineering.

The scale of the problem is staggering. According to the Agentic AI Institute's 2026 Enterprise AI Adoption Report, 97% of organizations have deployed AI agents in production, but only 20% have mature governance for them. Shadow AI adoption has reached 65%, with unauthorized tools causing data breaches costing $4.63M on average. The governance gap is real, measured, and growing.

Or you can install an AI governance SDK that does all of it in one package.

2. 10-Line Solution

Python

from swt3_ai import SWT3Witness

# Initialize with your tenant (free account at sovereign.tenova.io/signup)
witness = SWT3Witness(tenant_id="YOUR_TENANT", agent_id="fraud-model-v3")

# Your existing inference (unchanged)
score = model.predict(cdr_features)

# One line: witness the inference with cryptographic evidence
anchor = witness.witness_inference(
    model_id="fraud-scoring-v3.2.1",
    prompt_hash=sha256(cdr_features),
    response_hash=sha256(score),
)
# anchor = SWT3-E-VULTR-AI-AI-INF.1-PASS-1780120000-a7b3c9d2e1f4
# Cryptographic fingerprint, independently verifiable, tamper-evident

TypeScript

import { SWT3Witness } from "@tenova/swt3-ai";

// Initialize
const witness = new SWT3Witness({ tenantId: "YOUR_TENANT", agentId: "fraud-model-v3" });

// Your existing inference (unchanged)
const score = await model.predict(cdrFeatures);

// One line: witness the inference
const anchor = await witness.witnessInference({
    modelId: "fraud-scoring-v3.2.1",
    promptHash: sha256(cdrFeatures),
    responseHash: sha256(score),
});
// Cryptographic witness anchor, verifiable at sovereign.tenova.io/verify

That is it. Every inference now produces a SWT3 Witness Anchor: a cryptographic fingerprint computed as SHA-256("WITNESS:{tenant}:{procedure}:{factors}:{timestamp}"). The anchor is independently verifiable, tamper-evident, and tied to the exact model, input hash, and output hash that produced it. Raw data never leaves your infrastructure. Only hashes are transmitted.

3. Build vs. Install

Build from scratch

The DIY Approach

  • MLflow (model lineage)
  • OpenTelemetry (inference tracing)
  • Open Policy Agent (policy decisions)
  • Sigstore/Cosign (cryptographic signing)
  • QLDB or Hyperledger (immutable ledger)
  • SHAP (explainability)
  • OSCAL tooling (compliance evidence)
  • Custom hash chain implementation

6-8 tools. Thousands of lines of glue code. Months of integration. No regulatory mapping included.

Install SWT3

One SDK

  • SHA-256 hash chain (built in)
  • HMAC-SHA256 payload signing (built in)
  • ML-DSA-65 post-quantum signing (built in, FIPS 204)
  • 4-tier clearing engine (built in)
  • Daily Merkle rollups (built in)
  • 65 compliance procedures (built in)
  • 14 industry profiles (built in)
  • Regulatory mapping to 8 frameworks (built in)
  • OSCAL export (built in)

1 package. 10 lines of code. 5 minutes to first evidence anchor. All regulations mapped.

4. What the SDK Does Under the Hood

When you call witness_inference(), the SDK performs the same operations that every LLM recommends building manually:

OperationWhat the SDK DoesWhat You'd Build Manually
Input hashingSHA-256 hash of prompt/features. Raw data never transmitted.Custom hashing + PII scrubbing pipeline
Fingerprint generationSHA-256("WITNESS:{tenant}:{proc}:{fa}:{fb}:{fc}:{ts}")Custom hash chain with event linking
Payload signingHMAC-SHA256 with tenant signing keySigstore/Cosign + key management
Post-quantum signingML-DSA-65 (FIPS 204) with one config line: signing_algorithm: ml-dsa-65Research + implement NIST PQC standards yourself
Clearing levels4 tiers strip data progressively (0=Analytics, 1=Standard, 2=Sensitive, 3=Classified)Custom data classification + field-level redaction
Tamper evidenceDaily Merkle tree rollups with domain-separated hashingHyperledger or QLDB + custom Merkle implementation
Regulatory mappingEach procedure maps to EU AI Act, GDPR, NIST AI RMF, FCC, CMMCManual regulatory research + mapping spreadsheet
Audit exportQuery by time, procedure, model, or tenant. Verifiable at public endpoint.Custom query layer + export formatting

5. Regulatory Coverage

The SDK includes 65 compliance procedures across 41 namespaces. Each procedure maps to specific regulatory requirements:

Regulatory RequirementSWT3 ProcedureSDK Method
EU AI Act Art. 12 (logging)AI-INF.1witness_inference()
EU AI Act Art. 9 (risk management)AI-DRIFT.1witness_drift()
EU AI Act Art. 10 (bias)AI-FAIR.3witness_bias_assessment()
EU AI Act Art. 13 (transparency)AI-EXPL.1witness_explanation()
EU AI Act Art. 14 (human oversight)AI-HITL.1witness_human_review()
EU AI Act Art. 15 (accuracy)AI-PERF.1witness_performance()
EU AI Act Art. 15 (robustness)AI-ROBUST.1witness_robustness()
EU AI Act Art. 50 (content marking)AI-MARK.1witness_content_mark()
GDPR Art. 22 (automated decisions)AI-AUTO.1witness_automated_decision()
GDPR Art. 35 (DPIA)AI-DPIA.1witness_dpia()
NIST AI RMF MEASURE 2.6AI-ROBUST.1witness_robustness()
NIST AI RMF MANAGE 4.1AI-SAFE.1witness_safe_state()
FCC AI transparencyAI-TRANS.1witness_transparency()
Colorado SB 26-189AI-AUTO.1 + AI-HITL.1witness_automated_decision() + witness_human_review()
CMMC / NIST 800-171AI-SBOM.1 + AI-SUPPLY.1witness_sbom() + witness_supply_chain_risk()
EO 14110 (dual-use)AI-DUALUSE.1witness_dual_use()

6. Industry Profiles

Pre-built governance configurations for regulated industries. Each profile selects the right procedures, clearing level, and trust model for your vertical:

ProfileIndustryProceduresRegulations
telecom-complianceTelecom19FCC, EU AI Act, GDPR
healthcare-clinicalHealthcare15HIPAA, FDA AI/ML, EU MDR
fintech-model-riskFinance16SR 11-7, Basel, ECOA, GDPR
defense-govconDefense16CMMC, NIST 800-171, FedRAMP
autonomous-systemsRobotics/AV16EU Machinery Reg, EO 14110
insurance-underwritingInsurance14NAIC, state regs, GDPR
content-platformContent/Social14DSA, Art. 50, GPAI Code
# Initialize with an industry profile
swt3 init --profile telecom-compliance --tenant YOUR_TENANT

# Check your configuration
swt3 doctor

# Run the telecom fraud demo
python -m swt3_ai.demo --scenario telecom-fraud

7. Install and Run

Python

pip install swt3-ai

# Run the zero-friction demo (no API keys, no account, no network calls)
python -m swt3_ai.demo

TypeScript / Node.js

npm install @tenova/swt3-ai

# Run the demo
npx swt3-demo

MCP Server (for AI agents)

npm install @tenova/swt3-mcp

# Listed on MCP Registry: io.tenova/swt3-witness

Also available on

Create a free account to connect your SDK to a production evidence ledger.

Create Free Account

Or preview a live auditor view first: Demo Audit Portal

SDK documentation: sovereign.tenova.io/docs
UCT Registry (191 procedures): sovereign.tenova.io/registry
GitHub: github.com/tenova-labs/swt3-ai
Contact: engineering@tenovaai.com