Metric Provenance
Zero-cookie, infrastructure-level verification.
Intelligence Brief
+65% 7d momentumProtocol adoption spans 86 sovereign jurisdictions led by United States. 40% of all PyPI downloads originate from enterprise mirror infrastructure — organisations adding ODGS to internal package registries, indicating formal procurement approval. Microsoft Teams internal sharing signal detected — the ODGS certificate URL has been forwarded inside one or more enterprise organisations, indicating active discussion at architecture or compliance board level.
§1 — Adoption Evidence
Real engineers running real code.
GitHub clones are manual pull requests by developers evaluating ODGS for production use — each represents a developer or team deliberately pulling the protocol for evaluation. The geo-plot shows every country that has downloaded ODGS from PyPI, the world's primary Python registry.
Protocol Velocity
Jul 8 — Oct 3 · GitHub Views vs Engineer Clones
Global Installation Geo-Plot
Each bubble is a country that has run ODGS. Bubble size = total installs. Colours = which packages are active in that market.
Sovereign Jurisdiction Matrix
Each row = a country that has evaluated ODGS. Core = base protocol installs. Bridge pills show which enterprise connectors are active in that market — each connector represents a different integration partner stack (Flint, Collibra, Databricks, Snowflake).
Environment details visible on wider screens.
§2 — Adoption Intelligence
The integration signal — engineers building, not just testing.
Bridge connectors are installed on top of the core protocol to wire ODGS into production data systems (Flint, Collibra, Databricks, Snowflake, LLM). Organic bridge growth — distinct from automated CI cycles — confirms active enterprise integration work. Latest-version adoption marks the commercial release generation.
Flint Bridge — Enterprise Connector
Dedicated connector for Flint-based data pipelines — distinct from core protocol installs.
MCP Server — AI Integration Layer
Model Context Protocol server — exposes ODGS governance data to LLM agents and AI workflows.
Enterprise Upgrade Velocity
v5.x → v6.xv6.x is the current release. Engineers pinning to the latest major version are preparing production environments, not experiments.
Granular Version Adoption
All-time · per releaseExact per-release download counts — tracks which specific builds evaluators are pinning to.
| Version | Downloads |
|---|---|
| v6.0.6 | 1,149 |
| v6.0.5 | 680 |
| v6.0.4 | 659 |
| v6.0.3 | 771 |
| v6.0.2 | 800 |
| v6.0.1 | 620 |
| v6.0.0 | 671 |
| v5.2.0 | 986 |
| v5.1.0 | 1,126 |
| v5.0.1 | 891 |
| v5.0.0 | 966 |
| v4.0.1 | 721 |
§3 — Distribution Channels
Enterprise mirrors, corporate pipelines, academic publishing.
A significant share of installs originate from enterprise mirror infrastructure — private artifact registries (Nexus, Artifactory) inside organisations where a procurement or security team has formally approved the package. Weekday-heavy install patterns confirm corporate, not hobbyist, use. Academic downloads from Zenodo indicate research and standards citation.
Execution Timelines
Weekday-heavy patterns confirm enterprise, not hobbyist, use
Python Ecosystem
Backend version matrix — confirms production-grade environments
Academic Impact
Zenodo DOI Tracking
Traffic Sources
Where engineers arrive from — referrer origins
Popular Paths
Most evaluated repo content
npm Daily Trend
SDK download velocity (JavaScript / TypeScript consumers)
Operating Systems
Execution environments
CPU Targets
Hardware architecture
Linux Distros
Server & container distributions
Install Vectors
Enterprise mirror syncs vs CI pipelines
§4 — Strategic Intelligence
Market-level signals across sovereignty boundaries.
First-seen dates reveal the pace of geographic spread — from initial adoption to active use. Bridge-ready markets show where integration demand exists. Countries with latest-version installs are the highest-probability targets for commercial Sovereign CA Node deployments.
Geographic Expansion
First download per jurisdiction — tracks protocol spread
Bridge-Ready Markets
Countries with bridge downloads — integration-ready signals
v6.x Enterprise Formations
High-probability targets for Sovereign CA Nodes — isolated v6.x commercial adoption
Repeat vs one-time environments — distinguishes adoption from evaluation
Ecosystem Footprint
Multi-registry, multi-language distribution surface.
ODGS is distributed across PyPI (Python), npm (JavaScript/SDK), Helm Charts (Kubernetes), and GitHub. Combined, these registries represent the full deployment footprint across engineering stacks.
Package Downloads
PyPI downloads (last 30 days) — all ODGS packages
Repository Traffic
Views & clones across all MetricProvenance repos
Bridge-to-Core Ratio (Last 30d)
Bridge downloads vs core — measures ecosystem pull-through
Total Ecosystem
Combined PyPI + npm downloads
Distribution Surface
Artifacts published across registries
Metric Provenance Platform. Strictly internal distribution.