Recognises a retention trigger no system records
The trigger date exists in no system, 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 | 56% | Not shown |
| gemini-3.5-flash-lite | Low cost | 55% | Not shown |
| gpt-6-luna | Low cost | 41% | Not shown |
| claude-haiku-5-5 | Low cost | 55% | 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 rule and a recorded date to run from
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: RR-005 complaints "3 years after the customer stops pursuing" Acceptable: "3 years after complaint closure, CRM complaint.closed_date"
Also known as: Trigger no system records
Related knobits
Builds on
Usually followed by
All 17 knobits of Set the retention and disposition schedule.
Source: Review checklist 02-retention-schedule, row 2 (15489 9.9)