SYSE.29:1 - Problem frame

Use this pattern when a supported provision is changing or disappearing and users, retained state, dependencies or support promises still rely on it. Start by finding the affected uses and what must remain obtainable or transferable. Compare them with the proposed receiving path before announcing that migration is complete.

The first result is a bounded migration or retirement decision with an executable next increment, or an explanation of what prevents it. Name any missing consumer information, permission, compatibility result or recovery result. The subject is the change of actual supported use, not merely a new version name or a removal date.

Use SYSE.27 when the old/new interface meaning is still undecided. A private unused prototype with no retained state or external obligation does not need this migration Method. A live provision cannot be treated as that prototype merely because recent traffic is zero.