Skip to main content
This page is the practical map for deciding where a change belongs. It is not a replacement for the technical repository inventory; it is the short version a leader or new contributor can use to orient quickly.

​
Current shape

The generated system map currently records: These values are generated from the repository, not manually maintained. The technical map is regenerated whenever the relevant application surface changes.

​
Where a change belongs

​
How AI navigates the codebase

AI agents do not rely on a giant database dump or an embedding of every file. They follow a small, layered set of maintained artifacts:
  1. Repository rules and verification gates.
  2. Shared domain vocabulary and invariants.
  3. Generated system, route, API, and tool maps.
  4. Curated database metadata that explains purpose, ownership, and known traps.
  5. The smallest relevant source files, tests, migrations, and runtime evidence.
This matters because a technically valid change can still be wrong if it lands in the wrong runtime, bypasses a shared contract, or duplicates an existing owner.

​
Keeping the map current

Pre-commit and CI checks detect stale generated maps. A failed check explains the exact command needed to regenerate the artifact.

​
Why this matters

The map makes impact and ownership visible before a change is made. That lets Alleato scale without creating parallel implementations, undocumented data paths, or AI behavior that only exists in an individual developer’s memory.

​
Further reading