Flow browser

Use the search box below to find execution paths (function call trees with file:line links).

This search is only for code flows, not the MkDocs header search (which indexes prose manuals like INPUT.md and ARCHITECTURE.md).

Pick a flow below, or search (e.g. tab dlv, ctrl-c, stop). The call tree expands inline under the row you click; click the same row again to collapse it. Deep links: #dlv-console-tab, #stop-pipeline, …

Loading flows…

How the catalog is built

Call-graph analysis is done by the official Go tool golang.org/x/tools/cmd/callgraph, pinned in go.mod via a tool directive and run as go tool callgraph -algo vta. cmd/flowdoc parses its edge list and renders trees into flows.json.

Layer	Source	Meaning
Curated	flows: in flows.spec.yaml	Real user triggers (Tab, Ctrl-C, :gdb continue, …) with GDB/Delve branches
Auto	discover: in the same file	One tree per reachable function found by callgraph; marked auto

Auto flows are reachable static paths from main, not recordings — an edge may not fire for a given user action.

go tool callgraph -algo vta ./cmd/gdbforge   # raw edges (the analyzer)
go run ./cmd/flowdoc --generate              # edges -> flows.json
go run ./cmd/flowdoc --check                 # validate file:line links

CI runs --generate before MkDocs on every docs deploy, so the catalog tracks the code.

See also INPUT.md and DEBUGGER_INTEGRATION.md for prose documentation.