Code

The code source is the structural backbone of the ontology. It contains the modules, symbols, imports, and call paths of every connected repository, extracted by language-native parsers.

What it contains

• Modules — files and their logical groupings, with the import/export graph.
• Symbols — functions, classes, interfaces, types, and their signatures.
• Call paths — which symbols call which, so "what does this function touch?" is answerable.
• Dependencies — external packages and their resolved versions.

How it is built

Structure is extracted deterministically. Parsers walk the AST of each supported language and produce the module graph, the symbol table, and the call paths. The result is reproducible: the same commit produces the same code source, every time. No model runs during this step.

Providers

The code source is fed by repository providers: GitHub, Azure DevOps, and GitLab. Multiple repositories can feed the same project's code source. Ingestion is incremental — only changed files are re-parsed on each sync.

What a code search hit looks like

A code search hit identifies a symbol or module, scores it against the query, and carries a ref you can resolve to the full entity:

{
  "ref": "code:github:acme/api:main:src/auth/verify.ts:verifySession",
  "source": "code",
  "title": "verifySession",
  "snippet": "Validates a JWT session token and returns the decoded principal.",
  "score": 0.91,
  "entity_type": "function",
  "file_path": "src/auth/verify.ts",
  "repository": "acme/api"
}

Fetching this ref returns the full symbol, its signature, its callers, its callees, and the module it belongs to — the graph neighborhood, not just the file.

Next: Graph.