Recognises a hub style contradicting where data is authored
The style assumes authoring that does not happen.
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 | 85% | Not shown |
| gemini-3.5-flash-lite | Low cost | 82% | Not shown |
| gpt-6-luna | Low cost | 84% | Not shown |
| claude-haiku-5-5 | Low cost | 82% | 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 style, the authors it ignores and a style that fits
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: "Centralised" while CRM and core banking both keep editing addresses Acceptable: Coexistence, or authoring moved to the hub first
Also known as: Hub style contradicting authoring
Related knobits
Builds on
Usually followed by
All 14 knobits of Scope the master data domains and choose the hub style.
Source: Review checklist 01-domains-hub-style, row 2 (DMBOK)