A municipal leaf-collection helper still has 2018 resident phone lists in the retrieval pile just in case. Which governance practice should retire that pile?
Select an answer to reveal the explanation.
Short Explanation
Think of 2018 resident phone lists still sitting in the retrieval pile just in case. A data lifecycle keeps only what this season needs, then deletes or archives. Infinite retention is not governance.
Full Explanation
2018 resident phone lists still sitting in the leaf-collection retrieval pile “just in case” violate data lifecycle governance for AI corpora. Keep only what the current season needs for routing and notices, then delete or archive according to written policy. Lifecycle covers collection purpose, permitted use, retention, and retirement so stale personally identifiable information does not remain indefinitely searchable by the helper.
Infinite retention by default fails by concept: AI piles are not exempt from retirement; “just in case” is not a lawful or safe retention rationale for old phone lists once the season and purpose have passed. Amazon Polly fails because speech synthesis does not delete 2018 numbers from an index or enforce retention. Raising temperature fails because sampling randomness does not remove documents from retrieval storage or change what the index contains.
Exam caveat: archival or legal holds may require keeping some records offline—document exceptions carefully; otherwise prefer deletion from the live retrieval corpus when the season no longer needs the numbers. Operational check: inventory the retrieval pile for pre-season phone lists, remove or archive 2018 entries per policy, re-index the leaf-collection store, and probe the helper to confirm those numbers no longer retrieve for public or staff queries.