Data Retention and Deletion Schedule Agent

A database of old customer records sits untouched for six years while the policy says three, because nobody owns deletion. This agent reads the retention policy and data inventory and finds datasets past their limit. It checks legal holds and dependencies, drafts deletion requests, and verifies after deletion that the data is gone and nothing broke. It records each decision, including skipped datasets and the reason, so an auditor can see what was kept and why. If a deletion appears to have worked but a backup or copy still holds the data, the agent reports it as unfinished. Edge case: a dataset past its limit is under a legal hold, so the agent skips it and records why. The data owner approves each deletion.