CV / FIELD NOTESREFERENCE LEDGER · 2026

Built with respect for what came before.

The products, open-source projects, and engineering ideas we studied while building CodeVetter. Each note names a concrete lesson and the boundary of our own work.

Inclusion acknowledges research or inspiration. It does not imply endorsement, affiliation, code reuse, or feature parity. “In the product” identifies a bounded integration; the other labels describe research.

38 source-linked notes4 areas of influenceRead the wider research archive ↗

THE LEDGER38 ENTRIES

Search the notes

01AiderCode contextA small, ranked repository map gives an agent useful context without dumping the whole tree.Design reference 02GreptileVerificationA code review must follow a change beyond the diff.Design reference 03CodeRabbitVerificationReview is more useful when it arrives in the developer’s normal change workflow.Design reference 04Qodo / PR-AgentVerificationA review should be close to tests and the intent behind a change.Research reference 05EllipsisVerificationThe useful review loop continues from finding to attempted fix.Research reference 06SourceryVerificationFast review can combine code quality signals with readable feedback.Research reference 07BitoVerificationRepository architecture and external project context can change the meaning of a diff.Research reference 08Graphite AgentVerificationReview quality depends on the shape and timing of the change.Research reference 09Panto AIVerificationDesign documents, tickets, and code history can be relevant to review.Research reference 10GitHub Copilot code reviewVerificationA code host can make automated review a normal request on a pull request.Research reference 11DeepWikiCode contextA repository can be made legible quickly through structured explanation.Design reference 12SourcegraphCode contextFinding the right code is a first-class engineering workflow.Design reference 13Augment CodeCode contextFresh repository context should follow the developer across tools.Research reference 14ArborCode contextDeterministic graph traversal is a useful answer to structural questions.Design reference 15LogicStamp ContextCode contextArchitecture facts can be compiled into deterministic, diffable contracts.Research reference 16RepomixCode contextA repository packet should be portable and deliberate about what it includes.Research reference 17SwimmCode contextDocumentation is more useful when it remains connected to code.Research reference 18Google Code WikiCode contextRepository explanations should be refreshed as code changes.Research reference 19OpenDeepWikiCode contextRepository documentation can be self-hosted and available to agents.Research reference 20Claude CodeAgent workflowsAn agent can discover context through targeted search and reads.Design reference 21OpenAI CodexAgent workflowsAn agent’s patch and its execution trace should be available for inspection.Design reference 22CursorAgent workflowsCodebase navigation can feel immediate inside a coding workflow.Design reference 23WindsurfAgent workflowsAn agent’s context has to be assembled from several live signals.Research reference 24ContinueAgent workflowsThe developer should be able to choose models and context sources.Research reference 25ClineAgent workflowsPlanning and acting benefit from a visible boundary.Research reference 26Gemini CLIAgent workflowsA terminal agent can keep planning, tools, and code changes in one inspectable loop.Research reference 27Tree-sitterBuilding blocksSyntax trees make source relationships repeatable and fast enough for local tooling.In the product 28ast-grepBuilding blocksStructural search can express focused review rules more clearly than text matching.In the product 29SemgrepBuilding blocksSecurity and bug patterns can be written as reviewable code-shaped rules.Research reference 30CodeQLBuilding blocksDeep code queries can reveal data flow and security relationships.Research reference 31ripgrepBuilding blocksFast, plain text search is often the right first step in code exploration.Research reference 32GitNexusBuilding blocksA code graph can be exposed as a useful interface for agents.Research reference 33gitoxideBuilding blocksGit history can be explored through an owned Rust interface.Research reference 34SCIPBuilding blocksAn interchange format can connect symbol and reference information across tools.Research reference 35codesizeBuilding blocksA tiny heuristic can still point a reviewer toward risky code.Research reference 36Unsupervised FinderVerificationSearch a space of possible explanations before asking an agent to tell a story.Design reference 37DeepWorkVerificationLong agent tasks need explicit steps, artifacts, and quality gates.Design reference 38Karpathy’s LLM WikiCode contextKnowledge can accumulate as a maintained, inspectable artifact.Design reference