This project has a knowledge graph at graphify-out/ with god nodes, community structure, and cross-file relationships.
Rules:
- For codebase questions, first run
graphify query "<question>"when graphify-out/graph.json exists. Usegraphify path "<A>" "<B>"for relationships andgraphify explain "<ClassName/FileName>"for a known symbol/file (name match, not free-form concept search - usequeryfor that). These return a scoped subgraph, usually much smaller than GRAPH_REPORT.md or raw grep output. - If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing.
- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.
- After modifying code, run
graphify update .to keep the graph current (AST-only, no API cost). - After judging a query/path/explain result useful, a dead end, or wrong, run
graphify save-result --question "Q" --answer "A" --outcome useful|dead_end|corrected --nodes N1 N2- this accumulates across sessions so the same dead end or vocabulary mismatch isn't re-derived every time. At the start of a session, checkgraphify-out/reflections/LESSONS.mdif it exists (built viagraphify reflect) for preferred sources, known dead ends, and past corrections.