Compliance Glossary for Confluence

What does conformance show?

Conformance shows whether the stored objects of an enterprise freeze still match what was recorded. Run verification returns an overall status, such as conformant or nonconformant. The workspace shows it in one summary line with counts per state. The server also builds a per-object conformance report, but the current release does not display, store, or download it.

Last verified against production v6 · 24 October 2026

At a glance

InputActionOutputLimit
Current enterprise freezeSelect Run verificationOne summary line with status and matched-object countThe workspace opens the current freeze; there is no baseline picker
Each stored freeze objectCheck presence, SHA-256 checksum, chunk root, and freeze identityObject state: match, missing, corruption, drift, or stale sourceA match confirms recorded evidence, not source correctness
Object statesCount states that are not matchCounts in the summary, such as “missing 2, corruption 1”Object keys and reasons are not shown
Per-object checksBuild the conformance report on the serverChecks executed, matches, conflicts, unresolved checks, and a report hashReturned to the browser but not rendered or saved
Missing persisted verification inputStop verificationVisible errorA gap is not converted into a match

How it works

  1. Open Terminology Baseline.
  2. Scroll to Enterprise evidence workspace.
  3. Review Coverage blockers.
  4. Select Run verification.
  5. Read the summary line, for example “Verification conformant: 44 of 44 stored evidence objects match.”
  6. Record the status and counts in your own audit working papers.

Example

A stored freeze object no longer matches its recorded checksum. Verification classifies it as corruption and the freeze as nonconformant. The summary shows “corruption 1” next to the matched count. The team investigates storage access before using the package.

What this does not mean

Conformance is a read-only assessment of recorded evidence. It does not check live Confluence pages. It does not certify compliance. It does not approve a release. It does not prove that the original source was correct. It does not repair evidence. The workspace has no Conformance filter or column. Legal validity, signatures, and final acceptance remain outside the app.

Related questions

Next step

Run verification before export, audit handoff, or incident review. Resolve every nonmatching object first.

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