Skip to main content
Diagram

Your route graph is the reward layer's substrate.

Before TrueClara can run an experiment, it needs to know what your app is. The diagram is a parser-derived graph that starts with your source tree, gains runtime weight, and scopes every canary to the routes a change can actually touch.

Start freeSee the reward layer
01

Source graph

page.tsx files become route nodes, route groups collapse correctly, and dynamic segments stay generic for stable comparisons across arms.

02

Navigation edges

TrueClara derives the expected route shape before traffic arrives, then uses runtime transitions to know which value routes a given change is in scope for.

03

Runtime weight

Entries, exits, and edge transition rates tell the experiment which routes carry enough traffic to power a verdict.

Project Diagram (THEME (light))
TrueClara reads reshot.dev's route graph straight from the repo and renders it as the live operating surface — the pricing → checkout → success funnel on one canvas.
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 across arms.

App RouterPages RouterDynamic routes
Project Diagram (THEME (light))
Route nodes and edges come from the app itself — a navigable graph, with /checkout flagged on the experiment path.
Runtime weight

Traffic makes the graph operational.

Entries, exits, and edge transition rates tell the experiment which routes carry enough traffic to power a verdict.

EntriesEdge rateValue reach
Deploys List (THEME (light))
Every deploy lands on the same graph — the diff shows exactly which routes deploy 7f3a2c1 added, removed, and modified.
Deploy diff

The canvas shows added, removed, and modified routes.

Every deploy gets a marker. The diff is how TrueClara scopes the affected routes for the canary that deploy triggers.

AddedRemovedModified
Observation Detail (THEME (light))
An experiment verdict inherits the same route model — /checkout pinned to the deploy that started it.
Before / after · diagram

A static route list becomes a living graph the reward layer can act on.

Source structure, runtime weight, and deploy diffs sit in one surface — so TrueClara always knows which routes a change can affect before it scopes the experiment.

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, before the canary even starts.
Experiment scope is reconstructed later.

The diagram tells TrueClara what your app is.

Every experiment TrueClara runs is scoped by this graph — it's how the reward layer knows what to test and where the change can be felt.

Start freeSee the reward layer