At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Approved terms and governed scope | Create an enterprise freeze | Fixed meanings and source membership | Incomplete coverage must remain visible |
| Pages, code, tests, and files | Capture exact revision identity and hashes | Revision-bound evidence | Supported sources and size limits apply |
| Imported or approved links | Deposit the trace graph | Forward and reverse evidence paths | Candidate links do not count |
| Completed baseline | Verify and export | Integrity result and portable archive | The app does not provide legal WORM storage |
| External approval references | Add them to the handoff evidence | Recorded release context | Approval and signatures occur externally |
How it works
- Complete terminology review and the required scans.
- Select Create enterprise freeze for the release scope.
- Resolve Coverage blockers.
- Use Run verification when verification inputs are available.
- Inspect Forward impact and Reverse provenance.
- Use Export archive and Download reissue handoff as required.
Example
A release changes a regulated term and the code that implements it. The evidence package preserves the prior approved meaning, affected document revisions, code and test revisions, trace links, findings, and verification state. The external quality system retains the final approval and signature evidence.
What this does not mean
Compliance Glossary prepares and preserves supporting evidence. It does not decide release readiness, certify compliance, approve the release, or execute signatures. The organization owns the release decision and qualified approval system.
Related questions
Next step
Define the required release evidence before freezing the package.
View on Atlassian Marketplace