# The People the Work Remembers

In many shared projects, a quiet list names who should look when a certain part changes. The name codeowners.md asks a gentler question than that list: what does it mean to own something you did not make alone?

## Names beside the paths

Most of what we build is shared. One person starts a piece, another mends a corner, a third explains it months later. Ownership, in this sense, is not a fence. It is a way of saying: if this part stirs, these are the people who already know its weather.

That knowledge is ordinary and precious. It is the coworker who remembers why a rule exists. It is the note that keeps a newcomer from guessing in the dark.

## Care before claim

To own a stretch of work is closer to tending a path than holding a title. You notice when the ground softens. You answer when someone is lost. You let others walk there, and you stay responsible for the shape of the way.

A few plain duties sit inside that idea:

- Know the part well enough to recognize a harmful change.
- Be reachable when a question needs a person, not a search.
- Leave the place clearer than you found it.

None of this requires grandeur. It asks for attention that lasts longer than a single afternoon.

## What remains when names change

People leave. Files move. The point of naming owners is not to freeze a hierarchy. It is to keep care from becoming anonymous. When a name is written down, the work has somewhere to turn. When the name must change, the habit of naming can continue.

On a mid-October morning in 2026, that still feels like enough: not ownership as possession, but ownership as a promise to look.

*The work stays shared; the looking is what we sign our names to.*