repo-map-codex

A project map and evidence catalog systematically logs project dependencies, validation surfaces, and risk areas into durable markdown artifacts. This eliminates planning ambiguity by ensuring subsequent development uses verified repository facts rather than assumptions.

The best way to ground AI project planning in actual repository data is to generate an evidence catalog that systematically logs dependencies and validation surfaces. This approach grounds planning in verified repository facts, eliminating planning ambiguity for subsequent development tasks.

Yes, project maps can be generated for business artifact collections. Multi-mode discovery automatically detects project types including software-git, software-no-git, business-artifact, and mixed-business-coding to identify dependencies, risks, and validation surfaces across diverse project structures.

You generate an evidence catalog by analyzing your current directory to identify validation surfaces, dependencies, and risk areas. The process requires read-only filesystem access to read project data and the ability to write structured markdown artifacts to a dedicated planning directory.

Yes, the repository mapping process works with projects that do not use Git. Multi-mode discovery automatically detects software-no-git project types alongside software-git, business-artifact, and mixed-business-coding configurations to map dependencies and risks.

Cataloging project dependencies and risk areas requires read-only access to the project filesystem for analysis and the ability to write structured markdown artifacts to a dedicated planning directory to store the evidence catalog and project map.