Load
Read both exports locally. Validate structure, headers and row widths.
Every result has
a defined meaning.
Migraven separates what the comparison observed from what a migration team must still determine. That distinction is the basis of a responsible review.
01 / EXECUTION SEQUENCEFive steps.
Five steps.
No hidden inference.
The engine follows a deterministic sequence. Invalid input or ambiguous keys stop the run rather than producing a misleading result.
Validate
Require a non-empty unique key in each dataset. Duplicate keys stop the comparison.
Index
Build sorted key indexes to pair records without relying on row order.
Compare
Compare each selected field using exact string equality and retain original row references.
Preserve
Write machine-readable findings, an offline report and a SHA-256 integrity manifest.
02 / RESULT VOCABULARYThree outcomes.
Three outcomes.
Carefully bounded.
The status describes the selected comparison only. It does not make a wider claim about migration quality.
Matched under the selected rule
The key exists on both sides and the selected field values are exactly equal.
Observed value difference
The key exists on both sides, but the selected values differ. Investigate before deciding whether it is a defect.
One-sided key
The key appears in only one export. The comparison cannot determine why it is absent from the other.
03 / INTEGRITY & PROVENANCEIntegrity is not
Integrity is not
authenticity.
The evidence helper records SHA-256 hashes and byte sizes for the source, target and generated comparison result.
SHA
256
256
What verification establishes
The verifier can detect whether the recorded files still match the hashes and sizes in the manifest.
What it does not establish
The manifest is unsigned. It does not prove who created the files, that the original exports were complete, or that a manifest and files were not all replaced together. Use trusted storage or an independent signature process where stronger provenance is required.
04 / REPRODUCIBILITYRun the bundled
Run the bundled
synthetic example.
Build the C17 engine, then run the demonstration to create comparison JSON, an offline HTML report and an evidence manifest.
cmake -S . -B build
cmake --build build
python tools/demo.pyOpen technical repository ↗