LOCATE state: symbol resolution #19

New issue

Open

opened 2026-04-07 20:23:56 +00:00 by austin · 0 comments

austin commented

2026-04-07 20:23:56 +00:00

Owner

Implement the LOCATE pipeline state.

Given a target name/description from UNDERSTAND, find the relevant code
Primary resolution: exact symbol lookup in the AST index
Fallback: fuzzy name matching, then semantic search via embeddings
If multiple candidates, present a short list to the model with a constrained ranking prompt ("which of these is most relevant to: {task}?")
Output: the resolved symbol(s) with their extracted code and dependencies
If nothing is found, transition to an error state that asks the user to clarify

Most of the work here is harness-side (index lookup). The model only gets involved for disambiguation.

Implement the LOCATE pipeline state. - Given a target name/description from UNDERSTAND, find the relevant code - Primary resolution: exact symbol lookup in the AST index - Fallback: fuzzy name matching, then semantic search via embeddings - If multiple candidates, present a short list to the model with a constrained ranking prompt ("which of these is most relevant to: {task}?") - Output: the resolved symbol(s) with their extracted code and dependencies - If nothing is found, transition to an error state that asks the user to clarify Most of the work here is harness-side (index lookup). The model only gets involved for disambiguation.