At a glance
| Input | Current interface | Visible result | Server boundary |
|---|---|---|---|
| User role | Administrator controls | The whole admin app opens only for term managers | All enterprise resolvers also 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 and Artifact selects plus Frozen term or evidence search text | A narrower current page | These filters run in the browser. They do not search later pages. |
| A trace node | Start node, then Show trace graph | Retained graph hops in Trace graph | Forward impact and Reverse provenance switch between directions the server returned. |
| Current freeze | Run verification | One summary line: status and how many stored objects match | The server also builds a per-artifact conformance report. The interface does not render it. |
| Current freeze | Export archive | Action completion message | The server queues the archive job. Job coordination is not controlled from this screen. |
| JSON archive, up to 10 MiB, in Archive package | Import archive | Archive validation failed: with error codes, a parity error, or "Archive verified: N records imported, parity confirmed." | The picker accepts .json only. Unreadable JSON and files above 10 MiB show an error. |
| 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 in Frozen term or evidence search and select Search deposited evidence for a server search.
- Use the Subject and Artifact filters to narrow only the loaded page.
- Choose a Start node and select Show trace graph.
- Compare Forward impact with Reverse provenance. Select Open evidence where retained evidence exists.
- Run verification, archive actions, downloads, uploads, and Prepare and queue freeze as needed.
Example
An evidence administrator searches for “material incident.” They load its trace graph from the term node. 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. The workspace always opens the current freeze; older freezes cannot be selected. Archive import shows error codes and parity, not a per-record report. Detailed 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