At a glance
| Input | Current interface | Visible result | Server boundary |
|---|---|---|---|
| User role | Read-only banner or administrator controls | Disabled actions for a non-administrator view | All enterprise resolvers currently require administrator authorization. |
| Governed spaces and retention | Prepare and queue freeze | Queue confirmation and Freeze progress. | The server pins the scan snapshot, counts source units, checks capacity, and accepts 1–50 spaces. |
| A term or evidence prefix | Search deposited evidence | A cursor-backed page of up to 50 records | The server searches indexed subject or artifact prefixes. |
| Loaded evidence records | Subject, Artifact, Conformance, and Impact | A narrower current page | These filters run in the browser. They do not search later pages. |
| Loaded trace links | Forward impact or Reverse provenance | Retained graph hops and explicit unavailable evidence. | The interface switches between graph directions already returned by the server. |
| Active baseline | Run verification | The workspace reloads after success | The server returns verification and conformance details. The interface does not render that detailed report. |
| Active baseline | Export archive | Action completion | The server queues the archive job. Job coordination is not controlled from this screen. |
| Valid JSON archive, up to 10 MiB | Import archive | Action completion or a visible error | Validation, isolated reconstruction, and parity checks run on the server. Their detailed results are not rendered. |
| Current artifact record | Download glossary slice or Download reissue handoff | A JSON download | The handoff records an external review action. It does not perform document control. |
| Approved file and retention | Upload evidence | Progress, artifact identity, revision identity, and available usage counts | Direct or staged upload runs through authenticated resolvers. |
How it works
- Open Terminology Baseline, then find Enterprise evidence workspace.
- Review Coverage blockers, Freeze progress, and frozen records before using any output.
- Enter a prefix and select Search deposited evidence for a server search.
- Use the four record filters to narrow only the loaded page.
- Compare Forward impact with Reverse provenance. Open retained evidence where available.
- Administrators can run verification, archive actions, downloads, uploads, and Prepare and queue freeze.
Example
An evidence administrator searches for “material incident.” Forward impact displays loaded downstream links. Reverse provenance displays loaded links toward retained source evidence. Missing evidence stays visible. The administrator runs verification, then downloads an artifact glossary slice. A reissue handoff can record the required external review.
What this does not mean
The workspace does not certify compliance. It does not replace a QMS or GRC platform. It does not approve releases or execute electronic signatures. It does not provide legal WORM storage. Page filters do not cover unloaded records. Detailed archive and verification results remain server-side. No verified 200,000-page production capacity claim is available.
Related questions
Next step
Evaluate one governed space with a completed scan. Create a freeze, inspect both trace directions, and run verification before exporting evidence. View Compliance Glossary on Atlassian Marketplace.
View on Atlassian Marketplace