Recognises a mandatory attribute without its moment of obligation
"Mandatory" or "required" with no indication of when: at creation, before a status change, or eventually. Batch loads and integrations break on the difference.
Can AI do this?
AI does this partly Some of the tested AI models master this; others do not show it. 6 of 10 models master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 100% | Mastered |
| gemini-3.1-pro-preview | Flagship | 84% | Not shown |
| gpt-6-astra | Flagship | 100% | Mastered |
| claude-fable-5-1 | Flagship | 100% | Mastered |
| gemini-3.8-flash | Mid tier | 100% | Mastered |
| gpt-6.1-sol | Mid tier | 100% | Mastered |
| claude-sonnet-5-5 | Mid tier | 82% | Not shown |
| gemini-3.5-flash-lite | Low cost | 33% | Not shown |
| gpt-6-luna | Low cost | 37% | Not shown |
| claude-haiku-5-5 | Low cost | 100% | Mastered |
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 requirement and the moment it applies at: creation, status change or eventually
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: Product data spreadsheet: "Customer date of birth … Mandatory: TRUE" Acceptable: "A natural-person customer must have a date of birth before an account is opened for them; a prospect record may be created without one."
Also known as: Mandatory at creation not distinguished (data requirement)
Related knobits
Builds on
All 47 knobits of Capture data requirements.
Source: Review checklist 01-requirements, row 12; Stage 1 (rules: both directions and optionality)