Skip to content
PensievePensievePensieve

Recipes

const { recipe } = await pensieve.models.versions.retrieve("grade-audit", "v7");
console.log(recipe?.base_model);
recipe?.steps.forEach((s, i) => console.log(i + 1, s.method, s.description));
recipe?.data.forEach((d) => console.log(d.source, d.use));

A recipe is everything that made a version: the open model it starts from, the training steps in order, and the data each step learns from. It is the result of the experiments so far.

How a recipe grows

Section titled “How a recipe grows”

Every experiment’s A is the current recipe. When B wins and is kept, the change joins the recipe, and the next experiments start from the new one. A version is a recipe that was trained, tested and given a number.

For the sample model grade-audit, v7’s recipe is three kept experiments on an open 8B base:

Step Method From experiment
1 Distil a 70B open teacher’s step-by-step checks exp_0414, +0.4
2 Fine-tune on reviewer verdicts, with overturned grades weighted 4× exp_0418, +1.3
3 Preference-tune on 9,000 pairs of a right and a wrong grade exp_0416, +0.9

Gains measured one change at a time overlap, so they don’t add up: together, the three put v7 1.2 points above v6 on the test. Two other ideas tried in the same weeks, a meta-trained starting point and a longer context, were dropped, so they aren’t in it.

Why you can read it

Section titled “Why you can read it”
  • It is the finding. The recipe says what works on your data, and the experiments behind it say why. That knowledge stays yours.
  • It can be checked. Each step points at the experiment that earned it, with its runs, scores and checks.
  • It is portable. You keep the weights of every version you paid for. A recipe and its weights run on your own servers as well as Pensieve’s.

Next

Section titled “Next”