Attestry
BrowseOrganizationsLeaderboardCompliance-as-CodeProcurement ReportRegister
Powered by
RegSeal
← Back to Registry

OVS-AI 1.0

v1.0.0

Open Verification Specification for AI Compliance

An open standard for AI model fingerprinting, compliance attestation, and cross-framework verification.

Download PDFOpen Source & Community

OVS-AI 1.0

Foreword1 Scope2 Normative References3 Terms & Definitions4 Model Fingerprinting5 Attestation Schema6 Verification Protocol7 Framework Mapping8 ConformanceA Reference ImplementationB Submission TargetsC Open Source
Download PDF ↓GitHub Repo →

Foreword

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.

1 Scope

This document specifies requirements for:

  1. generating deterministic fingerprints for AI model versions;
  2. creating compliance attestation certificates that bind a fingerprint to regulatory framework assessment results;
  3. publicly verifying the compliance status of an AI model using only its fingerprint;
  4. mapping attestation results across multiple regulatory frameworks via a crosswalk mechanism.

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.

2 Normative References

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.

  • ISO/IEC 42001:2023, Information technology — Artificial intelligence — Management system
  • NIST AI 100-1, Artificial Intelligence Risk Management Framework (AI RMF 1.0)
  • FIPS 180-4, Secure Hash Standard (SHA-256)
  • RFC 8259, The JavaScript Object Notation (JSON) Data Interchange Format
  • RFC 3339, Date and Time on the Internet: Timestamps
  • W3C Verifiable Credentials Data Model v2.0, Credential issuance and verification

3 Terms and Definitions

For the purposes of this document, the following terms and definitions apply.

3.1 model fingerprint
Deterministic SHA-256 hash of a canonical JSON payload containing an AI system's identifying attributes, used to uniquely identify a specific model version.
3.2 attestation
Cryptographically bound certificate that associates a model fingerprint with the results of a compliance assessment against one or more regulatory frameworks.
3.3 attestation domain
Category of compliance an attestation covers: AI compliance, post-quantum cryptography readiness, or cross-domain.
3.4 verification
Process by which a third party confirms the compliance status of an AI model by querying a public registry using the model's fingerprint.
3.5 framework crosswalk
Mapping of requirements between regulatory frameworks, enabling a single assessment to partially or fully satisfy multiple compliance regimes.
3.6 registry
Public service that stores model fingerprints, attestation records, and provides a verification API.
3.7 conforming implementation
A system that implements all mandatory requirements (clauses marked "shall") of this specification.

4 Model Fingerprinting

4.1 General

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.

4.2 Algorithm

The fingerprint shall be computed as follows:

  1. Construct a JSON object with exactly these fields in this order:systemId,modelVersion,modelArchitecture,weightsHash.
  2. Absent optional fields shall be serialized as JSON null, not omitted.
  3. Serialize using RFC 8259 canonical form (no whitespace, no custom replacer).
  4. Compute SHA-256 (FIPS 180-4) of the UTF-8 encoded string.
  5. Encode the digest as a lowercase 64-character hexadecimal string.
Reference: Fingerprint Computation (TypeScript)
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");
}

4.3 Fingerprint record

A registry shall store at minimum the following fields for each fingerprint record:

RegistryFingerprint (TypeScript)
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
}

5 Attestation Schema

5.1 General

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.

5.2 Required fields

A conforming attestation record shall contain the following fields:

RegistryAttestation (TypeScript)
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
}

5.3 Attestation domains

Implementations shall support the following attestation domains:

DomainDescription
ai-complianceAI regulation compliance (EU AI Act, NIST, ISO, state-level)
pqcPost-quantum cryptography readiness assessment
cross-domainUnified attestation spanning multiple compliance domains

5.4 Expiration and renewal

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.

6 Verification Protocol

6.1 General

A conforming registry shall provide a public, unauthenticated API endpoint that accepts a model fingerprint and returns the verification result defined in 6.3.

6.2 Verification steps

The verification process shall follow these steps:

  1. 1
    Obtain Fingerprint — The model provider publishes the 64-character hex fingerprint.
  2. 2
    Query Registry — Send GET /api/v1/registry/lookup?fingerprint={hash} to retrieve the record.
  3. 3
    Validate Attestations — Confirm the attestation covers required frameworks, status is "active", and expiration is in the future.
  4. 4
    Verify Integrity — Optionally verify the zero-knowledge proof to confirm compliance without accessing underlying assessment data.

6.3 Verification result

The registry shall return a VerificationResult object:

VerificationResult (TypeScript)
interface VerificationResult {
  verified: boolean;              // Fingerprint found with valid attestations
  fingerprint: RegistryFingerprint;
  attestations: RegistryAttestation[];
  registryUrl: string;            // Canonical URL for this record
}

7 Framework Mapping

7.1 Supported frameworks

A conforming registry shall support attestations against the following regulatory frameworks at minimum:

Framework IDFull NameJurisdiction
eu-ai-actEU Artificial Intelligence ActEuropean Union
nist-ai-rmfNIST AI Risk Management FrameworkUnited States (Federal)
iso-42001ISO/IEC 42001 AI Management SystemInternational
colorado-ai-actColorado AI Act (SB 24-205)United States (Colorado)

7.2 Crosswalk mechanism

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.

7.3 Custom frameworks

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).

8 Conformance

8.1 Conformance levels

This specification defines two conformance levels:

LevelRequirements
Level 1: VerifierImplements clauses 4.1, 4.2 (fingerprinting), 6.1, 6.2, 6.3 (verification). Can generate fingerprints and verify attestations against a registry.
Level 2: RegistryImplements 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.

8.2 Conformance statement

An implementation claiming conformance to this specification shall state its conformance level and identify any extensions or deviations in a publicly accessible conformance statement.

Annex A (informative): Reference Implementation

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:

EndpointClauseDescription
POST /api/v1/registry/register4.2, 4.3Register a model and generate its fingerprint
GET /api/v1/registry/lookup6.1, 6.3Public verification — query by fingerprint
POST /api/v1/registry/validate5.1, 5.2Validate a .regseal.yml compliance-as-code manifest
POST /api/v1/registry/auditors/attest5.1–5.4Third-party auditor attestation issuance
GET /api/v1/registry/badge/{slug}6.3Embeddable SVG verification badge
Quick Verification (cURL)
# 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

Annex B (informative): Standards Body Submissions

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.

ISO/IEC JTC 1/SC 42

Draft preparation

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.

NIST AI RMF

Contribution planned

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.

EU AI Office

Contribution planned

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.

Annex C (informative): Open Source

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.

Repository

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.