How TrueClara works
The parser, runtime SDK, deploy records, and detector work together to explain behavior changes in a Next.js app.
TrueClara is behavior observability for Next.js. It does not replay every click or ask you to hand-instrument funnels. It builds a route graph from code, overlays runtime traffic, and watches how user flow changes after deploys.
Parse the app
@trueclara/parser reads the Next.js project and emits a deterministic graph of routes, layouts, and navigation edges.
Observe runtime flow
@trueclara/next sends pageview and transition counters after consent allows analytics delivery.
Attach deploy context
CI uploads the graph and commit metadata for each release so TrueClara knows what shipped.
Create observations
Detection jobs compare current behavior against deploy-aware baselines and create observations with route, edge, deploy, and statistical evidence.
Core surfaces
| Surface | What it answers |
|---|---|
| Map | What routes exist, how traffic moves through them, and where observations attach. |
| Observations | What changed, how severe it is, and which evidence supports the finding. |
| Deploys | Which release introduced route or edge changes and which observations appeared after it. |
| Routes | Which paths are value routes, low-traffic routes, or routes with active observations. |
The signal model
TrueClara joins four inputs:
- Static graph: the route and edge model from the parser.
- Runtime events: aggregate pageview and transition counters from the SDK.
- Deploy metadata: commit, branch, previous commit, graph diff, and deployment time.
- Project settings: value routes, alert destinations, consent defaults, and thresholds.
The output is an observation. Observations are not generic analytics alerts. They are tied to a route or edge, include the relevant deploy boundary when available, and carry evidence that a reviewer can inspect.
What TrueClara detects
| Observation type | Source | Example |
|---|---|---|
| Broken inbound URL | Unmatched paths after deploy | /docs/v1/install starts receiving traffic after a docs route was removed. |
| Route regression | Value-reach rate changes for a route | Sessions visiting /pricing reach /checkout/success less often after a release. |
| Edge regression | Transition rate changes between routes | Fewer users move from /signup to /onboarding/profile. |
What TrueClara does not do
- It does not replace product analytics.
- It does not run experiments or feature flags.
- It does not collect persistent browser identity by default.
- It does not infer business value without value routes or enough traffic.
Trust requirements
The graph, runtime SDK, and deploy upload all need to be healthy before regression observations are useful. If any one input is missing, TrueClara should make that gap obvious instead of presenting weak confidence as certainty.