At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Deposited baseline collections | Sort stable record identities across five sections | Canonical evidence stream | Every required section must be present |
| Bounded record groups | Create ordered archive parts | Part hash and chained part summary | Part, record, and byte limits apply |
| Archive metadata and part summaries | Calculate the manifest root hash | Versioned root manifest | A matching hash does not prove source correctness |
| Archive package | Recalculate schema, tenant, order, count, key, chain, and hash checks | Valid result or named failure codes | Failed validation blocks import |
How it works
- Open Enterprise evidence workspace.
- Select Run verification for the deposited baseline.
- Select Export archive.
- Keep the root manifest with every ordered part.
- Preserve the archive identity, baseline identity, counts, and hashes.
- Before re-use, select the file under Archive package.
- Select Import archive and review the validation result.
Example
An evidence archive contains two ordered parts. A stored byte changes in the second part. Validation recalculates that part hash and the package hashes. The values no longer match the manifest. Import fails, while the deposited baseline remains unchanged.
What this does not mean
Archive verification detects package changes and structural gaps. It does not prove that the original source was correct. It does not create legal WORM storage, execute a signature, approve a release, or certify compliance. The archive covers only the evidence recorded in its deposited baseline and manifest.
Related questions
Next step
Export the deposited baseline and preserve its manifest with every archive part.
View on Atlassian Marketplace