Systems / Developer Tools / 2026
Repository intelligence
Making a codebase easier to reason about.
I am developing local Rust tools for repository discovery, structured retrieval, and validation context.
Private — In development
Check the evidence against the source.
Follow a code question from repository structure to evidence with a known source state. Click a step, connection, or trace to inspect it.
Start the walkthrough, or inspect any step before running it.
Simplified from the project architecture. Runs locally; no live models, credentials, or external services.
The engineering
Inside
the decisions.
Make repository context precise enough to act on.
Developers and coding agents need precise answers about the code they are changing: where a symbol comes from, what depends on it, and what needs to be validated.
01The design decision
+
Combine language structure and local search with explicit evidence and validation context.
02The trade-off
+
Stored results are useful only within a known source state. Validation must remain distinct from retrieval, and whole-product qualification remains in progress.
03Extracting structured repository evidence
+
Built a Rust core around repository discovery, structured context, and evidence extraction.
04Combining parsing and local search
+
Used SQLite and FTS5 for local persistence and search, with Tree-sitter parsers for language structure.
05Checking the source state of a result
+
Developed explicit validation and qualification tooling so a stored result is not silently treated as proof of current source state.
↳Read the system flow
+
Repository intelligence · Public explanation of the implementation boundaries.
- DiscoverRead bounded repository context for developers and coding agents.
- Parse & indexTree-sitter structure and SQLite/FTS5 support local evidence retrieval.
- RetrieveReturn source context with information about its recorded state.
- RevalidateKeep a stored result distinct from a claim about the current code.
↳How it differs from Polli
+
Polli retrieves repository context inside a hosted agent platform. This project is local Rust tooling focused on structured source evidence and explicit validation for developers and coding agents.
↳A concrete stale-result example
+
A stored search result describes a function before an edit. Changing the source does not make that old result current. In the browser example, revalidation updates the result and its source-state label.
↳Implementation and demonstration
+
Repository discovery, parsing, local persistence, and validation tooling are under development. The browser lab demonstrates the stale-result boundary using a small sample repository, independently of the private Rust implementation.
↳Qualification still open
+
A complete language-support matrix and reproducible indexing, retrieval, and freshness benchmarks are not published. Whole-product qualification remains in progress.
Private — In development
Inspect
the work.
Active development of local retrieval and validation tooling. The current scope covers bounded repository context; whole-product qualification is still in progress.
Next project: Application engineering ↗Source material
Discuss the engineering