GPAI transparency obligations enforceable August 2026. CMMC Level 2 assessments mandatory November 2026. High-risk AI enforcement Dec 2, 2027 (Omnibus). Embedded AI Aug 2, 2028.
AI Evidence Clearing House

Your AI did something.
Prove it.

The evidence clearing house for AI compliance.
Record what your AI systems do. Prove it to any auditor. Verify it anywhere.

Your models make decisions. Your agents execute tools. Your orchestrators route data across jurisdictions. The Sovereign Witness Traceability protocol (SWT3) creates a tamper-evident record of every action -- anchored with SHA-256, mapped to 31 regulatory frameworks, and verifiable by any auditor without contacting you. Three promises: anchors never drop, the portal always loads, verification always resolves.

$pip install swt3-ai $npm install @tenova/swt3-ai $cargo add swt3-ai $dotnet add package swt3-ai $gem install swt3-ai
7 package registries
35,000+ SDK downloads
31 regulatory frameworks
Apache 2.0 protocol, patent pending
Trust Mesh Protocol

Your AI systems refuse to work with unverified partners. Automatically.

Three teams. Three jurisdictions. Three different regulatory requirements. Today, trust between AI systems is fragmented -- manual verification, incompatible audit formats, and no way to prove compliance across borders. Trust Mesh replaces that: every system proves its compliance posture before data flows.

Agent
Model
Orchestrator
Hong Kong
San Francisco
Brussels
SWT3 Protocol Layer
1 Brussels requires EU AI Act Article 12 logging. San Francisco requires NIST 800-53 AU-2 audit evidence. Hong Kong requires local AI governance attestation. Each system declares its own requirements. One protocol satisfies all three.
2 Before any data flows, each system presents a cryptographic credential proving its compliance posture: what it has witnessed, what clearing level it operates at, and what jurisdiction it serves. Every other system evaluates that credential against its own policy.
3 If trust is sufficient, data flows. Every exchange is recorded with jurisdiction (HK, US-CA, BE) and legal basis embedded in each witness anchor. All three regulators can independently verify without contacting each other.
4 If any system fails verification, the exchange is blocked. No data crosses the boundary. The blocked attempt is recorded as evidence. No human approval loop. No manual review. The protocol enforces what policy requires.

There is no server in the middle. Verification happens locally, with cryptographic proof that survives any audit. SWT3 is an open protocol with Apache-licensed SDKs in 7 languages. Anyone can implement it. No vendor dependency. Every partner that connects speaks the same protocol. That is the network effect.

How It Works

Four phases. No agents installed. No data retained. No central authority.

01

Witness

The SDK observes your AI inference at the point of execution. Evidence factors are captured and SHA-256 hashed locally. Raw prompts and responses never leave your infrastructure.

02

Anchor

Factors are sealed into an SWT3 Witness Anchor -- a tamper-evident receipt binding evidence to a verdict at a specific moment in time. The fingerprint formula is locked and identical across 7 languages.

03

Verify

Any party can independently verify the anchor using the open-source library or a browser. No API keys. No vendor access. SHA-256 runs locally. Just math.

04

Enforce

Policy-as-code rules declared in .swt3.yaml are evaluated at every tool call. Violations are recorded with full forensic context. The witness captures what happened and whether it matched policy.

103
AI Procedures
28
Frameworks
7
Registries
21
Integrations
2,125
Tests

What We Build

Open protocol. Commercial platform. From solo developers to sovereign enclaves.

Open Protocol

SWT3 AI Witness SDK

The evidence layer for AI systems. Cryptographic attestation for every inference. Trust Mesh for agent-to-agent verification. Policy-as-code governance for tool execution. 106 AI procedures mapped to EU AI Act, NIST AI RMF, CMMC, SR 11-7, and 27 more frameworks. Zero data retention. Three lines of code. SDKs in 7 languages. 21 integrations including OpenAI, Anthropic, Bedrock, LiteLLM, Ollama, vLLM, Cohere, Qdrant, LangChain, LangGraph, Google ADK, CrewAI, Microsoft AGT, and MCP.

Protocol Specification →
Evidence Clearing House

Axiom Sovereign Engine

The managed platform for AI compliance evidence. Your SDK sends anchors. We store them. Your auditor verifies them. Read-only auditor portal with finding register, completeness scoring, and decision chain visualization. Framework-mapped evidence views for EU AI Act, NIST, CMMC, IMDA, and 24 more. Bring your own infrastructure scans via evidence ingestion. Cloud, on-prem, or air-gapped.

Explore the Dashboard →
Kubernetes

K8s Hardware Attestation

Every machine running your AI has a hardware fingerprint -- GPU model, CPU architecture, runtime environment. If a workload migrates to different silicon, a GPU fails silently, or your cloud provider live-migrates a node, your compliance posture just changed and nobody recorded it. The SWT3 Witness DaemonSet runs on every node in your cluster and creates a tamper-evident record of the hardware actually executing your models. One install command. Zero code changes. Works across AWS, GCP, Azure, and on-prem.

helm install swt3 oci://ghcr.io/tenova-labs/charts/swt3-witness --version 0.5.8
DaemonSet Documentation →
MCP Server

AI Tool Compliance via Model Context Protocol

AI assistants call external tools -- APIs, databases, code interpreters, file systems. Every tool call is a decision with compliance implications: what data was accessed, which model made the call, and whether policy allowed it. The SWT3 MCP server sits between your AI assistant and its tools, witnessing every call without changing how your tools work. 18 compliance tools and 2 audit resources. Works with Claude Desktop, Cursor, Windsurf, and any MCP-compatible client.

npx @tenova/swt3-mcp
MCP Compliance Guide →

The Clearing Engine

Cross-border trust requires cross-border privacy. The clearing engine strips sensitive content before it leaves your jurisdiction. The proof survives. The data doesn't.

L0

Analytics

Full context: hashes, factors, model ID, provider, guardrails. For internal R&D and pre-deployment testing.

L1

Standard

Default. Hashes and factors only. No raw prompts or responses cross the wire. Production-grade privacy.

L2

Sensitive

Hashes, factors, model ID only. No provider metadata. Built for healthcare, legal, and PII workloads.

L3

Classified

Numeric factors only. Model ID hashed. Zero metadata. Built for defense, sovereign cloud, and air-gapped environments.

Regulatory Coverage

Native mapping to the frameworks that matter. Not a crosswalk bolted on after the fact.

EU AI Act NIST AI RMF NIST 800-53 CMMC v2.0 FedRAMP DoD RMF NIST 800-171 SR 11-7 HIPAA / 21 CFR GPAI Code of Practice IMDA Agentic AI Japan AI Promotion Korea AI Basic Act Colorado SB 26-189 Singapore IMDA ISO 26262 DO-178C FDA 21 CFR Part 11 ASL-4 (Anthropic RSP)

Give Your Auditor Their Own Portal

Read-only, time-limited, cryptographically verified. The auditor sees exactly what they need and nothing they should not.

Finding Register

Auditors annotate findings with severity classification (Major / Minor / Observation) per EU AI Act Article 43. Every finding is linked to SWT3 anchors.

Agent Subway Map

Multi-agent decision chains with cryptographic proof at every node. Swimlane visualization showing human, orchestrator, and worker interactions. Policy violations flagged inline.

Conformity Report

One-click Annex V conformity report. Pulls findings, checklist status, and corrective actions into a print-ready document with its own SWT3 anchor.

See Live Auditor Portal →

Proxies monitor traffic. We witness execution.

AI Governance Proxies

Sit between your app and the model. Can be bypassed. Cannot see inside private enclaves. Store prompts and responses on their servers. Single point of failure. Cannot operate cross-border without a central server.

SWT3 Protocol (SDK-Level)

Embedded in your execution logic. Cannot be bypassed. Works inside private enclaves, air-gapped networks, and sovereign clouds. Stores only cryptographic proofs. Agents verify each other directly. No central server. No borders.

Implementation Paths

Start with the protocol. Scale with the platform. Every path leads to auditor-grade evidence.

Open Protocol
For every team shipping AI
Install the SDK and start witnessing in 3 lines of code. Full protocol access, Trust Mesh, policy enforcement, 7 language SDKs, public anchor verification.
  • Python, TypeScript, Rust, C#, Ruby SDKs
  • Trust Mesh agent-to-agent verification
  • Policy-as-code attestation via YAML
  • OpenAI, Anthropic, Bedrock, LiteLLM, Ollama, vLLM, LangChain
  • MCP compliance server
  • Open protocol specification (Apache 2.0)
View on GitHub
Regulatory Advisory
For firms navigating compliance
Compliance architecture review aligned to your regulatory obligations. Framework mapping, evidence gap analysis, and implementation guidance from the team behind the protocol.
  • EU AI Act conformity mapping
  • GPAI Code of Practice alignment
  • NIST 800-53 / CMMC / FedRAMP alignment
  • SR 11-7 model risk overlay
  • Evidence chain architecture review
  • Notified Body preparation guidance
Contact Engineering

See the evidence before you commit.

Click through a live audit portal with real compliance evidence. No signup, no sales call. If the evidence speaks for itself, install the SDK or reach out to engineering. The protocol is free and open.