At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Root manifest | Recalculate its root hash | Matching root or named error | The manifest must use a supported schema |
| Ordered archive parts | Recalculate part and content hashes | Verified parts or hash failures | Missing, changed, or reordered parts fail validation |
| Part summaries and records | Compare keys, ranges, chains, order, and counts | Structural validation result | Part, record, and byte limits apply |
| Reconstructed collections | Compare identities and content hash with the source archive | Import parity result | A valid package does not prove source correctness |
How it works
- Open Enterprise evidence workspace.
- Under Archive package, select the exported archive file.
- Select Import archive.
- Treat the completion message as action status only.
- Require a detailed result with valid status, no errors, and archive parity.
- Stop if any hash, count, identity, order, or schema check fails.
- Use Run verification only when checking the deposited baseline itself.
Example
An archive has three parts. The second and third parts are exchanged. Their bytes still exist, but their part numbers, ranges, chain, and manifest order no longer agree. Validation reports the mismatch. No isolated import result is accepted.
What this does not mean
The interactive file path validates the archive and reconstructs isolated collections without promotion. The current workspace does not render its detailed validation or parity result. A stored-manifest import uses a separate queued workflow. Archive validation does not certify compliance, prove source correctness, create legal WORM storage, or approve a release.
Related questions
Next step
Validate every exported archive before audit handoff, restoration, or incident review.
View on Atlassian Marketplace