navieo

Codebase Knowledge

Open Codebase → Knowledge to inspect the route and element model produced by the latest scan. This is scanner evidence used by retrieval and deterministic navigation; it is not a replay of runtime user behavior.

What the graph represents

  • Route nodes use canonical paths or dynamic route patterns.
  • Element records describe scanner-discovered links, buttons, inputs, and other significant controls.
  • Navigation edges come from statically resolved anchors, Next.js links, and allowlisted literal router navigation.
  • Descriptions and embeddings help retrieval explain a route, but they never create executable navigation authority.

Select a route to review its description, elements, selector evidence, visibility, and navigation relationships. Dynamic routes such as /orders/[id] remain patterns; request-time instance evidence can narrow a final destination only when it maps unambiguously to one scanned route and verified control.

When to use it

  • After the first scan, confirm expected routes and controls are present.
  • After a significant UI change, run Codebase → Scan again and compare the graph.
  • When guidance reports an unavailable control, inspect the live page and its indexed destination. A missing scanner edge alone does not disqualify an otherwise eligible visible link for live guidance.
  • When an answer misses product context, improve the relevant route description or embedded documentation.

Hidden or protected routes remain in the model when needed for answers, but execution is more restrictive. A protected destination behind a menu, drawer, popover, dialog, or other reveal prerequisite stays answer-only.

Limitations

The graph cannot prove that a user is signed in, authorized, or viewing a particular record. It does not enumerate every dynamic instance, observe form values or authorize business actions. Live guidance uses the current page to verify targets, but hidden or lazy-loaded panels may still be unavailable. Re-scan after changes and report unsupported patterns; keep intentional owner exclusions in place. See release compatibility for SDK support.