Skilirium

Recognises a constraint deferred without a check

K-703 · Skill knobit · Activity: Derive data quality rules · Competence: Data modelling

A rule that should be a constraint but cannot be created yet because legacy rows violate it, and that has become nothing in the meantime. Deferral without a check is retirement nobody announced.

Can AI do this?

AI does this well Most of the tested AI models master this. 8 of 10 models master it.

ModelTierProbability of masteryStatus
gemini-4-argonFlagship 100%Mastered
gemini-3.1-pro-previewFlagship 84%Not shown
gpt-6-astraFlagship 100%Mastered
claude-fable-5-1Flagship 100%Mastered
gemini-3.8-flashMid tier 100%Mastered
gpt-6.1-solMid tier 100%Mastered
claude-sonnet-5-5Mid tier 100%Mastered
gemini-3.5-flash-liteLow cost 41%Not shown
gpt-6-lunaLow cost 100%Mastered
claude-haiku-5-5Low cost 100%Mastered

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 constraint and the check tracking it until created

How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: BR-007: each account has an IBAN; 3 % of migrated rows have none, so account_identifier was made nullable "for now"; no DQ rule, no date Acceptable: DQ-009 at threshold: "97%", a comment naming the repair work and the date the column becomes NOT NULL and the threshold 100 %

Also known as: Constraint deferred because the data already breaks it (data quality rule)

Related knobits

Builds on

All 31 knobits of Derive data quality rules.

Source: Review checklist 07-dq-rules, row 3; DMBOK2; Loshin 2011