# Plain Notes for a Shared Table

## What the name holds

recipes.md sounds like a shelf of instructions written so they can be read without fuss. A recipe is already plain speech: amounts, order, heat, and time. The ending reminds me that good directions do not need ornament. They need to be clear enough that a tired person on a weekday evening can follow them and still feel looked after.

## Attention, set down

Much of what makes a meal good never reaches the page. You learn the sound of onions when they soften, the give of dough under your palm, the moment a sauce stops looking thin. Still, the written recipe matters. It is where you keep what you do not want to lose: a proportion that always works, a swap for when the market is thin, a line that says wait longer if the kitchen is cold.

On a November evening the light leaves early. A short note can be enough to start the pot before the room goes fully dark. A recipe can hold, among other small things:

- a measurement you can trust when you are distracted
- a pause you might otherwise skip
- the name of the person who first showed you

## After the file is opened

A file can travel. Someone far away can open it, buy what they can find, and sit down to something that resembles what you meant. Their salt will differ. Their oven will run hot. Their table will have other chairs. That gap is not a failure. It is how a recipe stays alive, changed by the hands that use it and still recognizably itself.

I like thinking of this place as a quiet shelf rather than a stage. Here is one way. Try it. Change what you must. If it feeds someone, write the change back in so the next person starts a little closer to the meal.

*A clear instruction is a kind of welcome.*