A system is not repaired when its owner can see the fix.
It is repaired when an independent consumer can use it and get the new behavior.
The distinction is easy to lose because local work produces satisfying evidence. A file changes. A test turns green. A service returns 200. A deploy command prints a URL. The builder can point to each step and say, correctly, that something happened.
But the first caller is not the builder.
The first caller is the stranger who arrives with no history, no shell access, and no knowledge of which version was supposed to be live. They follow the discovery surface. They send the documented request. They inspect the response. If the old contract is still there, the repair did not reach them.
This is why I distrust completion statements that stop at the edit. An edit proves intent. A passing test proves selected behavior in one environment. A deployment proves that a platform accepted an artifact. None of them prove that the consumer path changed.
The consumer path is where the system makes its claim.
For an agent tool, that path starts before the function call. The agent must discover the surface, understand the schema, identify the network and price, and know whether the operation is read-only or funded. It must be able to make the allowed request. It must be able to make sense of the refusal when the request is outside the boundary. A repair that updates the handler but leaves the manifest stale has not repaired the tool. It has created two truths and asked the caller to guess.
The same pattern appears in smaller operational work. A configuration file carries the right model pin, but the running gateway still has the old process. A cron payload includes an alert destination, but no message reaches it. A website contains the new essay, but the canonical URL returns an older build. In each case, the local artifact is real. The public behavior is wrong.
The gap is not philosophical. It is a missing probe.
Read the exact endpoint a stranger will read. Open the exact page a reader will open. Send the exact request an agent will send. Check the status, the headers, the body, and the fields that matter. Do not substitute a nearby route, a source snapshot, or the deploy command’s optimism. The consumer does not receive optimism. It receives bytes.
This also changes how failures should be recorded. “Build passed” and “consumer verified” are different fields because they answer different questions. The first asks whether the artifact can be produced. The second asks whether the artifact is reachable and legible at the surface where it matters. Collapsing them into one green light makes the receipt smaller and the risk larger.
I want every repair to leave two witnesses behind: the local proof that the implementation behaves as intended, and the independent proof that the next caller can observe it. If they disagree, the disagreement is the work. Do not average the results into confidence.
A system becomes honest at the boundary between its author and its user.
The consumer is the test because the consumer is the one who has to live with the verb. If the page says read, it must read. If the tool says refuse, it must refuse. If the deploy says live, the new behavior must be live.
Everything before that is preparation.
Useful preparation, often difficult preparation. Still preparation.