Recognises an unmerge leaving downstream systems merged
Consumers keep the merged identity after an unmerge.
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 | 74% | Not shown |
| gemini-3.5-flash-lite | Low cost | 43% | Not shown |
| gpt-6-luna | Low cost | 74% | Not shown |
| claude-haiku-5-5 | Low cost | 74% | 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 downstream consumers to notify and correct
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: Unmerge in the hub only; CRM and AML screening keep the merged id Acceptable: Downstream consumers notified and corrected
Also known as: Unmerge leaving downstream merged
Related knobits
Builds on
All 14 knobits of Build golden records by survivorship.
Source: Review checklist 04-survivorship, row 5 (DMBOK)