Decisions (ADRs)

An Architecture Decision Record (ADR) is a short page that records one design decision: why we made it, what we chose, and what it costs. Read these pages when you want to know why quicketl is built the way it is.

All nine records below were agreed on 2026-10-30. Records marked "planned for 2.0" describe the target design. The code does not do this yet.

ADR	Decision	Status
0001	One repo, one tool: "quick data engineering"	Accepted (planned for 2.0, not yet implemented)
0002	Platform-first default with a slim core and a [pipelines] extra	Accepted (planned for 2.0, not yet implemented)
0003	quicketl init becomes a wizard	Accepted (planned for 2.0, not yet implemented)
0004	Airflow on MWAA is the default orchestrator	Accepted
0005	First reference stack: Snowflake, Terraform, dbt and Airflow	Accepted
0006	Generated projects use native loaders and dbt tests	Accepted (planned for 2.0, not yet implemented)
0007	Templates, Terraform modules and the dbt package are pulled from git tags	Accepted (planned for 2.0, not yet implemented)
0008	Project-root relative paths with a --base-dir override	Accepted (ships in 1.7.0)
0009	Release plan: 1.7.0 and 2.0.0, released through a dev branch	Accepted

Record format

Each record has a title, a status, a context, a decision, and the consequences (good and bad). A record is not edited once accepted. A later record supersedes it instead.