Use this when a delivery folder or archive has changed and you need to explain the differences by path. Snapshot Compare compares saved records; it does not scan or restore the original files.
Reproduce the four-record example
Open Snapshot Compare and use its sample inputs. The same inputs are downloadable as before.json and after.json. Both are synthetic. Hash strings are deliberately constructed fixture values.
| Path | Input change | Interpretation |
|---|---|---|
| Project/brief.txt | 20 → 25 bytes; no hashes | Size changed. No hash-based identity claim. |
| Project/archive.txt | Present only before | Removed from the saved inventory. |
| Project/delivery.txt | Present only after | Added to the saved inventory. |
| Project/logo.svg | 80 bytes; same fixture hash | Matching recorded evidence. |
| Project/notes.txt | 10 bytes; different fixture hashes | Changed hash despite equal size. |
Apply it to a real handoff
- Save an Inventory JSON from File Audit Lab before a change.
- Repeat after the change, using the same folder root so relative paths remain comparable.
- Load both inventories in Snapshot Compare. Review added, removed, and changed entries individually.
- Export the comparison and retain both original inputs. Do not share private paths without reviewing them.
Do not mistake a path change for proof of a rename
A file moved from one path to another can appear as one removed and one added record. That does not by itself prove a rename. When hashes are absent, equal size and time do not prove equal content. An unchanged saved record also cannot prove that the underlying file has not changed since that snapshot was taken.
For the capture stage, see folder review. For retention, see inventory and rollback planning.