Skip to content

Architecture Decision Records

Backfilled ADRs for the load-bearing architectural choices in this repo. Each ADR follows Michael Nygard's format: Context, Decision, Consequences, Status.

Numbered in order of decision, not importance. A decision that turned out to be wrong would be marked Superseded and keep its number.

ID Title Status
ADR-0001 DuckDB as the primary warehouse Accepted
ADR-0002 SQLMesh over dbt Accepted
ADR-0003 Single SQLMesh project across all sources Accepted
ADR-0004 Per-source raw DuckDB catalogs Accepted
ADR-0005 Dagster as the sole orchestrator Accepted
ADR-0006 MotherDuck as the cloud path Accepted