The Recipe Changed. The Cupboard Didn’t.

The spreadsheet has stopped describing the cupboard

You ask an AI assistant to help plan a few recipes. It gathers the ingredients and builds a shopping list. Then you change one recipe, and a number in your inventory changes too. Nobody bought anything. Nobody opened the bag. The spreadsheet has quietly stopped describing the cupboard.

A homebrewer on Reddit described that kind of frustration: recipe revisions led to overwritten inventory quantities and incorrect totals. That is one person’s report, not an independent evaluation of the product. It raises a useful question for anyone handing a changing plan to AI: which numbers is it allowed to change?

Start with one ingredient you can check

Imagine two recipes that use the same malt. Recipe A needs 2 kg and recipe B needs 3 kg. You weigh the usable stock in your cupboard: 1.5 kg. The recipes need 5 kg altogether, so the shopping list should say 3.5 kg.

Now revise recipe A to use 4 kg. Recipe B stays at 3 kg. The total needed becomes 7 kg, and the shopping amount becomes 5.5 kg. Your measured stock remains 1.5 kg. No purchase, use or correction to the stock count has happened.

That is the whole example. Before trusting hundreds of rows, make this one row easy to inspect.

Give each number a clear home

Keep measured inventory in its own record: ingredient, quantity, unit, and when you checked it. Only a real stock event or a verified correction should change that record. A larger recipe is neither.

Keep the proposed recipe plan separately, with quantities attached to each recipe. Let the assistant propose revisions there. Derive the shopping list from the current plan and the verified inventory. For this example, subtract stock from demand, with a minimum shopping quantity of zero.

Keep your original inventory outside the assistant’s write access wherever possible, and ask for proposed edits in a separate output. A sheet named “Do not edit” or a sentence in a prompt does not create write protection. Check the actual access controls and compare the original with any returned file.

Ask for a visible change log

A useful request is: “Use this inventory only as a reference. Propose the recipe revision separately. Show each changed recipe quantity, the old and new total demand, and the resulting shopping quantity. Flag missing units or uncertain ingredient matches. List any proposed inventory correction for me to review separately.”

In our illustration, the log would read: recipe A, 2 to 4 kg; total demand, 5 to 7 kg; shopping amount, 3.5 to 5.5 kg; measured inventory, unchanged at 1.5 kg. This is the expected result, not a recorded AI response.

Check the small example before scaling up

Recalculate the two totals yourself. Check that the stock record still says 1.5 kg. Compare the revised recipe with its source, and confirm the shopping formula still points to the right cells. If a number changed without an explanation, stop and resolve it before adding more recipes.

For a larger list, also check units and ingredient identities before combining rows. Keep pack-size rounding and substitutions separate from the amount actually needed. A tidy total can still combine the wrong things.

Passing this small check would show that this particular revision worked. It would not prove the assistant will handle every later edit correctly. Keep checking consequential changes against the recipes and the physical stock.

AI can help organize a plan and make its changes easier to review. The person standing in front of the cupboard still has to establish what is actually there.