# The Quiet Contract

## Three small parts of a name

The name api-docs.md is plain on purpose. One part is the doorway: a way for one piece of software to ask another for help, and to hear a clear answer. Another part is the writing that explains the knock. The last part is a humble file ending, a reminder that careful words do not need decoration to be useful. Together they suggest a simple idea. Help should be findable. A stranger should not have to guess.

## What we owe the person who arrives later

Most of the people who read these pages will never meet the person who wrote them. They arrive tired, mid-task, hoping the next sentence will save them an hour. That hope is a kind of trust. Meeting it does not require grand language. It asks for order, examples that match real life, and the honesty to say what will not work.

A good page does a few ordinary things well:
- It names the request in words a person can repeat.
- It shows what a kind answer looks like.
- It admits the edges, the limits, and the mistakes that are easy to make.

## Leaving the light on

I like to think of documentation as a lamp in a hallway. You may have already walked through. Someone else is still on the way, perhaps late on an October night in 2026, screen bright, question half-formed. The lamp does not solve their whole problem. It only says: you are not the first, and you do not have to start in the dark.

*A clear sentence is a small kindness left for someone you will never meet.*