Trunk
The map draws
itself.
Trunk crawls your real pages and links to render a live journey graph. Broken paths, orphan routes, thin nodes — surfaced automatically. Not a whiteboard exercise. Not maintained by hand.
No hand-drawn maps.
Trunk crawls the running product and turns real links into edges. Every commit re-derives the graph. If a page moved, the map moves. If a link broke, the map shows it — as red.
- ✓Static links, dynamic routes, redirects — all rendered.
- ✓Cross-branch overlay — see what a delta adds or removes.
- ✓Depth-first / breadth-first / manual layout.
Product · Docs · Deltas — all wired.
The Journey isn't just a route map. Every node knows the docs that describe it, the deltas that touch it, and the signals it emits.
The classic sitemap — every page in your app, colored by health. Click a node to open the primitive that owns it.
Which routes are being changed right now, by whom. Amber nodes are open deltas — one click drops you into the delta workspace.
Overlay the drop-off — thicker edges carry more traffic, red edges are where users bail. The graph itself becomes a funnel diagnosis.
Every branch redraws its own map.
Working on a delta? Trunk shows you the graph as if your delta were merged — highlighting exactly what changed. New routes glow purple. Broken paths glow red. Nothing surprises you at ship time.
The graph is one of six pillars.
Journey stitches to signals (which pages leak users), documentation (which route is under change), deltas (what a branch does to the flow).