discover

To generate architecture documentation for project handoff, you can use a system-map approach that analyzes a repository to produce a single docs/system-map.md file. This artifact documents top-level components, dependencies, risks, and open questions with source evidence.

A topological map of subsystems and dependencies is a structural representation identifying top-level components, their files, and how they integrate within a software repository. It serves as evidence-driven architecture documentation for planning and handoff.

Yes, you can analyze read-only codebases of varying sizes to map subsystems, files, dependencies, risks, and open questions. The process identifies repository architecture and produces a system-map artifact for handoff without requiring write access.

To document current state and identified risks for a codebase handoff, generate a system-map artifact containing a Current State narrative and an Identified Risks section. This documentation surfaces gaps and potential failure points with source evidence.

The best way to turn repository analysis into a system map with source evidence is to apply an evidence-driven discovery process that outputs a single docs/system-map.md file. This artifact includes a Topological Map, Current State, Identified Risks, Open Questions, and Source Evidence.

System mapping includes open questions when analyzing repository architecture to surface gaps and potential failure points that require further investigation. This evidence-driven approach ensures the generated docs/system-map.md artifact delivers comprehensive handoff documentation.