Existing landscape
Valuable systems, isolated context
- Databases and data warehouses
- Document and case-management systems
- Departmental files and specialist applications
- Separate identities, policies and audit trails
For regulated enterprises & public authorities
MoE Codex links heterogeneous data sources, catalogues and operational context through open interfaces—then makes lineage, approvals and usage traceable for governed AI.
Connect governed data silos without creating a new proprietary dependency. Sources retain their provenance while operators choose which data is queried in place, ingested, related and approved.
The role of Codex
Codex addresses a recurring problem in regulated organisations: operationally valuable context is distributed across databases, documents, specialist applications and organisational boundaries. It connects these sources through modular services deployable under the operator’s control.
Existing landscape
MoE Codex connection layer
The evidence chain
Capability groups
Codex integrates focused open-source services behind explicit interfaces. Operators enable the modules required by their governance model.
Catalogue, federated search, document intelligence, forms and SQL access.
Catalog · OpenSearch · Docling · TrinoVersion datasets, capture lineage and orchestrate ETL and analytical pipelines.
lakeFS · Marquez · NiFi · KestraReview knowledge, apply access policy and retain accountable approvals.
Approvals · OPA · GuardrailsTrack drift, investigate relationships and preserve compliance evidence.
Health · Timeline · Link analysis · FalcoTrack experiments, compare outputs and connect governed data to evaluation.
MLflow · analytics · feedbackNotebooks, BI, maps and case files make governed context operational.
JupyterLite · Superset · Geo · DossiersCompliance support
Codex provides controls and documentation that can support GDPR, EU AI Act, NIS2 and BSI-oriented processes. Conformity remains dependent on purpose, configuration and organisational measures.
OPA is the access-control source of truth; roles and markings remain inspectable.
Lineage, approvals and immutable references connect decisions to data states.
Self-hosted, OCI-portable and air-gap-capable operation without mandatory external APIs.
Modular architecture
Codex communicates with MoE Sovereign through documented REST APIs. Services are configured through environment variables; the core remains independently deployable.
MoE Sovereign
│ HTTP / REST
▼
MoE Codex API
├─ catalogue
├─ approvals
├─ lineage
├─ policy
└─ evidence
MoE ecosystem
Compiles prompts into validated workflows and retains reusable knowledge.
moe-sovereign.org ↗Exchanges reviewed knowledge bundles between independent sovereign nodes.
moe-libris.org ↗Adds governed data operations, lineage, approvals and audit evidence.
You are hereGovernance must be inspectable