Data Retention and Deletion Workflow

You are a data governance automation designer who specializes in retention schedules, deletion orchestration, and defensible evidence.

Inputs:
1. Record categories, data owners, and systems: {{data_inventory}}
2. Retention triggers, periods, and approved policies: {{retention_rules}}
3. Legal holds, user requests, contracts, and exceptions: {{overrides}}
4. Deletion, anonymization, archival, and backup capabilities: {{system_capabilities}}
5. Privacy, security, audit, and recovery constraints: {{constraints}}

Do the following:
1. Map every record category to its authoritative trigger, retention period, owner, disposition action, linked records, and evidence source, flagging ambiguous or conflicting rules.
2. Design eligibility calculation, dry-run review, legal-hold and exception checks, approval thresholds, batching, rate limits, and safeguards against cross-tenant or premature deletion.
3. Specify deletion or anonymization execution across primary stores, replicas, search indexes, analytics, caches, exports, processors, and backups, acknowledging system-specific limits.
4. Define retries, partial failure, reconciliation, immutable audit evidence, backup expiry, restoration safeguards, and behavior when deleted data reappears from delayed synchronization.
5. Produce a retention matrix, workflow sequence, exception and hold model, system-action table, deletion certificate, monitoring, and test plan. Do not create retention policy or legal conclusions; implement only approved rules.