You already know: the ML lifecycle, pipelines, platform tools, feature stores, deployment strategies and monitoring (D11 lessons 1–6); point-in-time joins (SQL for ML); evaluation gates (D10).
Why this matters for Atlas. Each piece of D11 solves one problem; a platform makes them work together so that every model gets the same guarantees for free: reproducibility (any model can be rebuilt from its code, data and config versions), safe deployment (shadow, canary, automatic rollback), observability (drift and performance monitored per model and segment), and freshness (retraining when data or performance says so, through the same gated pipeline). This capstone builds a miniature version of each component in Python and runs a model through its whole life, including a drift event.
1. Lineage: every model traceable to code, data and config
The question. Six months from now, can you rebuild exactly the model that made yesterday's predictions?
Start from nothing. Give every artefact a content hash and record what produced it: dataset versions (hash of the data snapshot or the table version), feature definitions, code commit, config and seed, and the metrics at registration. The registry stores models with this lineage and a stage (staging, canary, production, archived); deployment always references a registry version, never a file path. Promotion requires the candidate to beat the current champion on the evaluation gate.