# Replay examples before changing a data rule

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Replay examples before changing a data rule

ID: MHC-D-RESEARCH-9732 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/replay-examples-before-changing-a-data-rule

Stricter can still be wrong.

Knowledge source release: MHC-RPUB-20261112-20287590
Source corpus commit: 20287590ddd3999b7492df232822b6a0f7d114b1
Source manifest SHA-256: 2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95
Source projection SHA-256: 2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0

### Use when

- You change a data-quality rule after discovering errors or exceptions.

### Avoid when

- These cases support a regression check, not acceptance of the whole dataset. This is editorial testing practice; no optimal sample size or privacy guarantee is claimed.

### Explanation

Choose normal, erroneous and boundary cases. For each, record the intended accept/reject result and why it fits the agreed data requirements. Old pass/fail labels are comparison data, not the answer key. Run both rule versions on the same cases and explain every changed result.

### Steps

1. Use invented or redacted examples that preserve the condition under test. Retain only the fields needed; follow local handling rules if real records are necessary.
2. Keep both rule versions, expected results and reasons. Mark uncertain cases for review instead of guessing a label.

### Example

An agreed local code list permits ABC and ABCD. A three-letter-only check rejects ABCD but still accepts forbidden ZZZ. The examples expose both defects.

### Check

The intended errors are caught and justified valid cases remain accepted. Every changed result matches an agreed requirement or remains an explicit review item.

### Limits

- These cases support a regression check, not acceptance of the whole dataset. This is editorial testing practice; no optimal sample size or privacy guarantee is claimed.

### Evidence and sources

- supports: The issues framework recommends defining a data purpose, quality rules and targets before measuring performance, then prioritising below-target issues using purpose importance, failure impact and performance. — gov-rules. Claim limit: Practical prioritisation guidance, not evidence that its suggested scores or tolerances are universally optimal. Its date-range example is labelled accuracy; this source supports prioritisation here, not the validity/accuracy distinction set out in the companion guidance. Explicit denominators and regression examples are authored adaptations, not requirements established by this page.
Source reading history: selected_passages; 2026-10-11; Rules and purpose, importance/impact, targets and priority; 16 April 2026 update. 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 these prioritisation sections were read again. The date-range example uses accuracy where the companion guidance distinguishes validity; this limited source use does not adopt that example’s terminology.
Agent 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. (What data quality rules and issues are; Determine importance and impact; Set targets; Assign priority)
- supports: The action-plan guide advises keeping measurement criteria current, reviewing and refining assessment criteria, and comparing data quality before, during and after significant changes. — gov-action. Claim limit: Governance guidance, not experimental proof of this adapted regression procedure. Expected-case labels, synthetic/redacted cases and minimal retained fields are editorial testing choices; this source establishes no optimal sample size or privacy guarantee.
Source reading history: selected_passages; 2026-10-11; Steps 3–5 and 7: assessment, ownership, target timeframe/review date, cause investigation and monitoring; steps 2 and 7: current/refined criteria and before/during/after change comparison. 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 these sections were read again for the owned-action correction. No empirical effectiveness, independent or production acceptance is inferred. On 2026-10-11 steps 2 and 7, including Plan for and manage changes, were read for card 9732; its regression examples and data minimisation are authored practice, not empirical or privacy certification.
Agent 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. (Step 2: Identify data quality rules; Step 7: Repeat measure over time, Plan for and manage changes)
- gov-rules: Data quality issues framework — https://www.gov.uk/government/publications/implement-a-data-quality-action-plan/data-quality-issues-framework
- gov-action: Implementing a data quality action plan — https://www.gov.uk/government/publications/implement-a-data-quality-action-plan/data-quality-action-plan-implementation-guide

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
