8. After completion

An undertaking ends while its result continues

People can use, depend on and question a result long after the undertaking that produced it ends. A library edition, an installed application or an issued calculation can remain in use after the producing undertaking ends. If people confuse the undertaking with its result, maintenance becomes hard to describe.

One error treats each later improvement as evidence that the earlier work was never complete. The accepted result goes back to an earlier percentage position, and its whole basis becomes a candidate for repeated examination. The opposite error treats completion as the end of responsibility, so a recipient's consequential finding has no owner. Between these errors lies a quieter failure. Current sources move on while users stay uncertain about what changed since the edition they adopted.

An acceptance remains an actual historical decision about an identified subject, evidence and limitations. It is not a guarantee that the assessment was infallible. Later evidence can show that an earlier completion claim was wrong, that a commitment was not fulfilled, or that a result people relied on needs correction or withdrawal. The record of the decision can stay while the present assessment changes.

Anyone can raise such a finding and its evidence. The decision to revise acceptance, restrict authorized use or withdraw a release belongs to whoever holds the relevant acceptance or release authority. A new need is different. It does not become an unfulfilled old commitment merely because it is now important.

The phrase “after 100%” is useful only when this distinction stays intact. It identifies work after people have considered an undertaking complete. It does not mean that every possible use was qualified, or that the product has no further room for change. A completed result can stay adequate for its selected use while a later undertaking develops something further.

Different findings, different consequences

A defect is a failure to meet a commitment that applies to the accepted subject. A repair can keep the commitment and change the implementation. The finding also raises a question about past or continuing reliance, because someone can depend on behavior that the edition does not provide. Those who hold the relevant authority consider that consequence when deciding whether notice, correction, restricted use or withdrawal is warranted. A merged repair does not by itself answer the recipient's question.

A recipient can also show that the result meets its stated commitments but is unfit for the use that those commitments were meant to serve. This is a validation gap. The examination may have established conformity accurately, while the chosen criteria missed something consequential about the purpose. The finding goes back to the people responsible for the commitments and the intended use. It can warrant a revised basis, a changed permitted use or further examination.

Passing checks alone cannot resolve such a gap. And not every later preference shows one. What matters is how the finding relates to the original intended activity, and what evidence shows that the result is inadequate.

An implementation refinement can improve the means without a change to the promised behavior. A factual clarification can improve the explanation without a change to what the product did. Both can be small, but neither is automatically harmless. A person can rely on an explanation to decide whether an operation is suitable. A changed implementation can affect a consumer whose assumptions were not recorded locally.

A changed environment or dependency gives another possibility. The source can stay identical while the operating system, the input range or a supporting component changes. Earlier evidence can remain an accurate account of its subject without establishing the new use. The maintenance question then concerns how the retained result relates to the changed circumstances. It is not necessarily a question of an original defect.

A new priority or a requested capability can change the intended result itself. Its authority comes from a current undertaking or an applicable standing grant, not from the earlier acceptance of a product. Some of this work is an ordinary bounded extension. Other work changes the product's commitments enough to need a revised basis. A full definition exercise for every repair is no more adequate than treating every extension as maintenance that is already authorized.

One report can contain several of these meanings. A misleading behavior can expose a product defect, a poor explanation and an examination method that missed a class of failure. A product repair addresses one consequence, and reflection on the shared practice addresses another. These distinctions help people understand the report. They are not an exhaustive classification that every finding must pass through.

The reach of a later change

A change can be local in how it is made and wide in its effects. One validator condition can change which inputs the validator accepts from many consumers. A substantial explanatory revision can leave all their adopted instructions untouched. Examination follows the changed claim, the relationships it affects and the consequences of error. It does not follow the age of the product or the number of edited lines.

The account of evidence reuse in chapter 6 applies here too. A repaired interface can warrant focused regression and consumer checks without a repeat of an unrelated product qualification. When the subject of each check stays explicit, people can understand both the reuse of evidence and the need for new verification.

A published edition keeps its identity while maintained sources continue to develop. A correction can appear as an identified successor with a meaningful account of the change. It need not silently replace the bytes that earlier evidence and decisions named. A consumer can then assess the consequences and keep its own basis for current reliance.

This separation also means that a merged source repair is not necessarily delivered. The recipient can use an older package, a copied instruction or a product that embeds a selected library revision. Publication and adoption connect the changed result to those actual uses. Whether accumulated changes warrant another edition is a decision about their usefulness, their risk and their intended recipients. A calendar interval or a count of commits can prompt that decision but cannot make it.

Current descriptions matter between releases. A sentence can mislead a reader when it presents development material as part of a published edition. An old statement that an approval is still pending can also mislead. History can keep the sequence. But a person should not have to reconstruct that history only to identify what a current statement refers to.

Continuing ownership without endless work

The participants in a later undertaking can differ from those who produced the original result. Continuity depends on the maintained project's responsibilities, recoverable source, evidence and limitations. It also depends on the actual arrangements with recipients. It does not need one agent session to stay alive indefinitely, or a comprehensive registry of every possible consumer.

Each later piece of work still needs a clear purpose, authority and a usable result. A request and a focused examination can be enough. An adopted support obligation can itself authorize and require responses. Its scope matters, just as the scope of a new assignment does. Without such an obligation, an old improvement idea does not become an active task.

A maintained product can also reach the end of its maintained life. Retirement concerns which work and support will continue, how existing reliance is treated and which source stays recoverable. Retirement need not erase earlier editions, and recovery need not reactivate development. Where known reliance or an adopted arrangement continues, its consequence deserves explicit treatment. An assumption that silence ended the relationship is not such treatment.

So maintenance lets completion stay meaningful without making the result immune to further understanding. The work can end. Responsibility and later inquiry take the forms that the actual product, commitments and people warrant.