SYSE.29:5 - Archetypal Grounding

A separate constructed software example concerns three consumers of preview-environment recipe v1. Two use it daily; the third is a quarterly recovery exercise. Recipe v2 is available for the ordinary service class, and the provider wants to stop maintaining v1.

Thirty days of request logs show no use by the recovery consumer. Inspection of the actual recovery configuration nevertheless finds a pinned v1 dependency and retained environment metadata in v1’s format. “No recent requests” therefore does not close that use.

The first increment moves one daily consumer. Its request identifies the same service artifact, synthetic data and acceptance question on v2. A constructed trial returns the expected configured environment and successful connection test. In the adverse trial, creation times out after allocating resources; the operator identifies the partial environment before repair. The next action reconciles its configuration or returns to the still-supported v1 route under the tested conditions. It does not create another environment blindly.

The other daily consumer then moves under the same qualified conditions. Retirement still stops at the recovery consumer: its restoration procedure has not been exercised on v2, and old metadata must remain interpretable. A working ordinary preview is not that missing recovery result.

Two continuations are possible. If a bounded recovery exercise and metadata-reading check establish the needed result on v2, the holder can decide the final move and end v1 under the actual support conditions. If they fail, the result is continued bounded v1 support, a different receiving arrangement or an explicitly authorized end of that recovery promise—not “all users migrated.” A retained decoder or qualified conversion may remain necessary after the old request endpoint stops serving.

The decision records which continuation obtains.

For a physical inspection or machining path, exit also requires transferable tooling, programs, relevant rights and a provider capable of producing the required result. Sending a drawing does not qualify the receiving setup. Reverting the old program cannot restore material already removed from a component; recovery may require segregation, inspection, rework or replacement under the applicable engineering decision.

What changes in practice is the stopping condition: migration ends when the declared receiving uses and remaining obligations have actual dispositions, not when the new interface is announced.