Recognises a capacity horizon shorter than the lead time
The capacity horizon ends before new capacity could be delivered, or well before the platform's life.
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 | 86% | Not shown |
| gemini-3.5-flash-lite | Low cost | 47% | Not shown |
| gpt-6-luna | Low cost | 83% | 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 defect named on the horizon shorter than procurement and platform life, and its fix or the question for its owner
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: horizon_years: 1; procurement lead time 9 months; platform life 5 years Acceptable: Horizon covering the platform's planned life, reviewed yearly
Also known as: Horizon shorter than the lead time
Related knobits
Builds on
All 15 knobits of Plan environments and capacity.
Source: Review checklist 02-environments-capacity, row 9 (ITIL)