Determine how to identify where in a codebase a problem likely lives and what tools can be used to build a rough semantic map of what different parts of the codebase do.
The goal is to narrow an issue down to a likely area of the repository before assigning it to team members.
This should evaluate practical approaches such as repository structure analysis, path and naming heuristics, symbol and dependency indexing, embeddings, code search, ownership signals, git history, and other lightweight or scalable techniques.
The output should define an approach Dispatch can use to infer the most relevant files, directories, or components for a reported issue.
This work is a prerequisite for #15 and should account for the team/member structure introduced in #12.
Determine how to identify where in a codebase a problem likely lives and what tools can be used to build a rough semantic map of what different parts of the codebase do.
The goal is to narrow an issue down to a likely area of the repository before assigning it to team members.
This should evaluate practical approaches such as repository structure analysis, path and naming heuristics, symbol and dependency indexing, embeddings, code search, ownership signals, git history, and other lightweight or scalable techniques.
The output should define an approach Dispatch can use to infer the most relevant files, directories, or components for a reported issue.
This work is a prerequisite for #15 and should account for the team/member structure introduced in #12.