Map your codebase
Before ACE ships features, it studies your code. Mapping turns your repository into a shared source of truth: a record of how your system is built, available to you, your team, and the agents.
Why mapping matters
Knowledge about a codebase is usually scattered across people's heads, and it leaves when they do. Mapping fixes this: everything ACE learns lives in one place, giving the agents the context to make correct changes and giving your team a single reference for how the system works.
Step 1: Map the codebase
- Go to Knowledge → Discovery.
- Start the mapping process.
ACE reads your connected repository and builds a map of your architecture. This takes longer on larger codebases. Let it run to completion.
If Discovery asks you to connect a repository first, complete Connect a repository and come back here.
Step 2: Synthesize the architecture
Once mapping is done, synthesize your architecture. Where mapping records what your code is, synthesis records how it fits together, giving the agents a deeper understanding of the system as a whole.
Explore what ACE learned
Mapping and synthesis populate several views under Knowledge:
- Learn: the detailed map of your architecture, used by both the agents and your team as the source of truth.
- Book Mode: a narrative, high-level view (business rules, vision, stakeholders, personas) aimed at leadership rather than implementation detail.
- Diagrams: a visual companion to Learn, showing how the parts of your system talk to each other.
- Agents: the agents ACE generated for your codebase, such as a General Agent, Front-end Agent, Back-end Agent, and, if you have a separate database repo, a DB Agent.
If your project has several connected repositories, ACE maps them together and generates the right agents for the whole system.
Next steps
Your codebase is mapped and your agents are ready.
- Ship your first feature in the Software Factory.