research_codebase_nt

Documenting codebase structure without evaluations involves mapping directories, modules, and dependencies into a read-only, reproducible artifact. This maps the exact current state across components for onboarding and knowledge transfer.

A read-only codebase map is a machine-readable representation of current code structure and dependencies. You need it for auditing, onboarding, or knowledge transfer when you require reproducible documentation without architectural evaluations.

Generate reproducible code documentation for non-standard layouts by spawning parallel research tasks across components. This produces a non-evaluative artifact mapping the codebase exactly as it exists today.

Yes, you can map codebase dependencies and modules without modifying source files by producing a read-only artifact. This approach documents the current state while satisfying the requirement for non-evaluative documentation.

The best way to create a machine-readable map for auditing is to document the current codebase state across components into a reproducible, read-only artifact. This avoids evaluations and maps directories and dependencies as they exist.