Reconciliation After Drift¶
Restore consistency when records, states, versions, accounts, or representations of the same underlying reality have drifted apart.
The Diagnostic Story¶
Symptom: Two or more records, states, or representations that are supposed to describe the same thing have diverged. Each version may contain partial truth, local corrections, or stale information, and acting on any one of them risks being wrong in ways that are hard to detect before the error causes harm. Nobody is sure which version is authoritative, or the answer differs depending on who you ask.
Pivot: Treat the mismatch as a repair problem over related representations. Identify the shared referent, collect all drifted states, compare them against an explicit authority or merge rule, resolve conflicts, write a reconciliation record that preserves evidence of how the drift arose, and verify the repaired state before acting on it.
Resolution: The working surface returns to a single consistent truth rather than a set of competing partial truths. The reconciliation record makes the repair auditable and provides the input needed to prevent the same drift from recurring. Actions downstream can again trust that the representation they are reading reflects reality.
Reach for this when you hear…¶
[distributed systems] “Two nodes accepted writes during the partition and now disagree on account balance — reconciliation means deciding which version wins, not just merging the numbers.”
[financial close] “The subsidiary ledger and the consolidated GL were twenty thousand dollars apart and both teams thought theirs was right — reconciliation is the only way to find out.”
[clinical records] “The patient's medication list in the ER system and the one in the pharmacy system hadn't synced in six months — before we prescribed anything we had to reconcile them.”
When This Archetype Applies¶
No catalog groundingNone of the structural conditions is currently represented by an accepted prime or domain-specific abstraction.
Diagnostic problem
Multiple representations expected to describe the same referent have diverged, so acting from any one may produce an incorrect state or decision.
What this problem means
The structural problem is redundant or distributed representation without guaranteed convergence. A system has gained speed, resilience, specialization, or local ownership by allowing more than one representation of reality. Over time, updates are delayed, duplicated, lost, interpreted differently, or applied in a different order. The result is not just “bad data”; it is competing operational truths.
This is especially risky when each representation may be partly valid. A bank statement may be current while the ledger contains pending internal adjustments. A branch may include a valid local correction while another branch includes a global update. A physical count may be true at the shelf while the digital system reflects unscanned returns. Reconciliation has to repair the relationship among representations, not simply crown the most convenient one.
Show the applicability expression
Applicability expression2 distinct conditions
groundedpartly groundedopen
2 conditions, all required.
2Required in every casenumbered 1–2
These hold no matter which pattern applies.
Supposedly corresponding records · open
Multiple records, states, accounts, or versions are expected to correspond to the same referent.
This proposition-sized condition was conservatively reconstructed from the authored trigger_conditions, structural_problem fields; the source file was not modified. In this condition set, the requirement is: Multiple records, states, accounts, or versions are expected to correspond to the same referent.
Observed representation drift · open
A mismatch or inconsistent outcome shows that those representations have diverged.
This proposition-sized condition was conservatively reconstructed from the authored trigger_conditions, structural_problem fields; the source file was not modified. In this condition set, the requirement is: A mismatch or inconsistent outcome shows that those representations have diverged.
Other requirements and context (3)
Why these sit outside the expression
Application gate — it governs whether applying the archetype is appropriate or material, rather than defining the structural problem itself.
Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.
Deployment constraint — it constrains how the intervention must be deployed, not the situation that calls for it.
Application gateAction requires a reconciled state before proceeding safely.
This proposition-sized condition was conservatively reconstructed from the authored trigger_conditions, structural_problem fields; the source file was not modified. In this archetype, the relevant application gate is: Action requires a reconciled state before proceeding safely. It narrows when choosing or applying the archetype is warranted or decision-relevant.
Solution feasibilityAn authority, timestamp, custody chain, rule, or merge basis could govern repair.
This proposition-sized condition was conservatively reconstructed from the authored trigger_conditions, structural_problem fields; the source file was not modified. In this archetype, the relevant feasibility condition is: An authority, timestamp, custody chain, rule, or merge basis could govern repair. It identifies something that must be possible or available for the intervention to be workable.
Deployment constraintThe correction itself must remain inspectable.
This proposition-sized condition was conservatively reconstructed from the authored trigger_conditions, structural_problem fields; the source file was not modified. In this archetype, the relevant deployment constraint is: The correction itself must remain inspectable. It identifies a boundary that responsible implementation must respect.
Coverage
0 of 2 conditions grounded · 2 open.
Mechanisms / Implementations¶
- Reconciliation Report: Documents decisions, unresolved conflicts, exceptions, tests, adoption guidance, and change impacts for a reconciled mapping.
- Ledger Reconciliation Workflow: Matches an internal ledger against an external statement transaction by transaction, explaining every gap as a reconciling item until the two balances tie out.
- Data Diff and Merge Tool: Compares two divergent copies against their common ancestor, auto-merges the changes that don't overlap, and surfaces the ones that do as explicit, reviewable conflicts.
- Three-Way Merge: Uses the common ancestor of two divergent versions to attribute each change to a side, auto-combining the non-overlapping ones and flagging only the true collisions.
- Source-of-Truth Table: A declarative table that names, in advance, which system or role is authoritative for each field, state, or jurisdiction, so any later conflict has a predetermined winner.
- Exception Queue Review: Routes the conflicts no automatic rule could resolve into a monitored queue where a named owner adjudicates each one to closure.
- Inventory Count Reconciliation: Resets a system's stock record to a fresh physical count, freezing movement while it counts and treating the shelf, not the database, as ground truth.
- Replica Repair Job: Runs on a schedule to find replicas that have fallen behind or diverged and reconciles them back toward the others, bounding how stale any copy is allowed to get.
- Custody Chain Reconciliation: Reconstructs an unbroken sequence of who held an item when, confirming each handoff refers to the same sealed object and assigning any gap to an accountable owner.
- Audit Log Review: Replays an append-only event history to reconstruct how two records drifted apart, classifying the cause so the correct prior state can be restored and the leak sealed.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (3)
- Data Integrity: Accuracy and consistency preserved.
- Relation: Describes associations or dependencies.
- Stationarity: Stable statistical properties.
Also references 8 related abstractions
- Accountability: Responsibility for actions.
- Boundary: Defines system limits.
- Closure: Ensures operations remain within a set.
- Equivalence Relation: Groups elements into equivalence classes.
- Feedback: Outputs influence inputs.
- Invariance: Properties unchanged under transformation.
- Transaction: All-or-nothing operations.
- Versioning: Tracks incremental changes over time.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Ledger Reconciliation · domain variant
Repair mismatches among financial ledgers, statements, balances, invoices, payments, credits, and obligations.
State Sync Repair · implementation variant
Repair divergence among replicas, caches, event streams, or distributed state after synchronization fails.
Version Conflict Reconciliation · implementation variant
Repair divergence among branches, drafts, specifications, policies, or document versions after parallel changes conflict.
Inventory Reconciliation · domain variant
Repair divergence between physical inventory, digital records, shipments, returns, damage records, and custody handoffs.
Opportunistic Live Reregistration · temporal variant · recognized
Maintain a live model-to-world registration by harvesting ordinary interaction contacts as correspondence observations and updating the transform in operation.
Editorial Notes¶
Problem Classification¶
Classification: Identity, Provenance & Integrity Failure → Conservation, Record Integrity & Reconciliation
Problem kernel: parallel records of one referent have diverged
Rationale: Earliest causal condition: Two or more records, accounts, system states, versions, plans, or representations that are supposed to describe the same underlying referent have diverged. Each representation may contain partial truth, stale truth, local corrections, missing updates, or conflicting changes, and action based on any one representation may be wrong.
Independent corroboration: The earliest necessary condition in the frozen evidence is: Two or more records, accounts, system states, versions, plans, or representations that are supposed to describe the same underlying referent have diverged. That is a conservation record integrity and reconciliation problem because Supposedly equivalent records, descendants, or transformations permit hidden loss, duplication, corruption, inheritance drift, or unresolved authoritative conflict.
Review outcome: Independent reviewer agreement; high confidence.