At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| A saved page scan | Read its page ID, page version, modified time, space, and glossary snapshot | The expected source coordinate for capture | The scan must be complete and belong to the pinned glossary snapshot. |
| The current Confluence page response | Request the page in storage-body format | Live version metadata and canonical body text | The source must be readable. Its version and modified time must match the scan row. |
| Canonical body bytes | Copy and hash the bytes | Base64-encoded content, SHA-256 hash, byte length, and media type | Only captured bytes receive a content hash. A hash does not prove that the source was correct. |
| Scan usage and findings | Bind each record to the artifact ID, revision ID, and content hash | Revision-specific usage observations and finding evidence | Findings do not retain page context snippets. Malformed arrays stop capture. |
| A completed capture chunk | Persist content and records before checkpointing | Content-addressed object, SQL artifact and revision records, and baseline membership | Each worker delivery reads at most 100 source units. Partial storage does not advance the job. |
| Complete deposited evidence | Recheck the pinned source snapshot before promotion | Verified counts, root identity, conformance, and a promoted baseline pointer | Source drift or count mismatch blocks promotion. |
How it works
- Complete a terminology scan for every page that belongs in the governed scope.
- Open Baseline and find Enterprise evidence workspace.
- Under Create enterprise freeze, select Governed spaces and set the retention fields.
- Select Prepare and queue freeze. The server pins the scan snapshot before capture begins.
- Review Freeze progress. A changed or unavailable source appears as a failed freeze, not as a successful deposit.
- After promotion, inspect Frozen meanings and revisions. Review Revision, SHA-256, and Availability. Use Open evidence for the retained record.
Example
A policy page was scanned at version 18. An editor publishes version 19 before the freeze worker reads it. The live version no longer matches the saved scan coordinate. The worker records source drift and does not deposit version 19 under the version 18 evidence claim. The team scans again and creates a new freeze from the updated evidence.
What this does not mean
Revision capture is not a Confluence page-approval workflow. It does not stop later edits. It does not execute signatures or create legal WORM storage. SHA-256 detects changed captured bytes; it does not prove authorship, regulatory sufficiency, or source accuracy. The current enterprise source requires a readable page revision that still matches its scan evidence.
Related questions
Next step
Use one scanned policy page to evaluate revision capture. Record its current version, queue the freeze, and compare the deposited revision and SHA-256 with the source evidence. View Compliance Glossary on Atlassian Marketplace.
View on Atlassian Marketplace