Source graph
Route nodes come from the repo.
page.tsx files become route nodes, route groups collapse correctly, and dynamic segments stay generic for stable comparisons.
App RouterPages RouterDynamic routes
Diagram
Your route diagram becomes executable evidence.
The diagram is not a quarterly sketch. It is a parser-derived graph that starts with your source tree, gains runtime weight, and shows what changed between deploys.
01
Source graph
page.tsx files become route nodes, route groups collapse correctly, and dynamic segments stay generic for stable comparisons.
02
Navigation edges
TrueClara derives the expected route shape before traffic arrives, then uses runtime transitions to show whether the path is alive.
03
Runtime weight
Entries, exits, and edge transition rates let the diagram explain where behavior changed instead of merely showing where routes exist.
Navigation edges
Links and router calls become paths users can move through.
TrueClara derives the expected route shape before traffic arrives, then uses runtime transitions to show whether the path is alive.
Link hrefrouter.pushredirects
Runtime weight
Traffic makes the graph operational.
Entries, exits, and edge transition rates let the diagram explain where behavior changed instead of merely showing where routes exist.
EntriesEdge rateValue reach
Deploy diff
The canvas shows added, removed, and modified routes.
Every deploy gets a marker. The diff turns route topology into a release artifact the team can inspect.
AddedRemovedModified
Before / after · diagram
A static route list becomes a living, deploy-aware graph.
Source structure, runtime weight, and deploy diffs sit in one surface — so route topology is something you read at deploy time, not reconstruct after.
Install
The first graph appears from the codebase immediately.
A dashboard asks you to wait for data.
Inspect
Nodes and edges carry live transition weight.
A route list misses how users move.
Diff
Route changes are visible at deploy time.
Release impact is reconstructed later.
The diagram tells you what your app is.
Observations build on top of that graph to show what changed and which release caused it.