Recognises a retention period set outside the schedule
A period with no source in the records schedule.
Can AI do this?
Not settled yet The benchmark tested this, but the models' answers do not settle yet whether they master it. 0 of 4 models in the current benchmark master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 75% | Not shown |
| gemini-3.5-flash-lite | Low cost | 75% | Not shown |
| gpt-6-luna | Low cost | 75% | Not shown |
| claude-haiku-5-5 | Low cost | 75% | Not shown |
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 period with no source in the records schedule, and its fix or the question for its owner
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: RR-004 card authorisation logs, P2Y, source: null Acceptable: Taken from the schedule, or raised with the records manager
Also known as: Retention period set here
Related knobits
Builds on
All 14 knobits of Implement retention, archiving and purge.
Source: Review checklist 04-retention-archiving, row 8 (15489)