1 Introduction
Harness engineering has meant writing the program around the model by hand. A person studies one task, writes one file, and ships it. After that nobody reads the file and nobody scores it, so a wrong guess keeps running for months. The paper's answer is to stop writing that file by hand and let a loop write it, with the model itself untouched.
2 The loop
Each round starts from what failed. A small 4B model reads the failures and proposes 8 edits to the harness file. Every edit is scored on held-out questions, the best one is kept as the next version, and the other seven are dropped. The big model is never retrained: it stays frozen while the file around it changes.
3 What changes
Three parties touch the system and only one of them is a person. The human writes the scoring set: the questions the harness is graded on. The 4B model writes every edit to the harness file. The big model writes nothing; it is the same frozen model in every round, and only the file around it changes.
| Party | Writes | How often |
|---|---|---|
| Human | the scoring set | once, before the loop |
| Loop, 4B model | harness edits | 8 per round |
| Big model | nothing, frozen | runs every round |
4 Conclusion
When a loop writes the harness, frameworks become disposable and the exam becomes the job. The order of work flips: first the questions the harness will be graded on, then the code. That inversion is the paper's real claim, and it is a governance claim as much as an engineering one, because the scoring set is the artifact a human still owns.
- One guess about one task on one afternoon.
- 4B: a model of about four billion parameters, small next to the frozen model it edits for.
- Held-out questions are kept out of the editing step and used only for scoring.