Technical file fingerprinting, comparison and ORI/MOD/UNVERIFIED classification based on hashes and evidence rather than filename alone.
How it works — step by step
- 1
Load a binary or supported HEX, S-record or ZIP container.
- 2
Validate structure and generate stable hashes for trusted-evidence comparison.
- 3
Inspect matching/changed regions and the proposed ORI, MOD or UNVERIFIED class.
- 4
Approve classification only when the displayed evidence supports it.
- 5
Export hashes, file relationship, decision and complete audit history.
Key capabilities
- SHA-256 and server evidence
- HEX, S-record and ZIP
- Restore verified MOD only
- Reports and history
Result, scope and responsible validation
Every stage remains tied to the relevant account, licence, file or tenant. Source material and history are retained, uncertain cases never receive an invented result, and the output must pass the validation required for the specific program, integration or workshop process.
