SOUS/AI
A recipe manager built around the fact that you cook the same recipe more than once and change it every time. Versions, variants and diffs, like code.
why
Cooking from batch-cooking books, I kept hitting recipes with ingredients missing from the list. Cooking several meals at once, working out the order of the steps was its own job. And I had no library: the recipes lived in a dozen places.
So: everything in one place, and AI to manage it. Feed the books into the system and get back technical versions with temperatures and times adapted to my kitchen.
versions, not edits
Most recipe apps let you edit a recipe, which throws away what it used to say. Here a recipe is just an identity, and underneath it there is a tree.
Every version is an immutable snapshot pointing at its parent, and a parent can sit on a different branch, which is how a variant forks off a specific version instead of replacing it. «My focaccia» and «my focaccia in a cooler oven» coexist.
Diffs are never stored. They are computed by comparing two snapshots, matching ingredients by normalised name and steps by a stable id, and they even re-derive the baker's percentages so you can see the hydration change alongside the flour.
stack
what it looks like
links
where it is now
It runs on my machine against a local database with 130 recipes, 224 versions and 26 variants in it. Never deployed, and the pantry screen has no data in it yet.
The most ambitious thing here, and the one nobody can click.