{
  "schema": "vedokrok.public-item.v1",
  "release_id": "VEDOKROK-SEL-5d86e1b23401e578",
  "url": "/knowledge/define-what-complete-means",
  "id": "MHC-D-RESEARCH-9721",
  "version": "0.1.0",
  "title": "Define what complete means",
  "summary": "96% of what?",
  "kind": "checklist",
  "body": "Name the records and fields required for the task, then define what counts as complete. Show the count that passed and the total checked: the numerator and denominator. State any exclusions before calculating the percentage.",
  "limits": [
    "A high completion score does not establish that populated values are correct."
  ],
  "topics": [
    "critical-thinking"
  ],
  "intents": [],
  "source_ids": [
    "gov-guidance",
    "gov-dims"
  ],
  "evidence": [
    {
      "claim": "Data quality assessment should use explicit rules tied to critical data and its intended use, choose metrics suited to each check, and communicate results with their strengths and limitations.",
      "source_id": "gov-guidance",
      "role": "supports",
      "note": "Claim limit: Official practical guidance, not experimental evidence for the effectiveness of this checklist. Showing the numerator, denominator and exclusions is the card’s practical adaptation, not a quoted mandatory standard.\nSource reading history: selected_passages; 2026-10-11; Data quality action planning steps 1–3 and 8; previously selected metadata and quality communication guidance. Official page was opened on 2026-10-10 and identified sections inspected. This verifies a narrow reference basis, not the effectiveness or completeness of independently drafted practice steps. On 2026-10-11 action-planning steps 1–3 and 8 were read again for card 9721; this is selected-passage screening, not independent review. On 2026-10-11 the Completeness communication section, action-planning step 7 and root-cause data-journey section were read again for the missingness correction; source screening only.\nAgent release review: PostgreSQL 18 table expressions, NULL comparisons and aggregates, the UK Government Data Quality Framework and Microsoft Power Query profiling documentation were checked at the cited sections. The original examples and scope limits remain attached.",
      "locator": "Data quality action planning, steps 1–3 and 8: critical fields, quality rules, metrics and reporting"
    },
    {
      "claim": "Completeness covers both the presence of expected records and the population of essential values within records; populated values may still be inaccurate.",
      "source_id": "gov-dims",
      "role": "supports",
      "note": "Claim limit: A framework definition, not a universal field list or proof that the adapted checks diagnose a particular migration failure. Required records and values depend on the task.\nSource reading history: selected_passages; 2026-10-11; Six dimensions and user needs; Completeness definition and distinction from accuracy. Official page was opened on 2026-10-10 and identified sections inspected. This verifies a narrow reference basis, not the effectiveness or completeness of independently drafted practice steps. On 2026-10-11 the Completeness definition and its distinction from accuracy were read again for cards 9721/9725; this is selected-passage screening, not independent review.\nAgent release review: PostgreSQL 18 table expressions, NULL comparisons and aggregates, the UK Government Data Quality Framework and Microsoft Power Query profiling documentation were checked at the cited sections. The original examples and scope limits remain attached.",
      "locator": "Data quality dimensions: Completeness, definition and distinction from accuracy"
    }
  ],
  "use_when": [
    "A dashboard says customer data is 96% complete."
  ],
  "avoid_when": [
    "A high completion score does not establish that populated values are correct."
  ],
  "checklist": [
    "Write the required population, fields and completion rule.",
    "Show counts beside the percentage, with exclusions and the assessment date."
  ],
  "example": "In this example, 180 of 200 invoiced customers have a required billing address: 90%. Another 300 prospects do not need one. Including them as missing addresses would produce 36% and answer a different question.",
  "check": "Another analyst can reproduce the metric from the definition and counts.",
  "published_at": "2026-11-12T18:37:40Z",
  "review": {
    "kind": "agent",
    "label": "Agent editorial and scoped source review",
    "reviewed_at": "2026-11-12T18:37:40Z"
  },
  "knowledge_origin": {
    "release_id": "MHC-RPUB-20261112-20287590",
    "corpus_commit": "20287590ddd3999b7492df232822b6a0f7d114b1",
    "manifest_sha256": "2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95",
    "projection_sha256": "2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0",
    "published_at": "2026-11-12T18:37:40Z"
  },
  "editorial_overlay": null,
  "editorial": null,
  "notices": [],
  "sources": [
    {
      "id": "gov-guidance",
      "title": "The Government Data Quality Framework: guidance",
      "url": "https://www.gov.uk/government/publications/the-government-data-quality-framework/the-government-data-quality-framework-guidance"
    },
    {
      "id": "gov-dims",
      "title": "The Government Data Quality Framework",
      "url": "https://www.gov.uk/government/publications/the-government-data-quality-framework/the-government-data-quality-framework"
    }
  ],
  "relations": [
    {
      "from": "MHC-D-RESEARCH-9721",
      "to": "MHC-D-RESEARCH-9723",
      "type": "useful_with",
      "url": "/knowledge/trace-missing-values"
    }
  ],
  "collections": [
    {
      "id": "RC-MHC-UNION-DATA-JOINS-QUALITY-DIAGNOSTICS-2026",
      "title": "Diagnose data joins and quality before trusting a report",
      "url": "/collections/diagnose-data-joins-and-quality-before-trusting-a-report"
    }
  ],
  "topic_hubs": [
    {
      "id": "critical-thinking",
      "title": "Critical thinking and evidence",
      "url": "/topics/critical-thinking"
    }
  ],
  "solution_packs": []
}
