https://github.com/RinDig/icm-architect Most AI tools try to understand your project by stuffing as much of it as they can into one chat. That is slow, expensive, and they still miss the thing that matters: if I change this, what else breaks? The new System map form walks a repo (or a notes folder) and writes a small catalog instead: - What the pieces are — in your words and in the code’s words (“Chat” is actually called Incubator) - What is real vs leftover vs fake — so nobody builds on a feature that only exists in an old doc - If you change X, what else moves — and what looks related but is the wrong thing You do not get a 40-page audit report. You get index-card pages. A later agent opens the catalog, one card, and the file it points at. That is it. Same idea as the rest of ICM: the folder is the map. A person can open it. An agent can walk it. Nobody has to hold the whole system in their head. Ask it to “map this repo”