Compliance Glossary for Confluence

How do I verify a baseline?

Select Run verification in the Enterprise evidence workspace. It checks the current enterprise freeze; there is no baseline picker. For every stored evidence chunk, it recalculates the SHA-256 of the stored bytes and compares it with the recorded checksum. It also confirms the chunk root was recorded at promotion. The check changes nothing and reports one summary sentence.

Last verified against production v6 · 24 October 2026

At a glance

InputActionOutputLimit
Current enterprise freezeSelect Run verificationOne verification run for that freezePersisted verification evidence must exist
Stored evidence chunkCheck that it is presentmissing when absentAn absent chunk is never shown as a match
Stored chunk bytesRecalculate SHA-256 and compare with the recorded checksumcorruption on mismatchA matching digest does not prove source correctness
Chunk contentRecompute its content root and look it up in the recorded chunk rootsdrift when the root is not listedUnreadable chunk content also counts as drift
Chunk baseline identityCompare it with the freezestale_source when it belongs elsewhereOnly this freeze's recorded chunks are checked
All chunk resultsSummariseVerification conformant or Verification nonconformant, with match countsPer-chunk details are not displayed

How it works

  1. Open Terminology Baseline and find Enterprise evidence workspace.
  2. Review Coverage blockers before verification.
  3. Under Verification and portable evidence, select Run verification.
  4. Read the summary, for example "Verification conformant: 12 of 12 stored evidence objects match."
  5. Investigate any non-matching state before export or incident review.

Example

A freeze has twelve stored chunks. One chunk's bytes change in storage. Its recalculated SHA-256 no longer equals the recorded checksum. The summary reads "Verification nonconformant: 11 of 12 stored evidence objects match (corruption 1)." The freeze itself is unchanged.

What this does not mean

Verification is read-only. Usage and trace links are covered through the chunk checksums, not checked one by one. It verifies only the current freeze, not earlier ones. It does not certify compliance, establish legal validity, approve a release, or prove the original source was correct.

Related questions

Sha 256 Compliance EvidenceBaseline Conformance ReportVerify Exported Evidence Archive

Next step

Run verification before evidence export, audit handoff, or incident reconstruction.

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