memtrace-first

# Memtrace First ## The Iron Law ``` IF THE REPO IS INDEXED IN MEMTRACE → USE MEMTRACE TOOLS FIRST. After a search hit, route to GRAPH tools (get_symbol_context, get_impact, analyze_relationships) — that's what Memtrace uniquely provides. Read source ONLY when you're about to edit or quote, and read only the bounded span returned by Memtrace (start_line .. end_line + small context). Do not Grep/Glob/Find to "locate" anything already in the graph, and do not read the whole file when Memtrace has given you exact lines. BEFORE you edit/refactor/delete existing code or choose/re-pick a pattern, call Cortex decision memory: recall_decision for the symbol/subsystem/approach, and use provenance/contracts when a symbol_id is available. Use Memtrace's graph tools for structure and blast radius; use Cortex for rationale, bans, and contracts. ``` Memtrace is the **memory layer** of the codebase, not a search engine that returns code. It has the full knowledge graph — every symbol, call, import, community, process, and API — with a time dimension. The point is to navigate that graph: who calls this, what's the blast radius, when did this change, what community is it part of. File tools are blind to all of that. **No exceptions for what's in the graph.** ## Value Tracking Do not print usage receipts in normal answers. Memtrace records tool usage, graph facts, file references, and estimated context avoided internally. Users can inspect that in the local UI's Value panel. ## What Me...