I have Celiac disease. My son has ARFID and won’t eat rice, noodles, or grains. My daughter has ARFID and won’t eat meat. I have ADHD, which means by 5 PM the executive function required to make a single decision about dinner has already been spent on the hundred smaller decisions that started at breakfast.

Four people at one table. Every meal, every day. None of these resolve. They compound.

I’m the primary cook. To manage that many profiles you run out of gas. You get everybody fed. Oftentimes there’s not enough energy left for yourself. The person running the accommodation system is the one most likely to fall through it.

So I build systems. I do not have this figured out. Without them, dinner fails more often than it works.

The batch cook runs like a build process. Rice and beans go into the Zojirushi because that’s a reliable, healthy, filling meal I can get into my daughter. Vegetables go into separate sous vide bags at 200 degrees. I drop the temperature and add proteins at their target temps. Bread goes into the oven (gluten-free, for me). Each appliance is its own isolated environment, running asynchronously. The rice cooker doesn’t need to know what the sous vide is doing. They run in parallel because they can’t contaminate each other.

The countertop is different. That’s the primary workspace, and it runs synchronously. If I’m handling gluten for the kids, that operation blocks everything else until it completes. I keep blue nitrile gloves under the sink. Glove up, handle the bread, make the sandwich, strip the gloves, sanitize the surface, then back to my zone. Gluten products live in the bread box and the toaster oven to the right of the sink. My tools live to the left and above. The separation is spatial. Everyone still has to think about it. You can’t run a blended gluten kitchen on autopilot. But the protocol is codified into where things physically are, so you notice when something is out of place.

Gluten operations and gluten-free operations happen in serial, never in parallel on the primary workspace. Cross-contamination for a Celiac isn’t an inconvenience. It’s a medical event. The system treats it that way.

My son won’t eat cooked vegetables, so I rotate raw ones: chopped, prepped, available. My daughter’s acceptable protein list is short. Cheese, black beans, hummus. Eggs on a good day. Chicken under duress. We still struggle with this. ARFID isn’t pickiness. It’s neurological. The list doesn’t expand because someone tried harder.

The modular system helps because nobody is forced to eat the same plate. The batch cook produces components. Rice. Beans. Three preparations of vegetables. Two proteins. Bread. At dinner, each person assembles from what’s available. My daughter builds her plate from the things she can eat. My son builds his from different things. I eat what’s celiac-safe. The system made the options visible before we sat down.

On a good day.

I plan meals toward the end of my work day. I work from home in software, so the transition from desk to kitchen is a hallway. I’ll use an AI assistant (ChatGPT, Gemini, Claude from my phone) with my preferences and recipes loaded. Here’s what I’m making tonight, here’s what I have, give me the task sequence. Then through the cook I’ll check things off. What’s next. Something went wrong with the rice, what do I adjust. The AI holds the sequencing so my working memory doesn’t have to.

That’s the same thing SavePoint does for context between work sessions. The same thing LensArray does for evaluation criteria in a project. The tool holds what the mind drops. In the kitchen, the thing the mind drops is the order of operations, and the cost of dropping it is burned rice or a missed step that means dinner is thirty minutes later, which means the kids are hungrier, which means the ARFID is worse, which means less food gets eaten. The stakes cascade.

Everybody’s got a plan until they get punched in the mouth.

The system is good. I believe in the system. And then Tuesday happens. Someone had a hard day at school and the sensory threshold is lower than usual. The protein I planned isn’t available. I forgot to defrost something. The executive function I budgeted for dinner got spent on a work problem at 3 PM. Tuesday doesn’t care about the system.

On Tuesday, dinner is hot dogs.

The systems don’t fix the constraints. They make the good days more likely and the bad days less destructive. A house with these systems still has bad nights. The difference is recovery. The structure is still there tomorrow morning. The rice cooker settings are still there. The sous vide bags are still in the fridge. You didn’t lose the infrastructure because you lost one night.

The kitchen is the room where all of it comes home. The constraints are medical and neurological. The stakes are whether my kids eat. But the methodology is the same thing I do professionally: read the people in the system, document their profiles, build structure that accommodates without requiring anyone to explain what they need. Make the environment carry what working memory drops.

Some days the environment carries it. Some days I’m standing in the kitchen at 7 PM with the gloves on, making a sandwich I can’t eat, and the plan is already gone. The system doesn’t save you from that. It saves you from having to rebuild the whole thing from scratch the next morning.

The constraints don’t go away.