Changing one thing per optimization
Two changes at once and you have learned nothing about either. The chain of versions is the write-up.
Built in·updated 2026-08-03
Change one objective per run, note what moved, keep it or revert it. It feels slower and is not: a plan built by changing three things at a time takes more runs to reach the same place, and leaves nothing you can explain afterwards.
Weight or dose, not both. Raising a weight tells the optimizer to care more about a goal it is already missing. Tightening the dose changes the goal itself. Doing both makes the result uninterpretable.
Write the reason down at the time. The rationale on each script version is what turns a series of attempts into a write-up someone else can follow. Reconstructed afterwards it is always tidier and less true than what happened.
How to do it in
- Per run
- one objective changed
- Record
- objective list + achieved values
Change one objective, re-run, note what moved. Precision keeps the objective list visible next to the achieved values, so the whole state of a run is one screenshot — take it before you change anything.
On this platform each generated script version carries its rationale, and the next version reacts to what the previous one actually missed. That chain is the write-up, so write the reason at the time rather than reconstructing it afterwards.