Recognises a copy outliving its source
Backups or replicas kept longer than the data's own retention.
Can AI do this?
AI does this well Most of the tested AI models master this. 3 of 4 models in the current benchmark master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 91% | Mastered |
| gemini-3.5-flash-lite | Low cost | 88% | Not shown |
| gpt-6-luna | Low cost | 91% | Mastered |
| claude-haiku-5-5 | Low cost | 91% | Mastered |
Mastered means a probability of at least 90% that the model has this knobit, estimated from its graded answers. “Not shown” means the answers do not settle it either way. How the models are tested.
What it looks like in practice
Expected result: The defect named on the backup or replica kept beyond the source's retention, and its fix or the question for its owner
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: CP-001 core banking backups kept 15 years; RR-001 ends 10 years after the relationship Acceptable: Backup retention well inside the source's, or covered by the purge
Also known as: Copy outliving its source
Related knobits
Builds on
All 14 knobits of Implement retention, archiving and purge.
Source: Review checklist 04-retention-archiving, row 5 (GDPR Art. 5(1)(e))