At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Deposited evidence node | Open Trace graph | A starting point for trace expansion | The node must be indexed and imported or approved. |
| Governed outgoing links | Select Forward impact | Connected downstream evidence hops | The default service depth is five hops. |
| Governed incoming links | Select Reverse provenance | Connected upstream evidence hops | Candidate and rejected links are excluded. |
| Retained hop evidence | Select its evidence control | The supporting evidence reference | A hop can state that retained evidence is unavailable. |
| Missing endpoint or bounded result | Review Coverage blockers | A visible reason for partial results | Partial results must not be presented as complete. |
How it works
- Open Enterprise evidence workspace.
- Find the required item under Frozen meanings and revisions.
- Select Open evidence when the retained record is available.
- Open Trace graph.
- Select Forward impact to see downstream relationships.
- Select Reverse provenance to see upstream relationships.
- Open the evidence control for each retained hop.
- Review Coverage blockers before using the result.
Example
A compliance director opens a requirement. Forward impact shows connected documents, code references, and tests. Reverse provenance shows the recorded regulation or business decision behind it. Each line names the relationship. The director can inspect retained evidence without learning graph syntax or asking an analyst to write a query.
What this does not mean
Point-and-click access does not create missing relationships. It only presents imported or approved links in the deposited graph. Unsupported endpoints, result bounds, and unavailable evidence remain visible. The path does not establish legal interpretation, implementation correctness, or complete coverage.
Related questions
Next step
Open Trace graph for one critical evidence item. Review both directions and resolve every coverage blocker.
View on Atlassian Marketplace