At a glance
| Layer | Stored or displayed content | Important boundary |
|---|---|---|
| Approved meaning | Definition, category, synonyms, notes, references, effective dates, ownership, review fields, approval evidence, and meaning hash. | Only approved terms with separated approval evidence enter this freeze source. |
| Artifact and revision | Page identity, provenance, exact revision, media type, byte length, SHA-256 hash, and Object Store reference. | The SQL revision points to content-addressed canonical content. It does not embed the page body. |
| Usage and finding evidence | Usage rows bind a term to a revision. Finding descriptors retain identity, type, status, and optional term identity. | Finding descriptors do not retain page excerpts. |
| Trace evidence | The evidence model and persistence layer accept supplied trace links and count them in package metadata. | The current Confluence freeze source emits term and page units only. Its trace-link count can be zero. |
| Package metadata | Root hash, row counts, coverage, chunk roots, object checksums, conformance, archive section counts, and archive snapshot hash. | Scope, retention, source snapshot, checkpoints, and capacity decision remain job or freeze-state metadata. |
| Visible workspace | Frozen meanings and revisions, Coverage blockers, Freeze progress, Trace graph, availability, conformance, and impact. | The screen does not display every stored field, object key, count, or root. |
| Legacy baseline | Term state, page version, scan status, finding counts, and frozen usage rows. | The legacy path does not store page content hashes or trace-link coverage. |
| Operational qualification | A deterministic local workload covers 250,000 mixed artifacts and fault recovery | This is local simulation evidence. It does not establish Forge staging or production capacity. |
How it works
- Open Terminology 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 checks scope, snapshot consistency, source counts, and capacity.
- Monitor Freeze progress and review Coverage blockers.
- Inspect Frozen meanings and revisions and Trace graph.
- Select Run verification for the active baseline. The detailed result is returned by the server but not rendered as a report.
- Select Export archive to queue a portable evidence job.
Example
A policy freeze captures the approved meaning of “material incident.” It also captures a matching page body, revision, hash, usage rows, and finding descriptors. SQL keeps indexed records and membership. Object Store keeps canonical chunk content. If no trace links are supplied, the package trace-link count is zero.
What this does not mean
The current Confluence source rejects unavailable or changed pages instead of depositing an unavailable revision. The domain model can represent unavailable revisions from other evidence paths. A baseline does not certify compliance, approve releases, execute signatures, replace a QMS, or provide legal WORM storage. Hashes show byte changes. They do not prove source correctness or completeness.
Related questions
Next step
Use an enterprise freeze when evidence must retain exact meanings, page bytes, revision hashes, governed metadata, and a deterministic package root.
View on Atlassian Marketplace