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 Router
- Pages Router
- Dynamic routes
Diagram
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.
Operating model
Each product surface follows the same loop: define the route state, compare the release window, carry evidence into the decision.
Source graph
page.tsx files become route nodes, route groups collapse correctly, and dynamic segments stay generic for stable comparisons.
Navigation edges
TrueClara derives the expected route shape before traffic arrives, then uses runtime transitions to show whether the path is alive.
Runtime weight
Entries, exits, and edge transition rates let the diagram explain where behavior changed instead of merely showing where routes exist.
Deploy diff
Every deploy gets a marker. The diff turns route topology into a release artifact the team can inspect.
Before / after
The redesign keeps comparison visible because the product promise is not more charts. It is a cleaner handoff from release to action.
A dashboard asks you to wait for data.
The first graph appears from the codebase immediately.A route list misses how users move.
Nodes and edges carry live transition weight.Release impact is reconstructed later.
Route changes are visible at deploy time.Get started
Observations build on top of that graph to show what changed and which release caused it.