SYSE.29:4.5 - Give retirement an explicit scope

Before ending the old provision, give each remaining supported use an actual disposition: qualified transfer, continued bounded support, an available outside result, or an authorized end of reliance with its consequences understood. State the consequences of that disposition for the affected users, retained state, rights and support obligations. Do not present an unresolved disposition as migration success.

Separate cessation of new requests, removal of a served interface, deletion of resources, retention of records and loss of the ability to interpret those records. They can require different actions and permissions. Retaining an export file is insufficient if the needed content, identity or receiving reader is lost.

Update the user-facing entry and support information when the actual availability changes. Remove obsolete access or resources only under the applicable authority and retention conditions. If retirement is justified despite residual uncertainty, state the exact accepted exposure and response; do not claim that zero users or zero obligations was proved.

Return the bounded decision, any completed increment, and any next work or premise still needed. Retirement is not implied by a date, a disabled button or a period of zero traffic.