Repo-aware job specs with sealed environments.
Every training job is defined as code in your repository — model, dataset revision, seed, hardware shape, and dependency lock all pinned to the commit that triggered the run. No more "works on my cluster" reruns.
- Hermetic container builds with reproducible lockfiles
- Dataset and checkpoint versions addressed by content hash
- One-command rehydrate of any historical run from cold storage