The Quiet Work of Allergy Alerts.

It was a Saturday in October, the kind of evening where the apartment had been warm since four in the afternoon and the satay sauce had been simmering since five, when my friend Marit walked in with her seven-year-old daughter and I remembered, with the small cold drop in the chest that any parent will recognise, that the daughter was severely allergic to peanuts. The sauce on my stove contained, by volume, a great deal of peanut. I had read the recipe three times that afternoon. I had not seen it.

The dinner was saved, in the end, by a tin of cashew butter at the back of the cupboard and twenty minutes of improvisation that I have, for the most part, edited out of my memory. What I have not edited out is the moment of standing at the stove with a wooden spoon in my hand and the knowledge that I had, very nearly, hurt a child whose mother trusted me with her dinner. The recipe had not warned me. The app I had imported it from had not warned me. No piece of software in my kitchen — and I am, by trade, a person who works with software — had thought to warn me. The warning had lived, the entire time, in my own head, and my own head had failed.

§ I.The mental load nobody talks about.

Every household I know that contains an allergy contains, in the cook, a particular kind of background hum. A friend whose husband has a shellfish allergy reads every menu, every recipe, every label, with a small piece of her attention permanently dedicated to the word shrimp and its synonyms. A colleague whose son is coeliac has memorised the wheat content of seventeen brands of soy sauce. My neighbour, whose elderly mother lives with her, runs every Sunday roast through a quiet mental filter for sulphites in the wine that goes into the pan. None of these women speak about this work. They simply do it, every meal, every guest, every recipe, for years on end.

The mental load is not dramatic. It is not the headline of any cookbook or the subject of any food-magazine essay. It is the small, repeated act of glancing at an ingredient list and looking, before reading anything else, for the one thing that must not be there. Multiplied across a week of dinners, a season of dinner parties, a decade of family meals — it is, in aggregate, an enormous amount of work. And it is work that fails, sometimes, because the human attention is finite and the cook, on a Saturday evening with a friend at the door, is also tired.

What I want to argue, gently, is that this is precisely the kind of work that software should be doing. Not instead of the cook — the cook is still the cook, and the responsibility is still the cook's — but in the background, as a quiet second pair of eyes, every time, without being asked.

§ II.Why most recipe apps offer nothing for this.

I went looking, after the satay incident, for the feature in any of the recipe apps I had tried. There were, broadly, three things on offer. Some apps let me filter recipes by dietary tag — vegetarian, vegan, gluten-free — at the moment of discovery, which is useful when you are deciding what to cook but useless once a recipe is already in your library. Some apps let me add notes to a recipe by hand, which means I could write 'CONTAINS PEANUTS' at the top of the satay if I remembered to, which I would not. One app, to its credit, parsed ingredient lists for common allergens and showed a small icon — but only on recipes I had imported from its own curated database, not on the four hundred recipes I had brought in from the rest of my life.

None of them did the thing I actually needed, which was: to be told, once, what my household cannot eat, and to have every recipe in my library — written, imported, scribbled, scaled, shared — flagged automatically, before I started cooking, every time. The work of remembering was being asked of the cook in every case. The software, even the good software, was a passive shelf.

§ III.What it looks like when the software notices.

I told Basil, once, in a single screen — household allergens — that my home avoids peanuts and shellfish. There was a small text field, a list of common allergens to tap, a free-text option for anything unusual. The whole interaction took perhaps twenty seconds. I closed the screen and forgot about it.

Two days later, I imported a Thai noodle recipe from a YouTube video — a single tap on the share sheet, a four-second pause while the app parsed it — and the recipe arrived in my library with a soft amber bar across the top of the card. Inside, the line that read 'two tablespoons crushed peanuts, for garnish' was highlighted in the same colour, with a small note beside it: contains peanuts (household allergen). I had not asked for this. I had not opened a settings panel. I had imported a recipe, and the recipe had been read, before I read it, by something that knew what my household could not eat.

The next week I imported a paella, scaled it from four portions to eight for a dinner party, and saw the same amber bar across the prawns line. I had not been thinking about shellfish. The app had been thinking about shellfish, in the background, the entire time. Marit's daughter was not coming to the paella. But the principle — that a household allergen, declared once, would be checked against every recipe forever — meant that on the night she did come, and on every subsequent night for the next ten years, the second pair of eyes would still be there.

§ IV.The deeper consequence.

What I noticed, in the weeks after I set the allergens up, was a small change in my own attention. The hum was still there — I do not believe the hum will ever entirely go away in a household with an allergic guest — but it had quieted. I read recipes, when I read them, with slightly more of myself available for the recipe itself. I caught myself, once, reading a long-form essay about Sicilian almond pesto and enjoying it, instead of skimming it for tree nuts. Tree nuts were not on my household list. The software had taken that watch off my shoulders.

The argument I want to leave you with is not really about Basil, or about any particular app. It is about the kind of work that software should be doing in a kitchen, and the kind it should not. Software should not be telling me what to cook, or rating my efforts out of five stars, or sending me a push notification at 5 p.m. asking what is for dinner. Software should be holding, quietly, the small dangerous facts that the cook cannot afford to forget — and surfacing them, gently, in the moment they matter. The cook stays the cook. The judgement stays human. The forgetting is, finally, no longer fatal.

It is a Saturday again. The apartment has been warm since four. The pot on the stove this evening contains, instead of peanuts, a careful sauce of cashew and lime, and beside it a small tray of rice. Marit will arrive in twenty minutes, with her daughter, who is now eight, and who will eat the dinner without anyone at the table thinking about what is in it. The thinking, this time, was done by something that does not get tired, and does not forget, and does not have a Saturday evening of its own to be distracted by. A jar of peanuts is at the back of my cupboard, where it will stay. The recipe knows. I no longer have to.