Thursday. Crohn’s flare since Tuesday. The celiac layered on top, which it does when the immune system is already busy fighting itself. I stood in the kitchen at 5:15 PM and the idea of cooking dinner from scratch was not possible. Not difficult. Not unpleasant. Not possible.

My daughter needed to eat in forty-five minutes. My son needed something completely different. Both of them needed real food, not cereal, not toast.

I opened the fridge. Three containers from Sunday: pulled chicken thighs, a pot of black beans, roasted sweet potatoes. A jar of the green sauce I make in bulk. Rice in the rice cooker from that morning (my son won’t touch it, but my daughter will). I pulled two plates. Assembly took twelve minutes. My daughter got beans, rice, green sauce, and shredded cheese. My son got chicken and sweet potatoes with butter. Both plates were food I’d actually cook on a good day. The only difference was that today I didn’t cook anything.

That’s fidelity. The output matched the intent even though the conditions were degraded.

I think about fidelity a lot in my professional work. In product design, fidelity is the question you ask after the designer stops touching the system. Does the brand still read correctly on page forty-seven of the marketing site? Does the component still work when a content author puts three paragraphs where the design assumed one? The system has to hold without the original hand on it. That’s what fidelity means.

In the kitchen, the hand that built the system is the same hand that operates it. But the person operating it on Thursday is not the same person who built it on Sunday. Sunday had energy, planning capacity, the ability to stand at a stove for two hours. Thursday had twelve minutes of standing before I needed to sit down.

Batch cooking is the governance layer. On a good day, I build the base components: proteins, starches, sauces, prepped vegetables. These are the infrastructure. During the week, the daily operation is assembly. Pull containers, combine, heat if needed, plate. The decisions were made on Sunday. Thursday only has to execute.

This is the same principle I applied at Encore for twelve years. Drift happens when the system asks too much of depleted people. When an enterprise platform requires a content author to make thirty typographic decisions per page, the typography drifts. When a kitchen requires the cook to plan, shop, prep, and execute a full meal every night, the meals drift. The solution in both cases is to move the decisions upstream. Build the governance structure when you have capacity. Let the daily operation run on what’s already been decided.

The fidelity test is simple. Did the family eat well on a day when I could barely stand?

Thursday, they did. The chicken was good. The beans were seasoned properly. The green sauce tied both plates together even though the plates had nothing else in common. Nobody ate cereal. Nobody went to bed hungry. The system held.

Some weeks it doesn’t. The batch cook gets skipped because Sunday was also a bad day. The containers run out by Wednesday and Thursday is back to zero. I haven’t solved that. The system has a single point of failure, and that point is whether I get one good day per week. Most weeks I do. Some weeks I don’t, and those weeks the fidelity breaks.

I’m not pretending this is airtight. I’m saying the structure makes the good weeks reliable and limits the damage on the bad ones. That’s what governance does. Predictability where it counts, and honest failure where it can’t reach.