A recipe is one of the easiest forms of writing to fake convincingly.
It has a predictable structure: ingredients, quantities, steps, temperature, cooking time, serving suggestion. A language model has seen enough of that pattern to generate something that looks like a recipe almost instantly.
What the page cannot tell you is whether anybody actually cooked it.
That difference matters more than it might seem. Kitchen testing checks relationships that fluent text cannot verify by itself: whether the dough is too wet, whether the sauce splits, whether the stated temperature burns the food, whether the timing is realistic, whether the proportions produce twelve servings or three, and whether an unusual ingredient combination is safe.
Plausible instructions are not the same as tested instructions
A striking example appeared in 2023 when New Zealand supermarket Pak ‘n Save released its Savey Meal-bot, an AI tool intended to suggest meals from ingredients users had on hand. When people began entering household products rather than normal groceries, the system generated dangerous outputs, including an “aromatic water mix” that would create chlorine gas. The supermarket’s warning stated that generated recipes were not reviewed by a human and were not guaranteed to be suitable for consumption. The incident was reported in detail by The Guardian.
That case involved deliberately adversarial inputs, so it should not be treated as proof that ordinary generated recipes routinely become chemical weapons. It demonstrates something narrower and more useful: the system could produce authoritative-looking culinary instructions without having any physical process behind them to catch the nonsense.
A kitchen would have caught it immediately.
Testing is evidence
Traditional recipe development often looks inefficient compared with text generation because somebody cooks the thing repeatedly. Ingredients get weighed. Oven temperatures get adjusted. Instructions get rewritten when a supposedly obvious step turns out not to be obvious.
That labor produces information.
A publisher can certainly use AI to brainstorm variations, rewrite instructions, scale quantities, or organize existing recipes. But a collection of generated recipes should not quietly inherit the authority of a tested cookbook if nobody has tested the results.
Useful disclosure can be simple: “AI-generated suggestion, not kitchen-tested,” or “Developed with AI assistance and tested by our kitchen.” Those two statements describe very different products.
Synthetic recipe collections are interesting because they expose a larger problem with generated content. The page can reproduce the form of expertise while skipping the physical act that originally created the expertise.
For food writing, the missing evidence is sitting in a pan.