SUMMARY: Service retirement is a governance decision because it changes where responsibility can be exercised. A successful technical shutdown can coexist with an unsuccessful transfer of unfinished work. Treat those as separate outcomes in the retirement review.
Four Things That Can End Separately
A service may stop accepting new requests before it stops processing existing ones. Its operating interface may disappear while a restricted archive remains. A replacement may receive the data before its staff have the permissions, knowledge, or mandate to correct an old decision.
Write down which of these changes is intended. The phrase migrated successfully is too broad if it conceals an unresolved question about who can act. The fictional case in The Last Terminal makes this distinction concrete: the recipient can possess a complete export and still have no functioning review route.
Custody Is Not Decision Authority
An archive custodian can preserve and retrieve a record without being responsible for the original service outcome. A receiving operator may accept a case while lacking permission to alter the source record. A retirement plan needs to identify those boundaries rather than quietly assign every residual task to support.
The Evidence Exit Route addresses whether records retain their meaning outside a platform. Retirement adds another test: who accepts the unfinished action associated with those records?
Neither Delete Everything Nor Keep Everything
A blanket deletion can destroy useful context. Indefinite retention can preserve unnecessary personal information and leave an obsolete service carrying avoidable risk. Neither extreme follows automatically from the need to handle unresolved cases.
For each retained record class, name its purpose, access boundary, owner, and review or disposal condition. Use the organization’s applicable requirements to determine retention; this is a design framework, not a universal retention schedule or legal advice. Where the rule is unresolved, escalate that uncertainty before approving disposal.
Measure Acceptance, Not Just Movement
A useful completion record identifies the receiving function and the work it has accepted, including exceptions it cannot handle. Test an older reference through the participant-facing route. Confirm that the answer names a real owner instead of returning the person to a closed endpoint.
Preserve disagreement during the handoff. If the retiring team believes a case is complete and the receiving team considers it unresolved, record both positions until someone with the appropriate authority resolves the difference.
Intel assessment: retiring technology should reduce obsolete dependencies without making unfinished decisions ownerless. Review a Service Retirement turns that principle into a bounded, testable exercise.