restore single-file training guidance

Co-Authored-By: PI[openai-codex] <288921227+claudypoo@users.noreply.github.com>
This commit is contained in:
wassname
2026-09-02 08:59:10 +08:00
co-authored by PI[openai-codex]
parent c853e90eec
commit 9e6391583a
+2 -3
View File
@@ -64,9 +64,8 @@ separate bugs and weird correlational measurements, and have nothing to show for
the training script we watch it get better, we reuse the same code, we understand it better, and
we squash the bugs. - wassname
The training entry point (often `train.py`) owns the readable narrative. Keep the novel train
loop, forward pass, and loss linear, with tensor shapes at function boundaries; put ordinary
hackable support code in short modules such as `data.py`, `config.py`, and `run.py`.
`train.py`. One file. The novel part is written as a readable narrative with tensor shapes in
comments, so a reviewer can follow it top to bottom without opening other files.
Each long run owns `outputs/<date>_<slug>_<seed>/`: resolved config, commit and argv provenance,
`run.md`, rectangular metrics, ragged demos/generations, and checkpoints. A detached reader must