Compliance Glossary for Confluence

What is a verifiable evidence archive?

A verifiable evidence archive is a deterministic package for one deposited baseline. Its manifest identifies the tenant, baseline, product release, coverage, section counts, ordered parts, content hash, and root hash. Its parts carry meanings, artifacts, usage, links, and conformance records. The import service recalculates hashes and counts before it reconstructs anything.

Last verified against production v6 · 24 October 2026

At a glance

InputActionOutputLimit
Deposited baseline collectionsSort stable record identities across five sectionsCanonical evidence streamEvery required section must be present
Bounded record groupsCreate ordered archive partsPart hash and chained part summaryPart, record, and byte limits apply
Archive metadata and part summariesCalculate the manifest root hashVersioned root manifestA matching hash does not prove source correctness
Archive packageRecalculate schema, tenant, order, count, key, chain, and hash checksValid result or named failure codesFailed validation blocks reconstruction
Workspace import messageReport the validation outcomeArchive validation failed: with error codes, or Archive verified: with the record countParity mismatch is reported as an error

How it works

  1. Open Terminology Baseline and find Enterprise evidence workspace.
  2. Select Run verification for the current enterprise freeze.
  3. Select Export archive. The server builds the archive in app storage.
  4. To validate a JSON archive package, select it under Archive package.
  5. Select Import archive.
  6. Read the result. A failed package lists its error codes. A valid package shows Archive verified: with the record count and confirmed parity.

Example

An evidence archive contains two ordered parts. A stored byte changes in the second part. The import service recalculates that part hash and the package hashes. The values no longer match the manifest, so validation fails. The workspace shows Archive validation failed: with the failing codes. The deposited baseline remains unchanged.

What this does not mean

Archive validation 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 current workspace cannot download an exported archive.

Related questions

Next step

Verify the deposited baseline before export. Do not treat a workspace completion message as archive verification.

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