codenavi

Navigating an unfamiliar codebase involves building a persistent, consultable notebook to record findings and map dependencies. This structured approach applies to debugging and refactoring, ensuring surgical analysis and referencing source documentation before acting.

Documenting discoveries during codebase exploration is best handled by storing notes in a centralized, updatable log under a `.notebook/` directory. This enables knowledge reuse across debugging and feature work by capturing decisions and findings methodically.

A structured mission cycle supports refactoring and feature work by following BRIEFING, RECON, PLAN, EXECUTE, VERIFY, and DEBRIEF phases. This approach plans and validates changes methodically, ensuring surgical analysis when investigating incomplete source knowledge.

Code navigation applies across languages and frameworks, especially when source knowledge is incomplete. It investigates with precision, avoids guessing, and references source documentation before acting, making it suitable for diverse and undocumented environments.

To start mapping unknown paths, describe the target codebase and ask the system to begin discovery. It applies a structured mission cycle to explore flows and dependencies, automatically recording findings and decisions in a persistent notebook for reuse.