devour

Mapping a codebase to understand blast radius involves constructing a grounded atlas of packages, entrypoints, and dependencies to reason about spatial and temporal relationships. This enables safe, non-destructive exploration before risky migrations or refactors.

Documenting codebase architecture for onboarding is done by building a spatial and temporal map of dependencies and persisting it to a MAP.md file at the repo root. This creates bedrock knowledge that enables starting from a mapped state.

A codebase atlas helps with debugging runtime issues by mapping how time moves through the application across packages and dependencies. This spatial and temporal mapping reveals side effects and blast-radius relationships to isolate root causes.

Yes, you can use this codebase mapping approach across multiple coding-agent hosts. It constructs a grounded atlas enforcing non-destructive exploration and safe discovery commands, independent of the specific agent environment.

You persist a codebase dependency map by running an exploration that explicitly saves the atlas to a MAP.md file at the repository root. This ensures future refactoring sessions start from a mapped state rather than rebuilding context.

Non-destructive codebase exploration limits actions to safe discovery commands, preventing direct code modifications during mapping. It enforces explicit atlas persistence rather than automatically mutating codebase files or runtime environments.