Skip to main content

Open Data Governance Standard — Universal Validation Primitive

Project description

Open Data Governance Standard (ODGS)

Protocol Compliance DOI PyPI Downloads npm Downloads License

The Universal Validation Engine for High-Risk Data.


[!IMPORTANT] EU AI Act & CEN-CENELEC JTC 25 Candidate Standard (v5.0.0 Update) ODGS has been upgraded to a strict Polymorphic Execution Engine. It seamlessly evaluates your standard operational telemetry while natively ingesting authoritative W3C/JSON-LD legal ontologies (e.g., TNO FLINT) to enforce Administrative Recusal ("Hard Stop") in High-Risk AI pipelines.


🚀 What's New in v5.0.0: The Execution Plane

In alignment with European Data Space architectures (NEN 381 525), ODGS v5 structurally repositions as the missing Execution Plane for Civic Tech and "Rules as Code" initiatives.

  • Deprecation of NLP Harvesters: We are no longer trying to solve the problem of "Reading the Law." We are exclusively solving the problem of "Cryptographically Enforcing the Law."
  • Authoritative JSON-LD Ingestion: ODGS now natively delegates legal parsing to authoritative upstream sources (e.g., TNO FLINT). This eliminates vendor-specific legal interpretations and allows Sovereign States to act as their own Certificate Authorities.
  • Cryptographic Seals (SHA-256): Ingestion now generates a deterministic hash at the physical boundary. If the upstream authoritative source changes its JSON-LD definition, the downstream cryptographic execution seal is instantly invalidated.

🏢 Enterprise & Public Sector: EU AI Act Compliance

This open-source package connects your physical data infrastructure to the ODGS validation engine. However, if you are operating a High-Risk AI System and require strict liability indemnification under the EU AI Act (Articles 10 & 12), you need cryptographic provenance.

Metric Provenance offers the commercial Enterprise Infrastructure for ODGS:

  • Certified Sovereign Packs: Pre-compiled, cryptographically signed Ed25519 rule bundles for DORA, EU AI Act, and Basel.
  • The S-Cert Sovereign Registry: An air-gapped Enterprise Certificate Authority that natively ingests ODGS telemetry to mint immutable, JWS-sealed audit logs.

👉 Discover the Sovereign CA Enterprise Node & Packs


1. The Standard: Data Governance Without Compromise

The Open Data Governance Standard (ODGS) resolves the "Definition-Execution Gap" in data pipelines.

"Silence over Error." — The Core Philosophy. If data drifts from its legal, contractual, or internal definition, the pipeline must mathematically halt rather than process an invalid inference.

Semantic Certificate — Every sovereign definition carries a cryptographic fingerprint bound to its issuing authority. The data equivalent of a TLS certificate.

Semantic Certificate — cryptographic fingerprint bound to the Government of the Netherlands, with VALID status badge and SHA-256 content hash

📊 More Screenshots — Compliance Matrix · Sovereign Brake

Sovereign Compliance Matrix — Real-time governance status across 72 business metrics, aligned with EU AI Act Art. 10 & 12.

Sovereign Compliance Matrix showing 72 business metrics, domain filters, and Naked vs Sovereign status

Sovereign Brake — Live Interceptor — When data does not match its statutory definition, the system refuses to proceed. This is the "Administrative Recusal" principle.

Sovereign Brake showing HARD_STOP enforcement rules with regex validation


2. Quick Start: The Data Engineer Workflow

Stop relying on passive analytics dashboards. Enforce statutory rules directly in your Python transforms.

Install

pip install odgs==5.0.0

Example: Halting a Pipeline in Python/dbt

Inject ODGS directly into your data warehouse transforms, Airflow DAGs, or Databricks PySpark wrappers:

from odgs.executive.interceptor import OdgsInterceptor
from odgs.executive.exceptions import AdministrativeRecusal

engine = OdgsInterceptor()

# The physical payload (e.g., an AI applicant profile or standard telemetry)
payload = {"transaction_value": 150000, "aml_flag": False}

try:
    # Evaluate against your internal checks or mathematically hashed W3C JSON-LD ontologies
    engine.intercept("urn:odgs:sov:eu-ai-act:aml-threshold", payload)
    print("Payload Validated. Proceeding to inference.")
    
except AdministrativeRecusal as e:
    # The pipeline HALTS before an illegal decision is made.
    print(f"HARD STOP EXECUTED: Data Drift Detected. {e}")

3. The 5-Plane Semantic Architecture (v5)

ODGS v5 implements a strict 5-Plane topology to guarantee the absolute sovereignty of legislative intent over physical execution pipelines.

graph TD
    subgraph Legislative_Plane ["I. Legislative Plane (Semantic Truth)"]
        FLINT[TNO FLINT / W3C JSON-LD] --> |Semantic Hash| Definition(Statutory Definition)
    end
    
    subgraph Physical_Plane ["II. Physical Plane (ODGS Execution Engine)"]
        Definition -.-> |Cryptographic Tether| Boundary[Execution Boundary]
        Boundary --> Eval{Constraint Evaluation}
        
        Pipeline[IV. Data Pipeline Plane] --> |Payload| Eval
        
        Eval --> |Compliant| Approved[Execution Authorized]
        Eval --> |Data Drift Detected| Recusal[Administrative Recusal]
        
        Approved --> Audit[V. Forensic Audit Plane]
        Recusal --> Audit
        
        Audit --> |Generates| SCert[S-Cert: Immutable JWS Provenance Log]
    end

4. Platform Bridges

ODGS bridges connect your existing data governance platform to the Execution Engine, transforming passive data dictionaries into active runtime enforcement.

Bridge Function Status
odgs-flint-bridge Legislative: Ingests TNO FLINT JSON-LD into ODGS schema. PyPI Downloads
odgs-collibra-bridge Physical: Collibra Business Glossary integration. PyPI Downloads
odgs-databricks-bridge Physical: Databricks Unity Catalog integration. PyPI Downloads
odgs-snowflake-bridge Physical: Snowflake Data Dictionary integration. PyPI Downloads

Want to build a bridge? ODGS is designed to be the enforcement layer for any data governance platform. Open an issue or submit a PR.


5. Air-Gapped Execution & Stateless Cryptography (JWKS)

The ODGS Engine operates with Zero Telemetry and does not "phone home". It is designed for strict air-gapped enterprise environments.

To ensure metric authenticity, ODGS implements stateless cryptography using standard Ed25519 JWKS (JSON Web Key Set) public keys. When the Engine loads a Sovereign Pack, it cryptographically verifies the signature against the cached JWKS public key.


6. Audit Ledgers: Cryptographic Verifiability & Zero-Knowledge

ODGS outputs an agnostic cryptographic_attestation JSON schema to satisfy EU AI Act Article 12 (Forensic Logging) without exposing third-party data.

  • Git-as-Backend: ODGS utilizes a privacy-native logging architecture. Forensic logs are written directly to your private enterprise Git repository. Zero data ever leaves your perimeter.
  • The Tri-Partite Hash: The engine generates a cryptographic proof binding the Input Data Hash + Rule Definition Hash + Engine Configuration Hash. Independent auditors and regulatory bodies can mechanically verify the integrity of algorithmic decisions without exposing PII.

7. Enterprise Deployment (Kubernetes / Helm)

For organization-wide policy enforcement, Sovereign Nodes can deploy ODGS as an active sidecar container routing mesh traffic.

# Add the Official Metric Provenance Repository
helm repo add metricprovenance https://charts.metricprovenance.com
helm repo update

# Install the Engine
helm install odgs-cluster-agent metricprovenance/odgs-engine \
  --set configuration.namespace="urn:odgs:sov" \
  --set keys.jwks_url="https://platform.metricprovenance.com/.well-known/jwks.json"

To request architectural clearance for your organization's compliance deployment, please consult the Metric Provenance Enterprise Portal.


8. Documentation & Contribution

📚 Full Documentation Map → 🎯 Live Demo →

Guide Description
Migration Guide (v4.0 -> v5.0) Critical instructions for the Polymorphic Engine upgrade.
Adapter Guide For Data Engineers connecting ODGS to custom infrastructures.
Audit Ledger Guide For Big 4 Auditors verifying the Tri-Partite Hash.

Support & Community

  • Bug Reports & Feature Requests: Please use the GitHub Issues tracker.
  • Enterprise Compliance Deployments: For architectural clearance, SLA support, or custom Law Packs, please contact us via the Enterprise Portal.

License

Released under the Apache 2.0 License.

  • No Vendor Lock-in.
  • No Cloud Dependency.
  • 100% Data Sovereignty.

ODGS | Developed by Metric Provenance | The Hague, NL 🇳🇱

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

odgs-5.0.1.tar.gz (402.8 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

odgs-5.0.1-py3-none-any.whl (169.7 kB view details)

Uploaded Python 3

File details

Details for the file odgs-5.0.1.tar.gz.

File metadata

  • Download URL: odgs-5.0.1.tar.gz
  • Upload date:
  • Size: 402.8 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.9

File hashes

Hashes for odgs-5.0.1.tar.gz
Algorithm Hash digest
SHA256 2055ee7478eeccbdcd769ec6360a24efa1439abeeb5c6522f10c1910bd69c94f
MD5 0c41a11ec51d8ee2e11a0b1db41de90a
BLAKE2b-256 55263039a535fed23a32128850d4df4e634398cde13595a0919565a24cfdcd50

See more details on using hashes here.

File details

Details for the file odgs-5.0.1-py3-none-any.whl.

File metadata

  • Download URL: odgs-5.0.1-py3-none-any.whl
  • Upload date:
  • Size: 169.7 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.9

File hashes

Hashes for odgs-5.0.1-py3-none-any.whl
Algorithm Hash digest
SHA256 d0053735cfedfb1beab0d74e6721faedd54ad2e56cf458c81161457ccc83e731
MD5 3caafc9ebc90d7ba8e49518f5529eba1
BLAKE2b-256 7db6d62c80a52303c22be1892ca1235e585e95cd64bff28910a20b980cf3ff05

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page