Iterating and promoting

A completed test run holds the exact weights you used, the checkpoint readings, the yield, the cost, and a tasting outcome. The Iterate card on a completed run feeds all of that back into the recipe.

Two ways to iterate

• Write back to this version updates the version you ran with what you observed. Use it when the run simply corrected the paper recipe: the version’s numbers now match what works at the pot.
• Promote to new version leaves the version you ran untouched and creates a new version from the run. Use it when the batch deviated on purpose (you pushed the habanero share and liked it) and you want both states side by side.

A run is promoted once. Afterwards the card links to the recipe and reads “This run was promoted into a new version”.

The tasting outcome

The tasting score (1 to 10) and notes you captured during the run travel with it. Scores make versions comparable at a glance: version 3 scored 6, version 4 scored 8, keep 4. Compare versions side by side and mark the winner as current on the recipe’s versions page; the mechanics are covered in versioning.

Why runs beat a notebook

Trial 14 in a paper notebook says “less vinegar, better”. A test run says: 118 g of vinegar against 132 g planned, pH 3.6 measured, 91% yield, €2.14 per jar, tasting 8. Every trial keeps the same structure, so dozens of them stay comparable months later, and promoting the good one takes one click. That loop (plan, run, taste, promote) is what test runs are for.