Documentation

Graphtia documentation · concept

What is Graphtia?

A platform direction for code understanding and reviewable agentic engineering.

Two kinds of context

Understanding software involves more than finding a file. You need to understand which parts rely on it, what contracts cross its boundary and which observations support a proposed change. Extended engineering work adds another question: how does the work being performed relate to the objective that started it?

Graphtia brings these concerns into two related product directions. Explorer maps source structure and supports focused investigation. Governance explores how tasks, plans, bounded work units and evidence can make an engineering effort easier to review.

Context that stays tied to the task

A task is paired with relevant source, explicit constraints and tests into a reviewable context package before a person or agent reasons about a change. This is a conceptual example of useful context.

TaskA focused question
01
Relevant codeSource + relationships
02
Context packageBounded review material
03
ContractsConstraints and uncertainty
04
TestsEvidence to inspect
05
Relevant code + contracts + tests form the review context.

Start with an engineering question

For example, “What must we review before changing checkout validation?” identifies a module, its consumers and relevant checks. The useful result is a bounded explanation with source references and known limits. It is not necessarily a graph of the entire repository.

What is available on this website

  • The public website, documentation and persistent early-access waitlist are live.

  • Explorer has a working engineering build; public product access is being prepared.

  • Governance remains a future product direction. Accounts, checkout, licenses and public downloads are not enabled.

Graphtia

This page is on its way. Join the waitlist to hear what’s next for Graphtia.

Join waitlist