Recognises an uncovered identity requirement
For a significant thing, nothing says how the business tells one from another, who assigns the identifier, whether it can change, and whether it can be reused. Reused identifiers silently corrupt history.
Can AI do this?
People still lead Few or none of the tested AI models showed they master this. 1 of 10 models master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 91% | Mastered |
| gemini-3.1-pro-preview | Flagship | 33% | Not shown |
| gpt-6-astra | Flagship | 82% | Not shown |
| claude-fable-5-1 | Flagship | 83% | Not shown |
| gemini-3.8-flash | Mid tier | 34% | Not shown |
| gpt-6.1-sol | Mid tier | 79% | Not shown |
| claude-sonnet-5-5 | Mid tier | 80% | Not shown |
| gemini-3.5-flash-lite | Low cost | 35% | Not shown |
| gpt-6-luna | Low cost | 34% | Not shown |
| claude-haiku-5-5 | Low cost | 32% | 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 thing and its missing identifier, assigner, change and reuse rules
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: Account requirements that never say whether an account number can be reused after the account is closed Acceptable: "An account is identified by its IBAN, assigned by the bank at opening; it does not change and is not reused after the account is closed." (with source)
Also known as: Identity not covered (data requirement)
Related knobits
Builds on
All 47 knobits of Capture data requirements.
Source: Review checklist 01-requirements, row 27; Stage 1 (identity)