Six-forty in the morning. Four burners going. Rice cooker on the counter behind me, steam curling up toward the hood vent. I have a sheet pan of chicken thighs coming out of the oven in three minutes, a pot of GF penne at rolling boil, a skillet of regular linguine one burner over, and two different sauce bases reducing on the back. My son needs plain chicken with barbecue sauce on the side, not touching anything. My daughter will eat the pasta but only if the sauce isn’t “weird,” which rules out about half of what I make. My wife has her own constraints. I have celiac and Crohn’s, so cross-contamination isn’t a preference issue. It’s a medical one.

This is breakfast and lunch prep for the day. It takes about ninety minutes. Then the work starts.

Both of my kids have ARFID (avoidant/restrictive food intake disorder), which means their relationship to food is governed by texture, smell, temperature, and appearance in ways that don’t bend to persuasion or exposure therapy on any useful timeline. You can’t negotiate with it. You design around it.

My wife and I mapped this out over years, mostly through failure. We found four cuisine frameworks the family can tolerate across different configurations: Italian, Mexican, American BBQ, and French. Not every person eats every cuisine. But between those four, we can construct enough variety that nobody is eating the same three meals on rotation forever.

The cooking itself runs on a three-layer model, whether or not I had that language for it at the time.

The first layer is the group body. A protein, a starch, a sauce base, cooked in volume. Sunday I might do five pounds of pulled pork, a large pot of rice, and two sauce bases (a red and a cream). That batch is the raw material for the week. It doesn’t belong to any single meal yet.

The second layer is what I think of as the persona: the cuisine framework applied to that base. The same pulled pork becomes carnitas with lime and cilantro, or gets a Memphis rub and goes on slider buns, or folds into a ragu over pasta. Same protein, different room.

The third layer is individual accommodation. My plate gets the gluten-free version. My son gets his portion separated before any sauce touches it. My daughter gets the pasta but with the sauce she approved last Thursday (not the new one I tried). My wife’s plate accounts for her needs. Four people, four assemblies, from the same base.

This is the Selector operating in a kitchen. Modernist technique plus mapped cuisines gives me the crate. The constraints are fixed. The combinations inside those constraints are where the design lives.

I want to be honest about this: I absolutely cannot frame it as though I have this figured out. It is messy and it is ongoing. There are weeks where the batch cooking falls apart because I am in a flare and standing for ninety minutes at the stove is not happening. There are dinners that get rejected across the board and we end up at frozen pizza (GF for me, regular for everyone else, and even that requires two separate oven runs). The system does not fix the constraints. The constraints are permanent.

What the system does is make good days more likely and bad days less destructive. When I batch on Sunday and the week cooperates, Monday through Wednesday run almost on autopilot. When I am depleted, the frozen portions from last week’s batch are already portioned and labeled. The governance is against low-spoon days. The structure exists precisely because the maker cannot always be present to improvise.

Doing this, giving it a name, treating it as a formalized system even before I had that language, changed how I thought about every other design problem I touched. If you can run a three-layer model at six in the morning with a flare and two kids who will not eat what you made, you can run it anywhere.