audit-protocol

To audit a codebase, you scope the target area, read source files and existing docs, trace component composition and dependencies, and produce new markdown deliverables without modifying any code files.

Codebase traceability is mapping component composition and dependencies to clarify scope for maintainers. You need it when scoping an audit area to understand relationships and generate structured markdown documentation.

Yes, you can generate markdown documentation without modifying source code. The audit process reads source files and existing docs, traces dependencies, and writes only new markdown deliverables.

To trace dependencies and component relationships in a codebase, read source files and existing docs, map how components are composed, and output the traced relationships as structured markdown deliverables.

The best way to scope a codebase audit area is to identify module boundaries, dependencies, and relevant assets first, then read source files to trace composition and generate markdown deliverables for review.

A limitation of generating documentation from existing code is that the process writes only new markdown deliverables and does not modify any source files, meaning code fixes or refactoring must be handled separately.