# Names on the Door

## What the address suggests

The name codeowners.md is plain on purpose. It points to a habit many teams already keep: a short list of who looks after which part of the work. Read slowly, it asks something larger. If code can have owners, what kind of owning is worth having? Not a fence, and not a trophy. A name that means someone can be found.

## Owning as staying

The useful kind is not a claim staked in the ground. It is staying close enough to notice. You remember why a line was written. You can say, in ordinary words, what would break if it changed. When someone is stuck, they know whose attention to borrow.

That kind of ownership shows up in small ways:
- A note left where a future reader will actually find it.
- A reply that arrives before the question grows cold.
- A clean handoff when you step away, so the work is never an orphan.

None of this needs a grand speech. It needs a person who does not hide behind the work, and who treats a shared place as something that can be worn out by neglect.

## A promise small enough to keep

October 25, 2026 is an ordinary day, and ordinary days are when shared work either holds or frays. A list of names will not write the code. It can still keep a room from going dark. Someone is willing to be found. Someone will say, this part is in my care, and I will not leave it nameless.

*To own a piece of shared work is simply to leave a light where others can see your name.*