Compliance Glossary for Confluence

What happens if an archive changes?

Archive validation fails when protected content changes. Compliance Glossary recalculates part hashes, content hashes, counts, order, chain links, tenant identity, and the root hash. Missing parts, changed evidence, reordered records, or tenant mismatches return distinct errors. Invalid evidence is not reconstructed as a valid imported package and cannot pass parity verification.

Last verified against production v6 · 26 September 2026

At a glance

InputActionOutputLimit
Changed evidence recordRecalculate part and content hashesPART_HASH_MISMATCH or CONTENT_HASH_MISMATCHHashes detect change. They do not prove original correctness.
Missing archive partCompare the package with the manifestPART_COUNT_MISMATCH and order errorsImport does not fill missing evidence.
Reordered parts or recordsCheck part numbers, ranges, chains, and record orderPART_ORDER_INVALID or RECORD_ORDER_INVALIDMatching counts alone are insufficient.
Archive from another tenantCompare tenant identity across the packageTENANT_MISMATCHCross-tenant evidence is rejected.
Reconstructed collectionsRecalculate content and root parityA pass or failed parity resultChanged reconstructed data cannot pass parity.

How it works

  1. Open Enterprise evidence workspace.
  2. Under Verification and portable evidence, choose the Archive package.
  3. Select Import archive.
  4. The app parses the package and validates its manifest and parts.
  5. Review the returned validation errors.
  6. Do not use a package with hash, count, order, chain, schema, or tenant errors.
  7. Confirm reconstructed content and root parity before any handoff.

Example

One stored term definition changes by one character after export. The part hash no longer matches. The flattened content hash also changes. Validation returns both failures. The package is not accepted as valid imported evidence. The administrator returns to the deposited source archive instead of presenting the altered package.

What this does not mean

Mutation detection proves whether protected archive content still matches its recorded hashes and structure. It does not prove that the original evidence was accurate. It does not create legal WORM storage. A valid package can still have known coverage gaps recorded in its manifest.

Related questions

What is a verifiable evidence archive?How do I verify an archive?How do I re-import an archive?

Next step

Validate every archive before import or external handoff. Stop when any integrity or tenant check fails.

View on Atlassian Marketplace
Verification basis: production v6 code, tests, manifest, and operations guidance. Verified 26 September 2026.