Recognises a critical service depending on a data set outside the plan
A critical service names a data set the plan does not cover.
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 | 67% | Not shown |
| gemini-3.5-flash-lite | Low cost | 61% | Not shown |
| gpt-6-luna | Low cost | 61% | Not shown |
| claude-haiku-5-5 | Low cost | 67% | 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 service data set missing from the plan, and its fix or the question for its owner
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: CS-004 depends on DS-006, not in the plan Acceptable: DS-006 added with objectives
Also known as: Service depending on a data set not in the plan
Related knobits
Builds on
All 14 knobits of Plan backup, recovery and continuity.
Source: Review checklist 03-backup-recovery-continuity, row 8 (DORA Art. 11)