Journey View
Journey View turns a complex session into an agent-by-agent swimlane so teams can understand how work moved across prompts, tools, and delegated actors over time. It highlights governance signals inline, including risk badges, guardrails, and human oversight events.
Use it when a flat event timeline is no longer enough. This view is especially useful for debugging multi-agent workflows and explaining cross-system execution to reviewers or auditors.
Journey View
Journey View renders any VeriProof session as an interactive swimlane diagram. Instead of a flat chronological step list, Journey View organizes execution by agent — each lane represents a distinct agent, and the horizontal axis represents time. Delegation handoffs, tool calls, and governance events appear as labeled flow elements between lanes.
Business Owners see session summaries but not step-by-step execution traces — Journey View requires trace access, so it is not part of the Business Owner portal view. All other roles can open Journey View from the Time Machine toolbar.
Lanes and steps outside your engagement scope are blurred. Click Export Diagram to download a PDF of this view for inclusion in your evidence package.
You see the agent-level overview: which agents participated, the delegation chain between them, and the governance signals (risk badges, guardrail results) attached to each agent. You do not see the per-step execution trace inside each lane. Use the Export Diagram button to attach a governance-annotated agent map to your evidence package.
The governance events overlay on each step shows which rules evaluated and their result. Use this to verify that your Rego rules are firing at the right steps in multi-agent chains before a change goes to production.
Reading the Swimlane Diagram
Lanes
Each horizontal lane corresponds to a single agent that participated in this session. The lane header shows:
- Agent ID — the unique identifier assigned in your SDK configuration
- Agent role — Orchestrator, Specialist, Validator, Router, or Primary (see Agent Roles)
- Step count — total instrumented steps attributed to this agent
- Risk contribution — whether this agent’s steps contributed to an elevated session risk level
Steps
Steps appear as labeled boxes within each agent’s lane. Step types are visually distinguished by shape and color:
| Shape | Step type |
|---|---|
| Rounded rectangle | LLM call |
| Diamond | Decision / guardrail evaluation |
| Parallelogram | Tool call |
| Arrow label | Agent delegation |
| Circle | Session start / end |
Click any step to open its full detail in a side panel — the same data shown in the Time Machine Story tab for that step.
Delegation Arrows
When one agent delegates work to another, a labeled arrow connects the delegating step in the parent lane to the first step in the child agent’s lane. The arrow label shows the delegation type and any parameters passed.
If the delegated-to agent ran on a separate system and its session was linked by parentTraceId, the arrow crosses to a secondary session view — see Cross-System Session Links below.
Governance Signals in the Diagram
Journey View overlays governance signals directly on the diagram so you can see at a glance where risk concentrations occur in the execution flow:
- Red outline — a step with a CRITICAL or HIGH risk annotation
- Orange outline — a step with a MEDIUM risk annotation
- Shield icon — a guardrail evaluation occurred at this step
- Block icon — a guardrail blocked this step
- Human icon — a human oversight annotation is present at this step
The step detail side panel shows the full annotation set for any selected step.
Cross-System Session Links
When your architecture routes AI work across service boundaries — for example, an orchestrator on Service A delegates to a specialist on Service B — VeriProof links the child session back to the parent delegation step via parentTraceId and parentDelegationSpanId fields set in the SDK.
Journey View detects these links and extends the diagram to include the linked child session. Linked sessions appear in a separate panel below the primary diagram, connected by an inter-system delegation arrow. Click Expand on a linked session to inline its steps into the main diagram.
To enable cross-system linking, the SDK in the downstream service must receive the parent’s traceId during request handling and pass it as parentTraceId during session building. See the Multi-Agent Tracing guide for implementation details.
Navigating Back to Time Machine
Time Machine and Journey View are tightly linked — you can switch between them at any time using the tabs in the top navigation bar of the session detail area. No context is lost when switching.