Keep the missing link visible.
Original source and extraction hash history is incomplete. Later hashes cannot reconstruct evidence that was never retained.
A clean check.
A precise boundary.
Consistency of the bytes available today cannot recreate evidence that was never retained.
Provenance
Consistent bytes. Incomplete history.
Explore what each part of the available evidence can establish.
Nage-reported backfill: 7,230 chunks, zero mismatches across three environments. This is not three independent organisations or uninterrupted historical proof.
What was reported
7,230 chunks. Zero mismatches. Three environments.
Backfilled consistency
Mac and Railway used the same hashlib implementation; PostgreSQL used pgcrypto. Three environments do not mean three independent algorithms.
Original history
Original source and extraction hash history is incomplete. The original bytes and extraction path cannot be inferred from a later content hash.
Migration 043
Migration 043 addresses future rows. Historical original-byte backfill remains a separate task.
audit.py request hash
The raw UTF-8 request-payload hashing path remains open and is distinct from the three closed signed-record defects.
Reviewer question
Which bytes were hashed, and when?
A matching identifier proves less than a complete historical chain of custody. Ask when the identifier was created and which earlier evidence remains available.