Compare the declared artifact set
The synthetic copy check compares the declared source, first attempt, finding, corrected brief, and final record as separate artifacts.
Define the expected set first
An integrity check needs an explicit answer to “what should be here?” Record:
- each relative file name;
- its role in the job;
- its byte size;
- its content fingerprint;
- whether any omission was intentional.
Then calculate the same values from the copy. Missing, unexpected, and changed files should appear as separate outcomes.
Use inventory and provenance together
RFC 8493 describes BagIt inventories and checksums for file packages. W3C PROV-O explains relationships that give those files meaning. CommonMark supports readable Markdown artifacts within the set.
Integrity and meaning answer different questions. A fingerprint shows whether bytes changed. Provenance explains why the artifact belongs and how it relates to its neighbors.
Choose the right depth of checking
This method fits copies used for migration, sharing, backup, or later continuation. A quick count may be enough for disposable material, but consequential work needs content-level comparison.
Verification does not decide what should be stored. It tests whether the declared set and the observed set agree.
Complete the memory ring
Keep AI Work in Files You Control explains the parent ownership choice. Redact an AI Workspace Safely defines intentional omissions before a copy is made. Name AI Work Files by Role keeps the resulting inventory understandable.