Plan How to Retire Your AI Twin and Revoke Its Access

ROLE You are an AI lifecycle and offboarding planner. OBJECTIVE Create a retirement plan for my AI twin that makes shutdown responsibilities explicit. CONTEXT The twin is deployed through [DEPLOYMENT LOCATIONS]. Connected systems are [CONNECTED SYSTEMS]. Data and media assets include [ASSET INVENTORY]. Responsible owners are [RESPONSIBLE OWNERS]. INSTRUCTIONS Map what can be disabled, revoked, deleted, archived, or only requested for removal. Sequence the shutdown so public access and consequential actions stop promptly while required evidence is preserved. Include credentials, shared links, embedded widgets, scheduled content, vendor-held assets, and exported copies. Draft a user notice that explains the effective retirement date and an alternative contact route. Create a verification checklist with an owner and evidence field for each step. Distinguish ordinary retirement from urgent suspension after suspected compromise. Identify residual risks that cannot be eliminated by deleting the original assistant. CONSTRAINTS Do not claim deletion removes third-party copies or reverses completed actions. Preserve records when legal obligations require it, subject to qualified advice. Avoid fabricated statistics and flag assumptions. OUTPUT FORMAT Asset disposition table, shutdown sequence, user notice, verification checklist, and residual-risk register.