HUGO JERIA STRAUSS
Menu
← All writing

NOTE 01 · AI Evaluation · 6 min read

How Culinary Knowledge Can Improve AI Evaluation

Fluent food writing and correct food writing are not the same thing. Most evaluation pipelines are only built to catch the first.

Most people reviewing AI-generated food content are checking for the things general-purpose reviewers are trained to check: clarity, coherence, tone, whether the instructions are internally consistent. Those checks matter, but they don't catch the errors that actually break a recipe or a piece of food guidance in practice. A reduction that's given the wrong time for the stated volume, a leavening ratio that would produce a flat or overly dense result, a food-safety claim that's technically worded correctly but wrong for the ingredient in question — these read as perfectly fluent. They only fail once someone with kitchen experience checks them against how the process actually behaves.

This is the gap that domain-specific evaluation is meant to close. It isn't about having stronger opinions on flavor; it's about having a working, physical model of how food behaves under heat, time, and technique, and using that model to check whether a model's output would survive contact with an actual stove. A rubric built by someone with that background asks different questions: Is this ratio plausible for this method? Would this technique produce the texture being described? Is the safety guidance specific enough to be useful, or so generic it's technically true and practically empty?

In practice, this looks like structured review criteria rather than a simple thumbs up or down. A useful food-evaluation rubric separates plausibility (does this generally sound right), technical correctness (does this hold up against how the physical process works), and safety (is there anything here that could cause harm if followed literally). Reviewers without kitchen background can be trained to flag the first category reasonably well. The second and third categories are where a domain expert earns their place in the pipeline — not replacing general review, but catching what it structurally can't.

The larger point is that food is a physical discipline before it's a language one. Text about food can be well-formed and still wrong in ways that only show up when someone tries to actually cook it. Bringing that practical check into an evaluation process is less about adding another layer of polish and more about adding a layer of reality-testing that a purely linguistic reviewer doesn't have the background to provide.