At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Deposited document or code reference | Open its retained evidence | An implementation node with source provenance | The node must exist in the current baseline graph. |
| Imported or approved implementation link | Select Reverse provenance | A path from implementation to its requirement | Candidate and rejected links are excluded. |
| Approved requirement links | Follow the hops in Trace graph | Component and system requirement chain | Only supported node and relationship types are accepted. |
| Recorded authorization link | Open its evidence control | The business decision behind the requirement | No decision appears unless the relationship was deposited. |
| Missing or unavailable evidence | Review Coverage blockers and the hop message | An explicit gap instead of a silent omission | The app does not reconstruct undocumented reasons. |
How it works
- Open Enterprise evidence workspace.
- Find the deposited implementation under Frozen meanings and revisions.
- Select Open evidence for its retained record.
- In Trace graph, select Reverse provenance.
- Follow the implementation link to the component requirement.
- Continue through higher-level requirements to the business decision.
- Open the evidence control at each retained hop.
- Review Coverage blockers before relying on the path.
Example
A safety-control revision raises a motor stop threshold. Reverse provenance connects the code reference to its component requirement. The next link reaches the system safety requirement. An authorization link reaches the recorded business decision. Leadership can review why the change exists. The team can also see any missing evidence before an incident review.
What this does not mean
The trace proves the relationships recorded in the deposited graph. It does not infer intent, validate the implementation, or approve the business decision. An absent root can mean that no governed link was deposited. A complete path can still be partial when Coverage blockers are present.
Related questions
Next step
Open Reverse provenance for one critical implementation. Confirm that every requirement and decision hop has retained evidence.
View on Atlassian Marketplace