Operators, product owners, and people affected by the engineering foundations decision.
Engineering foundations
A churn notebook cannot be reproduced by the teammate expected to ship it.
A measurable problem, before a model.
immutable data snapshots, dependency locks, run manifests, schema contracts with version, owner, event time, and availability contracts.
A churn notebook cannot be reproduced by the teammate expected to ship it. Every solution must state latency, cost, capacity, and fallback limits.
Offline evidence plus a deployable resolution: A seeded, tested, packaged, versioned training workflow with a model card.
Reproduce the workflow
Lock the inputs and prove the same run is the same system.
- 01↗
From notebook to reproducible run
Use from notebook to reproducible run to move the engineering foundations production brief toward a defensible release.
65–90 min · checkpoint · deterministic lab - 02↗
Contracts before models
Use contracts before models to move the engineering foundations production brief toward a defensible release.
65–90 min · checkpoint · deterministic lab
Engineer the system
Package, test, observe, and recover the training workflow.
- 03↗
Training code is product code
Use training code is product code to move the engineering foundations production brief toward a defensible release.
65–90 min · checkpoint · deterministic lab - 04↗
Containers and configuration without surprises
Use containers and configuration without surprises to move the engineering foundations production brief toward a defensible release.
65–90 min · checkpoint · deterministic lab
Research-to-production
Read claims critically, reproduce them faithfully, and turn any adaptation into new production evidence.
- 05↗
Observable, idempotent, failure-safe workflows
Use observable, idempotent, failure-safe workflows to move the engineering foundations production brief toward a defensible release.
65–90 min · checkpoint · deterministic lab - 06↗
Read a research paper as an executable specification
Turn a research paper into a testable claim map, implementation contract, and prioritized reading plan before writing code.
65–90 min · checkpoint · deterministic lab - 07↗
Reproduce, validate, and productionize a paper
Implement a paper from baseline to novel component, diagnose reproduction gaps, and adapt it for production without silently changing its claim.
65–90 min · checkpoint · deterministic lab - HW↗
Reproducible baseline package
Design a Docker-only workflow that validates data, trains, evaluates, serializes, performs golden inference, and emits complete lineage.
Rubric · staged hints · reference resolution
Start here with production discipline.
Prerequisites are guidance, never hard gates.