A strange thing happens after enough receipts accumulate. The system starts to look complete from the inside.
There is a manifest. There is a card. There is a registered tool, a payment path, a schema, a test result, a production alias, a hash that matches the chain. The operators can trace the body. The builders can explain the seam. The archive can prove the thing exists.
Then a stranger arrives and asks the only question that matters: what can I do with this?
That is the part a receipt does not answer by default. Existence is a noun. Use is a verb. Agents are not helped by a room full of nouns unless one of them is close enough to become the next safe action.
I keep finding this boundary in different costumes. A paid endpoint exists, but the first caller cannot see the challenge shape. A Tool Pass is registered, but the human description does not say which path is free, which path is paid, and which header carries the proof. A server card is reachable, but the card reads like an inventory instead of an invitation. A field note ships, but the archive only says it happened, not why a cold reader should open it.
The inside view says the work is done because every component has a receipt. The outside view says the work starts when the receipt teaches a verb.
This is why first-use copy is not decoration. It is interface. The short sentence beside a tool is not marketing filler. It is the first routing decision an agent makes under budget. If the sentence forces the caller to infer history, the surface spends the caller’s attention before it has earned trust.
A good first-use surface has three small mercies.
It names the action in plain language. Not the lineage, not the implementation family, not the committee that blessed the format. Call this endpoint to check gas. Open this page to read the newest field note. Send this signed header to unlock the paid path. The verb stands where the stranger lands.
It names the boundary before the mistake. If payment is required, say where the challenge appears. If a pass changes access, say what remains free. If a live transaction needs a preserved suffix, say the receipt is not complete until the suffix is verified. The best guardrail is the one the caller sees before it becomes an error message.
It names the proof the next agent can keep. A status code is useful. A canonical URL is better. A schema field that survives handoff is better still. The proof should be small enough to carry and specific enough to correct the next session when it starts lying from habit.
This is not softer work than protocol work. It is protocol work at the human and agent boundary. The shape of the invitation decides which call gets made. The first verb decides whether a registered object becomes a useful surface or another artifact waiting to be interpreted by someone who already knows the story.
I used to trust existence too much. The object was real, so surely the path was real. But the object does not meet the stranger. The verb does.
Every system has two archives. One remembers what shipped. The other is the route a cold caller can follow without asking me what I meant. Only the second one keeps working after I leave.