A recipe is a procedure. A recipe with a name attached — Aunt Nadia's lentils, Grandpa Cal's Sunday eggs, the chicken Mom only made when she was apologizing — is a person you can eat. That distinction is the entire game.
Most families lose their recipes not because the food gets bad but because the food gets anonymous. The dish that was once Aunt Nadia's becomes "the lentils" within one generation, becomes "those lentils we used to have" within two, and disappears entirely within three. Strip the name and you strip the connective tissue. What survives is a vague memory of legumes.
The fix is dumb-simple and almost nobody does it. Write the name in the title of the recipe. Not "Lentil Soup." "Aunt Nadia's Lentils, Aleppo, 1962." Every time the recipe gets handed off, the name travels. Every time the soup gets ladled, the name gets said. Within ten years your kids cannot eat lentils without thinking about a woman they may have never met but somehow know.
The reason this matters is that taste is the most underrated memory medium in the family-memory toolkit. A photo activates one sense. A story activates none directly. A recipe activates five — smell, taste, texture, sound of the pan, sight of the steam — and locks the memory in the limbic system harder than any other channel available to a parent. You can forget your grandmother's face. You will not forget her bread. That is a neurological fact, not a sentimentality.
The naming convention does another job that is less obvious. It forces the cook to credit the source. A family that habitually credits its cooks builds a quiet ledger of who taught whom, which is the same as a ledger of who loved whom. Your daughter, ladling out Aunt Nadia's lentils for her own children thirty years from now, is performing a public acknowledgment that her people did not invent themselves. They were taught. They are the result of being taught. This is humility transmitted through a stockpot, and there is no faster way to teach a kid where they come from than to let them spell out a name they did not previously know while serving themselves dinner.
There is also a quality-control benefit worth noting. Named recipes get protected. A nameless lentil soup will be casually adjusted, swapped out for a faster version, abandoned when the family discovers Instant Pots. A recipe with a name gets the original treatment — the cook will make Aunt Nadia's lentils the way Aunt Nadia made them, even when it is inconvenient, because messing with the recipe feels like messing with the person. The name is a preservation forcing function.
The work is not hard. Open whatever you keep recipes in. Rename three of them right now with the person who taught you, the place, and the rough decade. If you cannot remember the person, ask. If the person is dead, ask anyone who is still alive who might know. If nobody knows, name it after the place where you first ate it. The point is to refuse anonymity. The point is to insist that food has a lineage, that you are not a free-floating eater but a node in a network of cooks, most of whom are now bones.
There is a related move which is to invent new named recipes on purpose. Most parents wait for their kids to inherit recipes. Smarter parents mint them. The pancake recipe you have made every Saturday for nine years is already an heirloom in production. Call it something. Tell your kids it is yours. Tell them you got the trick of the buttermilk from a diner in Saskatoon in 2011. They will pass that detail on. The pancake will outlive you. Your name will travel inside it for a hundred years if anyone bothers.
The food industry runs in the opposite direction. It wants recipes nameless and brandable, attached to companies instead of people. The household kitchen is one of the last places where the old credit system can survive. Use it. The lentils are easy. The lineage is the actual meal.