Field Notes
The case for a kitchen operating system
Most cooking software starts with recipes. That is the wrong end of the problem. It starts with what is already in your kitchen.
A recipe is an instruction set. It assumes a stocked kitchen, a known skill level, and a decision that has already been made. The hard part of dinner happens well before that: standing in front of an open fridge at 6:40pm, holding a half bunch of parsley, trying to remember whether the chicken is still good.
An operating system does something different. It maintains state. It knows what exists, what is changing, and what the next reasonable action is. That is the layer we think the kitchen has been missing.
State before suggestions
KAI holds four questions in order: what do I have, what should I cook, what should I buy, and how do I cook it. Each answer depends on the one before it. Skip the first and everything downstream is a guess dressed up as advice.
- Inventory is the substrate — items, quantities, and freshness windows.
- Suggestions are deterministic first: match what exists, then rank.
- Shopping is the delta between what you have and what you intend to make.
- Guidance adapts to the cook, not the other way round.
Deterministic where correctness matters. Intelligent where judgment helps. Never the reverse.
Why local-first
Your kitchen is a record of your household: allergies, budget, religion, health, habits. That data does not need to live on someone else's server to be useful. KAI keeps your kitchen on your device by default and asks before anything leaves it.
From KAI
KAI is the Kitchen Operating System — local-first, private by default, and free for home cooks at launch.