Agents enter with code. They leave with traces.
Training Day Redline is a cost-capped proving harness for ML systems work. A coding agent edits candidate kernel, CUDA and inference code inside a bounded benchmark. What comes out is a replayable evidence record that someone else can verify.
What a run emits
One record per trial. Six lines of manifest, and a list of what never ships.
api_cost_usd gpu_minutes wall_clock_minutes, with the observed values against each ceiling.scripts/tdpack_verify.py and no account.Redline
Every Rep runs under three ceilings. Cross one and the run is marked failed, the correctness result stays factual, and automation exits non-zero.
A missing measurement is rejected, not treated as free usage. Absent, negative and non-finite API, GPU and wall-clock readings fail closed.
Gauntlet Zero: Kernels
The CPU-safe drill pack. A CUDA drill with a CPU semantic oracle is in development.
Where it stands
Written down because the harness insists on it.
Public pack, not released
The harness and the eleven drills are built and running. The public distribution is still in private development.
Leaderboard, unranked
Ranking is gated on a sealed execution attestation that does not exist yet. Until then, a proof verifies correctness and nothing else.
No account, no telemetry
Runs are local. Exports are explicit. Nothing is uploaded, and there is no update check.