Recognises a forward dependency in a roadmap
A package depends on a package in a later state, or the dependencies form a cycle.
Can AI do this?
AI does this well Most of the tested AI models master this. 3 of 4 models in the current benchmark master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 96% | Mastered |
| gemini-3.5-flash-lite | Low cost | 38% | Not shown |
| gpt-6-luna | Low cost | 95% | Mastered |
| claude-haiku-5-5 | Low cost | 95% | 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 dependency and its fix
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: WP-002 (TS-1) depends on WP-005 (TS-2) Acceptable: WP-002 moved to TS-2, or the dependency removed
Also known as: Dependency pointing forward
Related knobits
Builds on
All 14 knobits of Sequence the implementation roadmap.
Source: Review checklist 05-roadmap, row 1 (TOGAF)