Diagnose a digest mismatch after an analytical export

Understand the likely causes

• Possible causes include selecting a derivative instead of the source, changed newline bytes, a different text encoding, added export metadata, truncation, an incorrect algorithm, or an unexplained change. Visual equality does not establish byte equality. Conversely, an intentional derivative should normally have its own identity rather than be expected to match the original digest.

Confirm the exact comparison boundary

Identify whether each digest covers original bytes, a selected range, decoded text re-encoded by an application, or an exported table. Check the algorithm and the expected value’s documented source. Do not use a filename alone to establish identity. Keep all actions within the approved material and avoid reopening a real device or contacting a service to resolve a classroom mismatch. This guide works entirely with author-created strings. In a real approved process, preserve original observations and document any correction rather than silently replacing the old expected value.

Test a specific transformation hypothesis locally

The example demonstrates an explicitly declared newline change. Both source and export remain available, their original digests differ, and a derived normalization matches. This supports that transformation for these known bytes only. It does not prove that an unknown real mismatch has the same explanation. Compare lengths and exact differing byte ranges, then relate the difference to the actual export settings and method record where authorized. Avoid trying many undocumented normalizations until one produces equality; that would hide meaningful distinctions and make the conclusion difficult to reproduce.

import hashlib
source = b"case=lab-4\r\nstate=created\r\n"
export = b"case=lab-4\nstate=created\n"
digest = lambda value: hashlib.sha256(value).hexdigest()
assert digest(source) != digest(export)
derivative = source.replace(b"\r\n", b"\n")
assert derivative == export
assert source.count(b"\r\n") == 2
print("declared newline derivative matches; original digests differ")

declared newline derivative matches; original digests differ

Repair the record association or preserve an unexplained difference

If the comparison used the wrong object, correct the association with a visible record of what was mistaken. If a documented transformation explains the change, assign the output a derivative id and record input, method, parameters, and output digest. If the difference remains unexplained, retain both objects and the limitation; do not relabel the new value as the expected original. A legitimate export change and an unexplained source change require different responses. Keep any real incident or handling decision with the accountable organization’s approved process.

Keep it from recurring

• Keep raw source objects immutable within the analytical workflow, label derivatives, and bind expected digests to exact identities and algorithms. Record export encoding and newline settings. Require an explained review for reference updates so a convenient new digest cannot erase an unexpected change.