Recognises parallel changes to one system of record
Two packages change the same subject area's record in the same state with no dependency.
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 | 57% | Not shown |
| gemini-3.5-flash-lite | Low cost | 53% | Not shown |
| gpt-6-luna | Low cost | 59% | Not shown |
| claude-haiku-5-5 | Low cost | 59% | 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 packages and their ordering or owner
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: WP-008 (CRM capture) and WP-009 (branch screens in core banking) both change Party in TS-1 Acceptable: WP-009 depends on WP-008, or one owner for both
Also known as: Parallel changes to one system of record
Related knobits
Builds on
All 14 knobits of Sequence the implementation roadmap.
Source: Review checklist 05-roadmap, row 6 (TOGAF)