At a glance
| Input | Check | Resulting state | Limit |
|---|---|---|---|
| Expected stored freeze object | Presence in Object Store | missing | The summary shows the count, not the object key |
| Recorded SHA-256 checksum | Recalculate from the stored bytes | match or corruption | A hash checks only the recorded bytes |
| Recorded chunk root | Recompute the chunk root and look it up in the freeze | drift when the root is not listed | Drift is not proof of who changed it |
| Freeze identity inside the object | Compare it with the verified freeze | stale_source when the object belongs to another freeze | Freshness is not correctness |
| Live terms and pages after a terminology baseline | Compare current state with the baseline | Changed terms, changed pages, deleted terms, and pages with new findings | Shown under Changed since baseline, not by enterprise verification |
How it works
- Open Terminology Baseline and scroll to Enterprise evidence workspace.
- Review Coverage blockers.
- Select Run verification.
- Read the summary, for example “Verification nonconformant: 41 of 44 stored evidence objects match (missing 2, corruption 1).”
- For live source changes, select a terminology baseline and review Changed since baseline.
- Correct the cause, then create a later baseline or freeze when needed.
Example
A stored freeze object was overwritten outside the app. Verification counts it as corruption, while an object that cannot be read counts as missing. The summary keeps both counts separate. A Confluence page edited after the terminology baseline appears under Changed pages with its version change instead.
What this does not mean
A visible failure state does not repair the source or approve a replacement. Enterprise verification does not detect deleted, moved, or edited live Confluence pages. It does not check trace link targets in the current release. The workspace has no filter by verification state, availability, or conformance. Administrators still decide how to correct live content and when to create a later baseline.
Related questions
Next step
Resolve each evidence state according to its cause before using the package.
View on Atlassian Marketplace