# Agent Tool Call Workflow

Renderer-driven workflow prototype with lanes, anchored nodes, and orthogonal edges

Guided views
Explore this system Step through curated paths without changing the source diagram.
Beat Next

Ready Chapter 01 / 01
Guided chapter
Diagram guide Explore this system

Inspecting compiled semantics

`E` Export `T` Theme `S` Style `0` Reset`+` Zoom in`-` Zoom out `Esc` Close

Find a node
⌕ `/`

No matching nodes

Semantic passport
``
Verified source
Authored reach
Route probe Choose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lens Compare system roles

Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.

Choose a kind to inspect its nodes and touching relationships.

Semantic radar Building overview
Click node Drag to pan

### Renderer Rules

- • Lanes and columns determine node placement
- • Edges attach to explicit node anchors
- • Cross-lane paths use orthogonal routing
- • Short adjacent links stay unlabeled

### Workflow Semantics

- • Approval is a first-class policy step
- • Consent gates are visible in the main path
- • External calls stay inside the tool lane
- • Trace writes are separate from the hot path

### Why It Matters

- • This is closer to a diagram_type renderer
- • The graph can be edited without SVG surgery
- • Layout rules can be tested and improved
- • A future IR can reuse this shape directly