Recognises duplicate data requirements
Two requirements with the same statement. Two IDs will be traced, prioritised and tested separately, and will drift apart.
Can AI do this?
People still lead Few or none of the tested AI models showed they master this. 0 of 10 models master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 70% | Not shown |
| gemini-3.1-pro-preview | Flagship | 38% | Not shown |
| gpt-6-astra | Flagship | 38% | Not shown |
| claude-fable-5-1 | Flagship | 38% | Not shown |
| gemini-3.8-flash | Mid tier | 38% | Not shown |
| gpt-6.1-sol | Mid tier | 38% | Not shown |
| claude-sonnet-5-5 | Mid tier | 36% | Not shown |
| gemini-3.5-flash-lite | Low cost | 37% | Not shown |
| gpt-6-luna | Low cost | 39% | Not shown |
| claude-haiku-5-5 | Low cost | 37% | 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 duplicate pair and the one to retire
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: DR-006 and DR-007, both "Every payment must record the date on which the payment was instructed." Acceptable: Keep DR-006; set DR-007 to retired with superseded_by: DR-006.
Also known as: Duplicate (data requirement)
Related knobits
Builds on
Usually followed by
All 47 knobits of Capture data requirements.
Source: Review checklist 01-requirements, row 21; 29148 5.2.6 (consistent); REQ-010