At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Current enterprise freeze | Select Run verification | One summary sentence with the conformance status | Verification does not prove source correctness |
| Affected artifact | Use Search deposited evidence or the Artifact filter | Frozen artifact record with Revision, SHA-256, and Availability | Search matches indexed prefixes, not arbitrary full text |
| Trace start | Pick a Start node and select Show trace graph | Trace hops for that node | The graph is empty until a start node is shown |
| Approved or imported trace links | Select Reverse provenance | Path to requirements, decisions, or regulations | Candidate and rejected links do not count as governed evidence |
| Code or test involved | Find its declared code_reference or test node | The external reference recorded on the node | No code revision or hash is captured |
| Missing endpoint or bounded result | Review Coverage blockers | Visible reconstruction gap | A partial trace cannot support a complete claim |
How it works
- Open Terminology Baseline and find Enterprise evidence workspace.
- Review Coverage blockers.
- Select Run verification and read the summary.
- Use Search deposited evidence or the Artifact filter to find the affected record.
- Note its Revision, SHA-256, and Availability.
- In Trace graph, choose the Start node and select Show trace graph.
- Select Reverse provenance. Review each hop's Evidence reference or its unavailable reason.
- Select Download trace chain to keep the chain as a JSON file.
Example
An incident concerns a controller change. The frozen policy page shows the revision and SHA-256 in force at the freeze. The controller appears as a declared code reference node pointing to the repository. Reverse provenance from that node reaches its component requirement, a business decision, and the regulation. A missing hop appears as a coverage gap.
What this does not mean
The workspace reconstructs recorded evidence. It does not perform root-cause analysis or restore absent source content. Code revisions stay in the repository; the app records only the reference. It does not approve remediation or certify compliance. Conclusions remain limited to the frozen evidence and approved links.
Related questions
Next step
Verify the current freeze before using its reverse trace in an incident review.
View on Atlassian Marketplace