At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Captured terms, page revisions, usages, findings, and membership | Canonicalize and hash each persisted chunk | A deterministic chunk root | The root represents canonical record material, not the source content itself. |
| Baseline ID and completed chunk roots | Sort the chunk roots and hash the aggregate at promotion | The enterprise baseline root hash | A changed chunk root changes the aggregate. |
| Stored chunk bytes | Run verification recalculates their SHA-256 | Match, or corruption against the recorded checksum | The workspace shows a summary sentence, not the hash values. |
| Stored chunk content | Run verification recomputes the chunk root | Match, or drift when the root was not recorded | Verification checks chunks one by one. It does not display the aggregate root. |
| Ordered archive section proofs | Hash the section proofs under the baseline identity | A separate archive source snapshot hash | The archive hash and the baseline root hash are different controls. |
How it works
- Open Terminology Baseline and find Enterprise evidence workspace. It opens the current enterprise freeze.
- Inspect Frozen meanings and revisions. Review each visible SHA-256 and Availability value.
- A term without a source page shows "Integrity: in the frozen chunk hash and baseline root hash".
- Select Run verification.
- Read the summary sentence and any Coverage blockers. A non-matching chunk is never reported as conformant.
Example
A freeze has three stored chunks. One chunk is rewritten in storage after promotion. Its bytes no longer match the recorded checksum, and its content root is no longer in the recorded list. Run verification reports the chunk as corruption and the freeze as nonconformant.
What this does not mean
The root hash is not a certificate, signature, timestamp authority, or legal WORM guarantee. It does not prove authorship or regulatory sufficiency. It does not reveal which business fact is correct. The workspace does not display the root hash value. The archive source snapshot hash serves a different purpose and must remain separate.
Related questions
Next step
Evaluate a small enterprise freeze. Run verification and review the summary together with coverage blockers. View Compliance Glossary on Atlassian Marketplace.
View on Atlassian Marketplace