Field Notes
Keep the Teaspoon
Firefox discovered that a recipe cannot be summarized like an article. Some small details are not supporting material. They are the work.
A teaspoon is not supporting detail.
Mozilla's team discovered this while tuning Firefox's mobile page summarizer. Its general prompt already recognized several kinds of pages: news, reviews, research, opinion, fiction, how-to guides, and recipes. It told the model what to prioritize for each one, then asked for concise paragraphs suitable for a phone.
The approach worked reasonably well until somebody tried to cook from it.
Asked to summarize a lentil soup recipe, the system produced a tidy account of the dish. It named lentils, tomatoes, broth, spices, vegetables, and the trick of blending part of the soup for a creamy texture. It was accurate as description and nearly useless as dinner. The quantities and most of the instructions were gone.
The failure reveals how much judgment hides inside the word summary. For an article, removing examples may leave the central claim intact. For a novel, a short account can omit most events and still convey the plot. A recipe behaves differently. Four cups of broth, one tablespoon of oregano, and one teaspoon of thyme may look like subordinate facts to a model trained to find the gist. To the person holding the measuring spoon, they are the point.
Firefox's response was not simply to demand a better summary. The team created a separate recipe prompt and used structured data embedded in the page to route recipes to it. That path asks for servings, times, ingredients, ordered steps, tips, and nutrition information. Mozilla reports that the change made complete and accurate results more than twice as likely on a curated set of recipe sites.
The important move happens before generation. The system decides what kind of text it has encountered and what that kind of text is allowed to lose.
Researchers working on procedural-text summarization make a related distinction between a global overview and a step-level view that preserves salient entities as their state changes through a process. A recipe is not only prose about soup. It is an ordered record in which onions become translucent, a portion of the mixture becomes smooth, and ingredients introduced earlier remain present even when a later step refers to them only as the soup.
The dedicated prompt is a better fit, but it is still a choice about usefulness. It favors the page as a tool for cooking. A headnote may carry a family history, explain why a substitution matters, credit a tradition, or simply contain the writer's voice. Those parts can be expendable in front of a hot stove without being worthless. Metadata built for search can identify the operational recipe, but it cannot decide everything the page means.
That is why Firefox's support documentation still tells people to check important details against the original. A compact cooking view should remain a view of a source, not quietly become its replacement. It should keep the route back close and distinguish fields copied from the page from language the model reconstructed.
The broader interface lesson is modest. Summarize sounds like one action because the button is the same. In practice, every summary contains a preservation rule. Before making a page shorter, what is this particular transformation meant to keep: the idea, the evidence, the sequence, the voice, or the teaspoon?
