Recognises a purge trigger the data does not hold
The trigger field is not in the data set, so the date cannot be computed.
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 trigger field absent from the data set, and its fix or the question for its owner
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: PJ-002 uses relationship_end_date; DS-004 holds no such field Acceptable: The field added at source, or the trigger derived from a held field with the owner's agreement
Also known as: Trigger the data does not hold
Related knobits
Builds on
All 14 knobits of Implement retention, archiving and purge.
Source: Review checklist 04-retention-archiving, row 10 (15489)