What Your Cook Actually Needs to Know That You Forgot to Say

Ask any household admin what their cook knows and they'll describe the recipes. Ask what their cook needs to know and the list gets longer and stranger, fast: which nights the in-laws come and expect a certain dish, that the youngest has a walnut allergy but will eat almonds, that Thursday is always lighter because everyone eats out, that the good rice is in the second cupboard and the everyday rice is in the first, and mixing them up caused an actual argument once.

None of this lives in a recipe. It lives in the admin's head, gets repeated verbally every few weeks, and evaporates completely the day the cook changes.

Try this exercise. Set a timer for ten minutes and write down everything your cook currently knows that isn't written anywhere. Not recipes. Context. A few prompts to get started:

• Who has an allergy, a dislike, or a religious dietary rule, and what happens if it's missed.
• Which days have guests as a default, and who those guests usually are.
• What "the good version" of a staple looks like versus the everyday version. The rice cupboard problem is not unique to one household.
• What happens automatically without being asked. Does the cook already know Friday means a bigger lunch, or does someone have to say it every single Friday.
• What the cook has quietly changed or improved on their own, that nobody ever formally approved, but everyone now depends on.

Most households get to twenty or thirty items in ten minutes. That's twenty or thirty things currently living in one person's memory, with no backup, that a new cook would have to learn the hard way, one mistake at a time.

This is the actual argument for building a real household knowledge base instead of a mental one. Not because your current cook is doing anything wrong. Because everything they've learned about your house should survive them, the way it would in any well-run kitchen that isn't one person's memory. In Paz, that context gets captured as it comes up, in conversation, and it's there for whoever needs it next.