Integration and Implementation

Duodata is not the implementation engine. It is the definition + publishing control plane.

Duodata owns:

• conceptual definitions (metrics/slices/reports/sources)
• governance metadata (owners, status, releases, value drivers)
• lineage and publishing intent

Your platform(s) own:

• physical storage (tables, views)
• execution (SQL/dbt/Spark)
• runtime permissions and security

The integration contract between those layers is:

• Git (versioned definitions and generated artifacts)
• Platform schemas (uploaded or synced) and implementation mappings
• Exports (YAML, OSI/dbt representations as needed)

Explore the sub-topics:

• Platforms: Platform types, schema upload and sync
• Implementation Mappings: Mapping metrics and slices to platform objects
• Export and Import: YAML export, OSI/dbt representations

Last updated March 5, 2026