At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Production version 6 | Open Terminology Baseline | Baseline page with legacy and enterprise sections | Deployment is confirmed. Forge staging qualification remains incomplete. |
| Completed scan evidence | Select Governed spaces | Scope for source preparation and capture | Choose 1–50 listed spaces. Every space needs at least one complete scan row |
| Retention requirement | Set Retention class, Retain until, and optional Legal hold | A retention policy stored with the freeze | Retention class and date are required. The organization remains responsible for its lawful retention decision. |
| Selected scope | Select Prepare and queue freeze | A pinned glossary snapshot, source counts, and seven capacity estimates | All selected scan rows must share one glossary snapshot. Missing, malformed, or mixed scan evidence stops preparation. |
| Accepted preparation | Queue the freeze | A persisted job and a bounded queue reference | Capacity rejection creates no job and emits no queue event. |
| Queued response | Display approved-term and scanned-page counts | Queue confirmation | The current UI does not poll the new job or expose cancellation. |
| Approved terms and matching page revisions | Run bounded capture | Frozen meanings, artifacts, revisions, hashes, usages, findings, and membership records | Each delivery processes at most 100 source units. A changed live page revision fails the job. |
| Complete persisted evidence | Verify counts, checksums, root hash, and snapshot | A promoted current baseline pointer | Incomplete evidence, drift, count mismatch, or failed verification blocks promotion |
| Create terminology baseline | Select Create baseline | Legacy baseline workflow | This is not the enterprise freeze path and remains enabled during migration |
| 250,000-artifact harness | Run a deterministic local simulation | Recovery and modeled resource evidence | It is not Forge capacity evidence and does not represent 250,000 Confluence pages |
How it works
- Confirm the installed app is production version 6 and exposes Enterprise evidence workspace.
- Complete a terminology scan for every space in the evidence scope.
- Open Terminology Baseline. Do not use Create baseline for an enterprise freeze.
- Under Create enterprise freeze, select the required Governed spaces.
- Enter Retention class and Retain until. Select Legal hold when policy requires it.
- Select Prepare and queue freeze. Wait for the queued confirmation and source counts.
- Treat this message as queue confirmation. The current UI does not poll the new job or expose cancellation.
- After the promoted baseline becomes current, reopen Terminology Baseline and inspect Frozen meanings and revisions.
Example
A medical technology team needs a fixed evidence point before an external review. Its administrator selects quality and product spaces with one shared scan snapshot. The server admits the workload and captures matching evidence. It verifies counts, checksums, and the root hash before promoting the baseline pointer.
What this does not mean
Production version 6 was deployed on 2026-09-26. The current qualification bundle still lacks Forge staging latency, consumption, cost, residency, and capacity evidence. The current page initiates a freeze but does not poll or cancel the returned job. The legacy Create baseline path remains enabled. The 250,000-artifact result is a local mixed-data simulation, not a page-capacity result. Baseline creation does not approve releases, execute signatures, certify compliance, or replace a QMS.
Related questions
Next step
Confirm production version 6 and the enterprise workspace. Then start with one scanned space and a documented retention decision. View Compliance Glossary on Atlassian Marketplace.
View on Atlassian Marketplace