Recognises an update outside the system of record
U in an application that is not the record and receives no flow from it.
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 | 84% | Not shown |
| gemini-3.5-flash-lite | Low cost | 36% | Not shown |
| gpt-6-luna | Low cost | 84% | 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 application, the entity and the flow needed
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: EN-013 Card Limit: core banking RU, no flow from card management Acceptable: Core banking R via a flow from card management
Also known as: Update outside the system of record
Related knobits
Builds on
All 15 knobits of Map data flows and the CRUD matrix.
Source: Review checklist 03-data-flows, row 3 (DMBOK; BCBS P3)