The codebase map fact-checks itself against the code

A new engineer joins a 400,000-line repo on Monday. Nobody has written the architecture doc; the three people who could are in the release.

You run Codebase Map, a workflow that ships with the agent. One click. The first pass surveys the repository and drafts the map: modules, boundaries, entry points, where the state lives. The second pass reads the draft against the real code and corrects what the first pass guessed. The output lands as a file in the container the new hire already has a URL to.

The doc isn't a wiki page that rotted in 2024. It was generated from this week's tree and checked against this week's tree, and it can be regenerated next quarter with the same click.