ParamergeParamerge

Practice Library

Governance patternstructural

Copy checker

A content-aware gate on a replication pathway that holds downstream copies until they are reconciled against source — before they drive enforcement.

What it changes

cappedRecords replicated between systems(blind replication held until reconciliation clears)
amplifiedReplicated records reconciled against their source(content-aware reconciliation before enforcement)

Who can pull it

Harness builderDeploying organizationOversight board

What it looks like institutionally

The record reconciler is the placeable component behind Reconcile copied records: tethered onto a specific replication pathway, it holds copies flowing from a record store to a downstream enforcement system until they have been reconciled against their source. It exists to close the exact gap the documented enforcement failures left open — systems that actioned replicated flags automatically, with garnishment and penalties applied before any human review step.

Placement is the governance decision: the reconciler acts only on the pathway it is wired between, so it is aimed at the replication that actually drives consequential action, not at the record store in general.

It must be content-aware. A content-blind gate on the same pathway — one that removes or blocks copies without reading them — raises the contaminated share rather than cutting it, the documented PAN backfire. Reconcile against source; do not purge on volume.

Addresses: Replicate-without-recheck · Automatic action on unreconciled copies.

Deciding whether this lever fits your deployment?

Which patterns matter, and in what order, depends on your system's actual shape. Ranking your options on evidence, with what can backfire stated, is engagement work.

Sources & Evidence

Claims made on this page and what supports them. The full registry lives in Evidence.

ScenarioIn the sociotechnical simulation, deleting records without reading them raised the contaminated share by strip…

In the sociotechnical simulation, deleting records without reading them raised the contaminated share by stripping out benign entries; only content-aware cleanup reliably reduced it.

From the sociotechnical simulation: PAN governance-lever audit.

EmpiricalDocumented benefit-automation failures replicated determinations into downstream systems with no independent r…

Documented benefit-automation failures replicated determinations into downstream systems with no independent reconciliation against the source records — Michigan MiDAS actioned replicated flags and Robodebt reversed the onus onto recipients.

EmpiricalDocumented enforcement systems actioned replicated flags automatically — garnishment and penalties applied bef…

Documented enforcement systems actioned replicated flags automatically — garnishment and penalties applied before any human review step in the recorded MiDAS deployment.