Splits a record class by retention
Separate classes for record types with different retention, each under its activity
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 | 82% | Not shown |
| gemini-3.5-flash-lite | Low cost | 72% | Not shown |
| gpt-6-luna | Low cost | 82% | Not shown |
| claude-haiku-5-5 | Low cost | 82% | 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: Separate classes for record types with different retention, each under its activity
How it is assessed: Each resulting class can carry one retention rule
Related knobits
Builds on
All 14 knobits of Inventory the records and build the file plan.
Source: Graded on its own by dcm-file-plan