# Reconcile what is missing and what should never have arrived

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

---

## Reconcile what is missing and what should never have arrived

ID: MHC-D-RESEARCH-0981 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/reconcile-what-is-missing-and-what-should-never-have-arrived

Everything expected can be present while the result is still wrong.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A source-to-target comparison reports no missing records, but the target may contain extras.

### Avoid when

- A target may legitimately contain records outside this run. Define scope before treating all unmatched target rows as defects.

### Explanation

Compare the expected and actual populations in both directions. Expected minus actual reveals omissions; actual minus expected reveals unexpected additions. Use the same identity definition and cutoff in both comparisons, then inspect duplicates separately when repeated occurrences matter.

### Steps

1. Freeze the expected population and the matching target scope.
2. Produce separate lists of missing and unexpected identities.
3. Compare occurrence counts or duplicate-sensitive rows when identity membership alone is insufficient.

### Example

All 80 intended partners arrived, but 12 unintended partners arrived too. A missing-only check would have declared success.

### Check

The reconciliation reports omissions, extras and relevant multiplicity differences, not one reassuring percentage.

### Limits

- A target may legitimately contain records outside this run. Define scope before treating all unmatched target rows as defects.

### Evidence and sources

- supports: EXCEPT returns rows in the first query but not the second, and removes duplicates unless ALL is specified. — RS-5EBA53046715516C. A one-direction difference cannot also identify unexpected target rows; distinct-set comparisons can hide repeated occurrences. (Section 7.4)
- RS-5EBA53046715516C: Combining Queries: UNION, INTERSECT, EXCEPT — https://www.postgresql.org/docs/current/queries-union.html

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/make-every-selected-record-end-in-an-explicit-status-bucket
