At a glance
| Input | Service check | Error code | Limit |
|---|---|---|---|
| Changed evidence record | Recalculate part and content hashes | PART_HASH_MISMATCH, PART_CONTENT_HASH_MISMATCH, or CONTENT_HASH_MISMATCH | Hashes detect change. They do not prove original correctness. |
| Missing archive part | Compare the parts with the manifest | PART_COUNT_MISMATCH | Import does not fill missing evidence. |
| Reordered parts or records | Check part numbers, ranges, chains, and record order | PART_ORDER_INVALID, PART_RANGE_INVALID, PART_CHAIN_MISMATCH, or RECORD_ORDER_INVALID | Matching counts alone are insufficient. |
| Changed manifest | Recalculate the root hash and section counts | ROOT_HASH_MISMATCH or SECTION_COUNTS_MISMATCH | The manifest must use a supported schema version. |
| Archive from another tenant | Compare tenant identity across the package | TENANT_MISMATCH | Cross-tenant evidence is rejected. |
| Workspace message | Report the validation outcome | Archive validation failed: with the codes above | A valid package shows Archive verified: with its record count and confirmed parity. |
How it works
- Open Terminology Baseline and find Enterprise evidence workspace.
- Under Verification and portable evidence, choose the JSON file under Archive package. The browser limit is 10 MiB.
- Select Import archive.
- The service parses the package and validates its manifest and parts.
- Read the result. Archive validation failed: lists every failing code, separated by commas.
- Rely on the archive only after it shows Archive verified: with confirmed parity.
Example
One stored term definition changes by one character after export. The part hash no longer matches. The flattened content hash also changes. The service returns both failures and does not reconstruct the package. The workspace shows Archive validation failed: with both codes.
What this does not mean
The service checks whether 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. The current workspace has no download path for an exported archive. A valid package can still carry coverage gaps recorded in its manifest.
Related questions
Next step
Do not treat the import completion message as an integrity result. Stop when any integrity or tenant check is unknown.
View on Atlassian Marketplace