Recognises a missing architecture stakeholder
A domain or regulatory reader in scope with no stakeholder; its questions will be discovered at sign-off.
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 | 83% | Not shown |
| gemini-3.5-flash-lite | Low cost | 83% | Not shown |
| gpt-6-luna | Low cost | 84% | Not shown |
| claude-haiku-5-5 | Low cost | 84% | 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 missing stakeholder
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: Payment data in scope; no Head of Payments among the stakeholders Acceptable: SH for the Payment data owner with their concerns
Also known as: Missing stakeholder
Related knobits
Builds on
All 17 knobits of Frame stakeholder concerns and architecture principles.
Source: Review checklist 01-concerns-principles, row 11 (42010; DMBOK)