research-codebaselisted

# Codebase Research Local codebase research for finding patterns, tracing call flows, and mapping module dependencies. No external web access — all evidence comes from the local codebase. ## Iron Law > **CITE CODE, NOT ASSUMPTIONS** > > Every claim about the codebase must have file:line evidence. Patterns require 3+ > examples to count as patterns. "I believe this is the pattern" without citation is > a research failure. If you can't find the evidence, say so — don't invent it. ## Trust Tier **trusted** — Local code is the authoritative source. All findings carry maximum confidence. ## When This Activates Loaded by Researcher agent when `RESEARCH_TYPE` is `codebase`. Covers: - Finding existing patterns before implementing new features - Tracing call chains to understand data flow - Mapping module boundaries and dependencies - Identifying conventions used across the codebase --- ## Methodology ### Step 1: Define Scope Before reading anything, define the scope: - Target area (directory, module, or concept) - What you are looking for (patterns, functions, conventions, dependencies) - What files are likely NOT relevant (test fixtures, generated files) ### Step 2: Structural Scan Use Glob and Grep to build a map before reading: ``` Glob: Find all files matching the area (e.g., src/auth/**/*.ts) Grep: Search for key terms, function names, type names ``` Use this to build a candidate file list. Do not read more than 15 files total. ### Step 3: Deep Read (Targeted) R