Use Verachi
Graphs
Inspect decision and project relationships without leaving the record.
UpdatedMay 4, 2026
On this page
Graphs show how records relate. They live on decision and project detail pages.
The /graph route is only a compatibility redirect. /graph?decision=<id> opens that decision detail page. /graph without a decision opens Projects.
Decision graph
Open a decision and expand Relationships.
The decision graph shows:
- related decisions
- supersession chains
- decision dependencies
- project links
- linked evidence
Use it to see what a decision depends on, what replaced it, and what records sit nearby. Decision dependency links are decision-to-decision edges, not evidence artifacts.
Project graph
Open a project and choose the Graph tab.
The project graph shows:
| Column | Records |
|---|---|
| Inputs and controls | Integrations, upstream projects, assigned guidelines |
| This project | The current project |
| Linked work and risk | Decisions, risk findings, dependent projects, gaps |
Use it to understand project context without jumping through every record one by one. Use the graph toolbar to add upstream dependencies, filter one or more node types, fit the view, or open the graph fullscreen. The Gaps filter shows phantom nodes for missing context such as no linked decisions, no sources, no checks, missing risk owners, unresolved blockers, missing dependencies, or an unevaluated project risk signal.
Read the graph
- Click a node to inspect details.
- Use People involved in the selected-node sheet to see supported owners, creators, or risk actors without leaving the graph.
- Use risk quick actions in the selected-node sheet to change owner, severity, or state.
- Right-click a node or blank graph area to open contextual actions.
- Drag nodes to adjust the current canvas view.
- Use the node action to open the full record.
- Follow arrows to understand dependency direction.
- Read green, yellow, and red edges as the connected record's current risk or health signal.
- Read dashed risk edges as source context. They show where a finding came from, not the risk target.
- Read dashed muted nodes as gaps. They are prompts to capture missing project context, not real records.
- Remove upstream dependencies from the selected-node sheet when they no longer apply.
- Treat muted or warning states as signals to review the underlying record.