blueprint

Generate architecture documentation by tracing actual imports, calls, and route wiring to build verified component graphs. This approach requires file discovery and citation-backed prose to ensure every documented edge maps to real source files, preventing invented components. Output includes mermaid diagrams and auditable documentation.

Creating mermaid diagrams for a codebase involves analyzing import structures and call graphs to produce validated visual representations. The process traces dependencies across source files, validates diagram edges against actual code paths, and outputs diagrams with line-level citations linking visual elements to specific code locations.

Incremental documentation refresh updates only changed areas by detecting modified files and regenerating their associated sections and diagrams. This scoped approach preserves existing verified citations for unchanged modules while updating component edges and prose explanations for affected source files, reducing processing overhead.

Documenting a specific module uses scoped component analysis to trace imports and calls within a defined boundary. The process discovers files in the target module, maps its internal dependencies, and generates focused architecture documentation with mermaid diagrams and source citations for just that scope.

Blueprint supports repo orientation workflows by generating system overviews from verified source files. It traces imports and calls to produce human-facing architecture documentation with component graphs and mermaid diagrams, helping developers understand codebase structure through auditable, citation-backed explanations rather than guesswork.

Automated codebase diagram generation requires accurate file discovery and import tracing to produce valid results. Complex dynamic imports, runtime dependency injection, or reflection-based wiring may not appear in static call graphs, potentially omitting edges that exist only at runtime despite source file citation requirements.