codebase-knowledge-graphlisted

# Codebase Knowledge Graph — graphify integration Maintain a live map of the codebase — modules, symbols, dependencies, call sites — so change propagation operates on facts, not memory. This is the `graphify` link in the propagation chain. Investigate before asserting impact: query the graph, don't guess what depends on what. ## Fits in the pipeline - **Stage 9 + continuous** — the `graphify` step in `change-propagation`'s chain (PRD → blueprint → roadmap → **graphify** → code). Refresh it before in-code changes so the impact/call-site set is accurate. ## On invocation — detect, then choose a path ### 1. Detect Check whether graphify is installed (try both — on Windows, pip often installs it OFF the PATH): ``` graphify --version python -m graphify --version ``` - If either responds → **resolve & persist the invocation (step 1b)**, then go to "Using graphify". - If not found → present the two options below. Don't silently pick. ### 1b. Resolve & persist the invocation (the step that stops agents falling back to grep) The #1 reason a built graph goes unused is a bare `graphify` that isn't on the PATH — on Windows pip drops it in `%APPDATA%\Python\Python3xx\Scripts\graphify.exe`, so `graphify` "command not found" and the agent reaches for grep instead. Resolve a command that actually runs, in this order: 1. `graphify` (already on PATH) · 2. `python -m graphify` (PATH-independent) · 3. the absolute exe — Windows: `%APPDATA%\Python\Python3*\Scripts\graphify.exe`; POSIX