Open Verification Specification for AI Compliance
An open standard for AI model fingerprinting, compliance attestation, and cross-framework verification.
This document specifies the Open Verification Specification for AI Compliance (OVS-AI), a standard for proving that an AI system has undergone compliance assessment against one or more regulatory frameworks. The specification defines model fingerprinting, compliance attestation, and public verification protocols.
OVS-AI is designed to be implemented by any platform, registry, or compliance tool. It is framework-agnostic and extensible to new regulatory regimes as they emerge. This document is structured following ISO/IEC Directives, Part 2, for potential submission to international standards bodies.
Document Status: Community Draft
This specification is open for community feedback. Submit issues and pull requests on the GitHub repository.
This document specifies requirements for:
This document is applicable to organizations that develop, deploy, procure, or audit AI systems and wish to establish a portable, verifiable compliance record.
This document does not specify the content of regulatory frameworks themselves, nor does it define assessment criteria. It specifies the data structures and protocols for recording and verifying that an assessment was performed.
The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document.
For the purposes of this document, the following terms and definitions apply.
A conforming implementation shall generate model fingerprints using the algorithm specified in 4.2. Identical inputs shall always produce an identical fingerprint. Any modification to the input parameters shall produce a different fingerprint.
The fingerprint shall be computed as follows:
systemId,modelVersion,modelArchitecture,weightsHash.null, not omitted.import { createHash } from "crypto";
interface FingerprintInput {
systemId: string; // UUID of the AI system
modelVersion: string; // e.g. "v2.1.0"
modelArchitecture?: string; // e.g. "transformer-decoder"
weightsHash?: string; // SHA-256 of model weights file
}
function generateFingerprint(input: FingerprintInput): string {
const payload = JSON.stringify({
systemId: input.systemId,
modelVersion: input.modelVersion,
modelArchitecture: input.modelArchitecture ?? null,
weightsHash: input.weightsHash ?? null,
});
return createHash("sha256").update(payload).digest("hex");
}A registry shall store at minimum the following fields for each fingerprint record:
interface RegistryFingerprint {
algorithm: "sha256"; // Hash algorithm identifier
fingerprint: string; // 64-character lowercase hex string
modelVersion: string; // Version of the model at fingerprint time
systemId: string; // UUID of the AI system
registeredAt: string; // RFC 3339 timestamp
}An attestation shall bind a model fingerprint to a compliance assessment result. Each attestation shall reference at least one regulatory framework and shall include an expiration timestamp.
A conforming attestation record shall contain the following fields:
interface RegistryAttestation {
fingerprintId: string; // Reference to the fingerprint record
frameworks: string[]; // e.g. ["eu-ai-act", "nist-ai-rmf"]
overallScore: number; // 0-100 compliance score
attestationDomain:
| "ai-compliance" // Standard AI regulation compliance
| "pqc" // Post-quantum cryptography readiness
| "cross-domain"; // Multiple domains
verificationUrl: string; // Public URL to verify this attestation
issuedAt: string; // RFC 3339 timestamp
expiresAt: string; // RFC 3339 timestamp
}Implementations shall support the following attestation domains:
| Domain | Description |
|---|---|
ai-compliance | AI regulation compliance (EU AI Act, NIST, ISO, state-level) |
pqc | Post-quantum cryptography readiness assessment |
cross-domain | Unified attestation spanning multiple compliance domains |
Attestations shall have a finite expiration. A conforming registry shall not report an expired attestation as "active". Model owners should renew attestations before expiration to maintain continuous compliance status.
A conforming registry shall provide a public, unauthenticated API endpoint that accepts a model fingerprint and returns the verification result defined in 6.3.
The verification process shall follow these steps:
GET /api/v1/registry/lookup?fingerprint={hash} to retrieve the record.The registry shall return a VerificationResult object:
interface VerificationResult {
verified: boolean; // Fingerprint found with valid attestations
fingerprint: RegistryFingerprint;
attestations: RegistryAttestation[];
registryUrl: string; // Canonical URL for this record
}A conforming registry shall support attestations against the following regulatory frameworks at minimum:
| Framework ID | Full Name | Jurisdiction |
|---|---|---|
eu-ai-act | EU Artificial Intelligence Act | European Union |
nist-ai-rmf | NIST AI Risk Management Framework | United States (Federal) |
iso-42001 | ISO/IEC 42001 AI Management System | International |
colorado-ai-act | Colorado AI Act (SB 24-205) | United States (Colorado) |
Conforming implementations should provide a crosswalk mechanism that maps requirements between supported frameworks. This enables a single assessment to partially or fully satisfy multiple compliance regimes.
Registries may support custom frameworks beyond those listed in 7.1. Custom framework identifiers shall use lowercase alphanumeric characters and hyphens (e.g., internal-risk-policy).
This specification defines two conformance levels:
| Level | Requirements |
|---|---|
| Level 1: Verifier | Implements clauses 4.1, 4.2 (fingerprinting), 6.1, 6.2, 6.3 (verification). Can generate fingerprints and verify attestations against a registry. |
| Level 2: Registry | Implements all Level 1 requirements plus clauses 4.3, 5.1–5.4, 7.1 (attestation storage, framework mapping). Operates a public registry with attestation management. |
An implementation claiming conformance to this specification shall state its conformance level and identify any extensions or deviations in a publicly accessible conformance statement.
Attestry (attestry.ai) serves as the reference implementation of OVS-AI 1.0. It implements all Level 2 (Registry) requirements and provides the following public endpoints:
| Endpoint | Clause | Description |
|---|---|---|
POST /api/v1/registry/register | 4.2, 4.3 | Register a model and generate its fingerprint |
GET /api/v1/registry/lookup | 6.1, 6.3 | Public verification — query by fingerprint |
POST /api/v1/registry/validate | 5.1, 5.2 | Validate a .regseal.yml compliance-as-code manifest |
POST /api/v1/registry/auditors/attest | 5.1–5.4 | Third-party auditor attestation issuance |
GET /api/v1/registry/badge/{slug} | 6.3 | Embeddable SVG verification badge |
# Verify a model (public — no authentication required)
curl https://attestry.ai/api/v1/registry/lookup?fingerprint=e3b0c44298fc1c...
# Register a model (requires API key)
curl -X POST https://attestry.ai/api/v1/registry/register \
-H "Content-Type: application/json" \
-H "x-api-key: rs_live_..." \
-d '{"systemId": "550e8400-...", "modelVersion": "v2.1.0"}'Full API documentation: attestry.ai/docs
OVS-AI 1.0 is being prepared for submission to the following standards bodies and regulatory programs. Organizations and national bodies interested in co-sponsoring submissions are invited to contribute via the GitHub repository.
Artificial Intelligence
The primary international standards committee for AI. OVS-AI is positioned as a new work item proposal (NWIP) under SC 42/WG 3 (Trustworthiness) or WG 1 (Foundational standards). The specification complements existing ISO/IEC 42001 by providing a machine-verifiable attestation layer.
Supplementary Materials
NIST maintains a library of supplementary resources for the AI Risk Management Framework. OVS-AI is positioned as a tooling recommendation under the GOVERN and MAP functions, providing a standardized format for recording and sharing AI compliance assessments.
Tooling Recommendations
The EU AI Office develops guidance and tooling for EU AI Act compliance. OVS-AI provides a reference verification protocol for Article 6 (Risk Classification) and Article 9 (Risk Management) compliance evidence, enabling interoperable compliance records across member states.
The OVS-AI specification is developed as an open-source project to enable community feedback, implementation validation, and transparent governance. The specification text, TypeScript type definitions, and reference test suite are published under the Apache 2.0 license.
github.com/regseal/ovs-ai
Contributions welcome via pull requests. See the contribution guide for details on submitting changes, reporting issues, and participating in the standardization process.