Recognises a retention trigger missing from the metadata
A schedule trigger with no element or link carrying its date.
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 | 83% | Not shown |
| gemini-3.5-flash-lite | Low cost | 85% | Not shown |
| gpt-6-luna | Low cost | 58% | Not shown |
| claude-haiku-5-5 | Low cost | 83% | 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 trigger and the element it needs
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: RR-001 needs relationship end date; no element Acceptable: ME-012 relationship_end_date, inherited from CRM
Also known as: No element for a retention trigger
Related knobits
Builds on
Usually followed by
All 15 knobits of Define the content metadata schema.
Source: Review checklist 03-content-metadata, row 2 (23081-1; 15489 9.9)