At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Deposited baseline and artifact | Select Download glossary slice | Artifact-specific meaning package | The artifact must be retained in the baseline |
| Indexed usage observations | Filter usages to the artifact | Relevant frozen term identities | A partial usage index blocks the slice |
| Frozen approved meanings | Join each observed term | Full meanings used by the artifact | Candidate or missing meanings are rejected |
| Archive and artifact hashes | Bind the package to retained evidence | Verifiable slice identity | The slice does not approve document release |
How it works
- Open Enterprise evidence workspace.
- Select the deposited baseline and artifact.
- Confirm its usage evidence is indexed.
- Select Download glossary slice.
- Check the artifact, archive, counts, and slice hash.
- Attach the slice to the required external handoff.
Example
A controlled procedure uses six approved terms. Its glossary slice contains those six frozen meanings and the matching usage observations. It excludes unrelated organization terms. The external document-control owner receives a smaller, artifact-bound package for review and reissue.
What this does not mean
A slice reflects deposited, indexed usage evidence. It can be incomplete when coverage or indexing is incomplete. It does not replace the full glossary, certify the artifact, approve reissue, or execute signatures.
Related questions
Next step
Generate a slice only after checking artifact retention and usage-index coverage.
View on Atlassian Marketplace