# The Names Beside the Work

## Who answers

A shared project is a house with many doors. Most days you never meet the people who keep it standing. You only notice that a light still works, a loose step has been fixed, and someone already knows which window leaks in the rain. A list of code owners is that kind of map. It does not crown a founder. It names the person who will pick up when something breaks.

Ownership, in this sense, is less a claim than a habit of noticing.

## Care without ceremony

To look after a stretch of code is closer to tending a garden bed than holding a deed. You learn where the soil stays wet, which corner needs more light, and which old patch should be left alone. You leave a note so the next person does not have to learn the same lesson the hard way.

The stewards worth trusting tend to be plain about it:

- They read before they change anything.
- They explain the odd corner instead of guarding it.
- They say when they will be away, and who can stand in.

None of this needs a speech. It needs a name that can be reached, and a person willing to be interrupted.

## What the name is for

The address sounds technical, almost clerical. Under it sits an older hope: that work lasts longer when someone agrees to be found. Not famous, and not solely in charge. Simply willing. A name turns a pile of decisions into a place with a keeper.

On a short October day, that feels like enough. You do not have to finish the whole field. You only need to know which rows are yours, and to leave the path a little easier to follow.

*Being named is a small promise to stay reachable.*