# Git is the source of truth for contracts

Data product contracts are authored and reviewed in Git, while the runtime catalog/control plane serves promoted projections for discovery, enforcement, orchestration, and agent use. This avoids a dual source of truth: Git owns diffs, review, CI validation, approvals, and history; the runtime plane owns serving and enforcement. Every promoted runtime contract must carry provenance back to the approved Git revision that produced it.