codebase-memorylisted

# Codebase Memory Codebase Memory is a persistent operational index over explicitly indexed repositories: conceptually a rebuildable projection of source, safe to recreate from its canonical repositories. It is not historical experience memory, not authority for current code, and not required for active-project orientation. Fovea owns the active working-set map, and direct source owns truth: confirm exact code in the JetBrains IDE or direct source before editing or making exhaustive claims. ## Core Principle A rebuildable cross-repository index, not a default step: the graph is a derived projection of source, never historical memory, confirmed against exact current source and tests before use. ## When to Use / NOT - **Use when:** the question spans repositories, services, or explicitly indexed repository revisions: finding which indexed project holds a pattern, comparing a reference candidate, cross-service structure, or non-Pi environments where Fovea is unavailable. - **NOT when:** the active project just needs orientation (use Fovea or direct source). Do not index a current or active owned project merely because the MCP is connected. Index creation requires an explicit user request; a finished project is not ingested by default. Never call `codebase-memory_delete_project` without explicit user approval, and do not write ADRs or ingest traces unless requested (see Boundaries). ## Workflow Use these steps only for graph-assisted work. If relevant source is accessible