Data Integrity Preservation

Preserve the accuracy, consistency, and traceability of data or records across their lifecycle.

The Diagnostic Story

Symptom: Different systems report different values for what should be the same record, and nobody can explain where the discrepancy came from or which version is current. Users compensate with spreadsheets, manual cross-checks, and screenshots because the official record is unreliable. Backups and logs exist but cannot establish a trusted state when an incident or dispute occurs.

Pivot: Define what trustworthy data state means for the context, identify the lifecycle boundaries where integrity breaks down, constrain authorized mutation paths, validate state and transitions, and preserve the provenance evidence needed to investigate and correct discrepancies.

Resolution: Decision-makers can tell which data is trusted, suspect, stale, or under repair. Corruption and unauthorized change are detected earlier and propagate less widely. Trust in records becomes inspectable and maintainable rather than assumed, and recovery after incidents restores trusted state rather than merely restoring bytes.

Reach for this when you hear…

[financial reconciliation] “The ledger and the sub-ledger disagree by forty thousand dollars and I cannot tell which one to trust or when they diverged.”

[clinical data management] “The patient record shows a contraindicated drug was never given, but the nursing note says it was — someone edited something without a trail.”

[data engineering] “The pipeline ran successfully but the output totals do not match the source, and without lineage I have no idea where the transformation went wrong.”

Mechanisms / Implementations

• Access Control Enforcement: Restricts who or what may read, write, approve, delete, or restore protected data, so records change only through authorized paths and never through hidden side doors.
• Audit Log: Keeps an append-only, attributable record of every action on protected data — who, when, and what changed — so integrity events can be investigated and reconstructed after the fact.
• Backup and Restore Verification: Proves that protected data can actually be restored and that the restored records still satisfy their integrity invariants — not merely that a backup file exists.
• Checksum or Hash Validation: Detects unintended alteration, transmission error, or corruption by comparing a freshly computed hash against a trusted reference value.
• Data Lineage Capture: Records how each value moved through sources, transformations, joins, and derivations, so a suspect output can be traced back to the upstream step that produced it.
• Data Validation Schema: Encodes the structure, types, allowed values, and cross-field rules a record must satisfy, rejecting malformed data at the boundary before it is trusted.
• Integrity Anomaly Monitoring: Watches trusted data for impossible values, unexpected drift, duplication spikes, missing records, or staleness, and raises a visible exception when something looks wrong.
• Reconciliation Workflow: Compares two records or states that should agree, classifies each discrepancy, and drives it to a repair, quarantine, or accepted-divergence decision that is recorded.
• Referential Integrity Constraint: Prevents a record from pointing to a nonexistent or invalid related record, so links between data never dangle.
• Source-of-Truth Registry: Documents, per field or claim, which system or role is authoritative — the reference that integrity checks and reconciliation consult to know which value should win.

▸ Show 1 more

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 (2)

• Data Integrity: Accuracy and consistency preserved.
• Invariance: Properties unchanged under transformation.

Also references 11 related abstractions

• Access Control: Restrict system access.
• Accountability: Responsibility for actions.
• Boundary: Defines system limits.
• Closure: Ensures operations remain within a set.
• Constraint: Limits possibilities to guide outcomes.
• Fault Tolerance: Continue operating under failure.
• Feedback: Outputs influence inputs.
• Observability: Infer internal state externally.
• Relation: Describes associations or dependencies.
• Transaction: All-or-nothing operations.

▸ Show 1 more

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Record Integrity Preservation · domain variant · recognized

Preserve the trustworthiness of official, legal, clinical, financial, administrative, or operational records across their lifecycle.

Provenance Integrity Preservation · implementation variant · recognized

Preserve trustworthy origin, authorship, transformation, and custody information for data or records.

Cross-System Consistency Preservation · scale variant · recognized

Preserve agreement among related records, states, ledgers, schemas, or reports distributed across systems or organizations.

Transactional Integrity Preservation · mechanism family variant · recognized

Preserve data integrity while related changes are written, committed, reversed, retried, or exposed to readers.

Recovery Integrity Preservation · risk or failure variant · candidate

Preserve or re-establish trusted data state after corruption, loss, unauthorized change, failed migration, or incident response.