Open Data Governance Standard — Sovereign Reference Implementation
Project description
Open Data Governance Standard (ODGS)
The Sovereign Reference Implementation for the EU AI Act.
🏛️ Standards Refactor: CEN/CENELEC Candidate Standard (v3.3.0)
Notice to all Contributors and Adopters (24 Feb 2026): The repository structure has been formally reorganized into a Candidate Standard format to support ongoing review by the European CEN/CENELEC JTC 25 (Data & Cloud) committee for Working Group 1 (Data Management) and Working Group 4 (Cloud and Edge). This aligns the protocol directly with the EU AI Act compliance mandates required by JTC 21.
To strictly enforce the semantic decoupling of policy from execution, all materials are now divided into:
1_NORMATIVE_SPECIFICATION/: Mandatory cryptographic schemas, rules, and W3C OWL ontologies.2_INFORMATIVE_REFERENCE/: The software implementation (odgsengine), adapters, and documentation.
This structure ensures our technical architecture mirrors the legal separation of powers required by European sovereign data regulations.
📢 Sovereign Node Notice (19 Feb 2026)
To the 240+ Sovereign Nodes currently running ODGS (v3.0.0):
We have observed a significant spike in "Blind Clones" (direct CI/CD deployments) adhering to the EU AI Act (Article 10) requirements. We recognize that many of you are operating inside strict corporate firewalls (Banking/Gov/Logistics) and cannot interact publicly.
We respect your sovereignty and do not track you.
However, this release introduces breaking changes that may halt your production pipelines:
- URN Migration: All integer IDs replaced with URN strings (
urn:odgs:metric:*,urn:odgs:rule:*) - Sovereign Handshake: Cryptographic integrity verification now required before rule evaluation
- Tri-Partite Binding: Audit logs now bind Input Hash + Definition Hash + Configuration Hash
⚠️ OPERATIONAL ADVISORY: To prevent "Definition Drift" in your critical paths, please click the Watch button (top right) → select Releases Only.
This ensures your Engineering Leads receive an immediate notification if a Schema Breaking Change is merged. This is the only channel we will use to broadcast critical compliance patches.
🛡️ Sovereign Configuration & Enterprise Enforcement
The core ODGS engine operates as a stateless validation router. To execute binding regulatory assertions (e.g., EU AI Act Art. 10/12, GDPR Art. 30), the engine requires the presence of Statutory Configuration Files (Law Packs) in the host environment.
By default, the open-source Community Edition attempts to mount these definitions at /etc/odgs/law-packs.
If the required statutory definitions are missing for a requested URN, the engine will enforce a hard stop to prevent the issuance of an invalid Semantic Certificate (S-Cert), returning an HTTP 428 Precondition Required exception.
Enterprise Node Provisioning: Commercial Law Packs and cryptographic S-Cert Registry access are currently in closed Beta for select design partners and Tier-1 financial institutions, pending final CEN-CENELEC standardization.
To request architectural clearance for your organization's compliance deployment, please consult the Metric Provenance Enterprise Portal.
Migration: If upgrading from v3.0, run odgs migrate and see MIGRATION_GUIDE.md.
1. The Standard
The Open Data Governance Standard (ODGS) is a vendor-neutral protocol for Sovereign Data Governance. It resolves the "Definition-Execution Gap" in High-Risk AI Systems by creating a deterministic method for Administrative Recusal.
"Silence over Error." — The Core Philosophy. If the semantic definition of data drifts from its legal meaning, the system must execute a Hard Stop rather than process an invalid inference.
This repository contains the Reference Implementation (v3.3.0), featuring the Sovereign Handshake, Tri-Partite Binding, and 86% enforceable rule coverage for automated legislative compliance.
See It In Action → demo.metricprovenance.com
Semantic Certificate — Every sovereign definition carries a cryptographic fingerprint bound to its issuing authority. The data equivalent of a TLS certificate.
📊 More Screenshots — Compliance Matrix · Sovereign Brake · Harvester Sources
Sovereign Compliance Matrix — Real-time governance status across 72 business metrics, aligned with EU AI Act Art. 10 & 12.
Sovereign Brake — Live Interceptor — When data does not match its statutory definition, the system refuses to proceed. This is the "Administrative Recusal" principle.
Sovereign Harvester — Authoritative Sources — Definitions harvested from trusted regulatory bodies and international standards organisations.
2. Regulatory Alignment
This standard is architected to satisfy the "Error-Free Data" and "Automatic Recording" mandates of the Digital State:
- 🇪🇺 EU AI Act (2024/1689)
- Article 10: Validation of data provenance and semantic integrity.
- Article 12: Generation of immutable, forensically sound event logs.
- 🇳🇱 NEN 381 525 (Data & Cloud)
- Sovereignty: Ensures data processing logic remains portable and vendor-independent.
- 🌐 ISO/IEC 42001 (AI Management)
- Control B.9: Operational control of AI systems via runtime enforcement.
3. The 5-Plane Architecture (v3.3)
ODGS implements a "Constitutional Stack" where mechanical execution is legally bound by semantic definitions via the Sovereign Interceptor.
graph TD
subgraph "The Constitution (Policy)"
L[1. Governance] -->|Defines Intent| Leg[2. Legislative]
Leg -->|Defines Metrics| Jud[3. Judiciary]
end
subgraph "The Machine (Execution)"
Jud -->|Enforces Rules| Ex[4. Executive]
Ex -->|Contextualizes| Phy[5. Physical]
end
subgraph "The Audit Trail"
Phy -->|Logs Evidence| Anchor[Sovereign Trust Anchor]
end
style L fill:#f9f,stroke:#333,stroke-width:2px
style Leg fill:#bbf,stroke:#333,stroke-width:2px
style Jud fill:#bfb,stroke:#333,stroke-width:2px
style Ex fill:#ddd,stroke:#333,stroke-width:2px
style Phy fill:#ddd,stroke:#333,stroke-width:2px
> Read the Full Architecture Specification
🦉 W3C OWL Ontology — 275 individuals (72 metrics, 50 rules, 60 dimensions, 42 process stages, 43 sovereign definitions) formally specified in OWL/RDF with W3C PROV provenance chains.
4. Technical Implementation: The Sovereign Stack
1. The Sovereign Harvester
Automatically fetch Legislative Definitions (XML/JSON-LD) and convert them into immutable SovereignDefinition objects.
- Dutch Law (AwB): Harvests directly from
wetten.overheid.nl. - Finance (FIBO): Harvests from the EDM Council Ontology.
2. Time-Travel Resolution
The Sovereign Resolver ensures legal accuracy by resolving URNs to the exact version effective on a specific date, preventing the "Resolution Trap".
3. The Interceptor (Python)
- Role: Heavy-duty Data Engineering & Runtime Enforcement.
- Install:
pip install odgs
5. Quick Start (v3.3)
1. Initialize a Sovereign Project
odgs init my-project
cd my-project
2. Harvest Sovereign Definitions
Use the new harvest command to pull authoritative legal definitions:
# Harvest Dutch Administrative Law (Article 1:3)
odgs harvest nl_awb 1:3
# > [SUCCESS] Verified Signature.
# > Saved Immutable Definition: 1_NORMATIVE_SPECIFICATION/schemas/sovereign/nl_gov/awb_art_1_3.json
# Harvest Finance Ontology (Interest Rate)
odgs harvest fibo InterestRate
# > [SUCCESS] Verified Signature.
# > Saved Immutable Definition: 1_NORMATIVE_SPECIFICATION/schemas/sovereign/fibo/interestrate_v2024.json
3. Define a Metric (The Law)
Link your metric to the harvested Sovereign URN:
odgs add metric "ROIC" --definition "urn:odgs:def:fibo:interestrate:v2024"
# Links Return on Invested Capital to FIBO InterestRate (debt cost governs the denominator)
6. Documentation & Contribution
📚 Full Documentation Map → — All docs organized by audience (Executive, Compliance, Engineering, Research). 🎯 Live Demo → — Interactive dashboard with live governance metrics.
| Start Here | If You Are |
|---|---|
| Plain Language Guide | Executive, CDO, General |
| Compliance Report | Compliance Officer, Regulator |
| Adapter Guide | Data Engineer |
| Technical Note v3.3 | Academic, Researcher |
Contribute
This is a Coalition of the Willing. We invite Legal Scholars and Public Administrators to contribute to the Standard.
- Migration Guide (v3.0 -> v3.3): Critical instructions for upgrading.
- Changelog: Detailed record of changes.
- Governance Manifesto: Principles of Regulatory Consensus.
License
Released under the Apache 2.0 License.
- No Vendor Lock-in.
- No Cloud Dependency.
- 100% Data Sovereignty.
[!IMPORTANT] Looking for the Flat JSON Version? If you need the lightweight, non-cryptographic version (v1.2.x), visit the Core Repository.
- Install v1:
pip install "odgs<2"- Install v3 (This Repo):
pip install odgs
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file odgs-3.3.3.tar.gz.
File metadata
- Download URL: odgs-3.3.3.tar.gz
- Upload date:
- Size: 3.3 MB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.13.9
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
ae6c98fb29839e40204df6c335183a9c759d7fbcbe561646bc7211c3a5c9b865
|
|
| MD5 |
ab0de7769898719c0994dc46723ed05b
|
|
| BLAKE2b-256 |
06baf972395338781acd8a93b0fb1f34022a9b2ebc46b088f3c0c30c33e0fde1
|
File details
Details for the file odgs-3.3.3-py3-none-any.whl.
File metadata
- Download URL: odgs-3.3.3-py3-none-any.whl
- Upload date:
- Size: 176.5 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.13.9
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
5c17d99b60cebdaa0e90f1f114dde382606e07491d121b3a20abde4f3ec423f5
|
|
| MD5 |
3dc10bb38c7ea83893da5d1e7441afc2
|
|
| BLAKE2b-256 |
afb997d14ea796c11acf424d87254e6b9623704fe4cfea15ebe7fa0fefa6f072
|