# Who Answers for the Path

Every shared project grows paths. Some are walked every day. Others narrow until only one person remembers where they lead. A list of code owners is a way of saying, before anyone is lost: if you need this stretch, here is who still knows it.

## Not a fence

The word owner can sound like a gate. In practice it is closer to a name on a garden bed. The soil is common. The watering is not. Someone has agreed to notice when the leaves droop, to remember which corner floods after rain, and to tell the next person before they plant in the wrong place.

That agreement is small and serious. It does not grant permission to shut others out. It grants a duty to be reachable.

## What gets written down

A good list is short enough to trust. It does not try to describe the whole landscape. It only marks the places where a question should land on a person, not vanish into a crowd.

What belongs on it:
- the part of the work
- the person who will look
- a way to find them while the question is still fresh

Anything more starts to look like a monument. The point is use, not display.

## The ordinary Tuesday

Today is 27 October 2026. Nothing about the date makes the work more dramatic. Systems still break on quiet days. The value of a named keeper is exactly that quiet: someone has already said yes, so the rest of us do not have to hunt for a witness after the fact.

Care, written in plain lines, outlasts the meeting where it was promised.

*Responsibility is just a name left where the path might otherwise go dark.*