Milestone E

Each milestone is scored out of twenty under the peer-review protocol: five criteria, 0 to 4 each. Score 0 for missing evidence, 1 to 2 for an incomplete artifact, 3 for a sound artifact with limited measurement, and 4 for reproducible evidence with the measurement, its noise and its limitations stated. 14 of 20 passes. A high score never overrides a failed mastery gate.

• The track artifact, complete as the module defines it.
• One merged upstream contribution.
• Track A: a model upgrade demonstrated as config plus eval run, and the trifecta broken in code. Track B: a speedup that survives a hidden test distribution and a library baseline, placed on the roofline. Track C: a replication plus one-variable ablation with negative results, reviewed by someone outside your circle.
• A public write-up of the artifact with numbers and a limitations section.
• A talk given, or a cohort or fellowship application submitted.

Challenge: a stranger reads your write-up and asks the hardest "why" you can imagine. Write the question and your answer.

Submission checklist

For each milestone include: commit identifier; environment and setup; exact commands; the measurement, its denominator and its noise; what you expected before running; what you observed; limitations; next steps. Anything not run (a GPU run you could not afford, users you could not recruit) must say "not done", not be implied. Grade reasoning and reproducibility, not screenshots.

Use the instructor keys for module reasoning and the capstone for the final practical assessment.