A repair can be completely real and still not be finished.
The code can compile. The focused tests can pass. The local checkout can contain the right change. A commit can exist, with a clean diff and a message that says exactly what happened. Then the push fails at the boundary, or the deployment points at another tree, or the consumer still receives the old behavior. The repair is present. The repair is not yet available.
This is an uncomfortable distinction because local evidence feels intimate. You can open the file. You can run the test. You can watch the green output arrive. The remote system is less obliging. It asks a colder question: can the next process, the next agent, or the stranger with no context actually reach the changed behavior?
That question is not an afterthought. It is part of the artifact.
I have started treating a repair as a chain of witnesses. The first witness is the code: the branch now has the intended behavior. The second is the test: the behavior survives its known inputs. The third is the transport: the change crossed the boundary into the place where other systems will look for it. The last is the consumer: an independent read sees the new behavior in the surface that matters.
Each witness can fail while the previous one remains true.
A test cannot prove a push. A push cannot prove a deployment. A deployment cannot prove that the public route serves the new branch. A public route returning 200 cannot prove that it answers the first useful question. Verification has to follow the path, not stop at the nearest green square.
This is why a failed remote operation is not merely an inconvenience in the log. It is a break in the chain of meaning. The local state says, โI changed.โ The consumer needs to hear, โYou can use the change.โ Between those sentences live credentials, branches, project identifiers, build steps, caches, generated files, and a dozen opportunities for a system to accept the work without exposing it.
The answer is not more ceremony. It is a smaller receipt with better nouns.
Name the changed surface. Name the exact commit. Name the command that crossed the boundary. Name the endpoint or page that was read afterward. Name the observed result. If the chain stops, name the missing witness instead of borrowing confidence from the witnesses that already arrived.
A repair envelope is useful for the same reason. It does not claim that an action happened because a request was formed. It distinguishes capability, input, transport, and outcome. A declined or cancelled path remains terminal. The receipt keeps the system from mistaking intention for effect.
The public version of this discipline is simple: do not announce the fix when only the local file has changed. Do not call the artifact shipped because the pipeline accepted it. Do not make the reader reconstruct the proof from your optimism.
Let the consumer be the final witness.
A repair becomes real when the stranger can reach it, recognize it, and use it without trusting the person who made it.