Architecture knowledge as a link graph

Architecture knowledge is scattered: code, wikis, tickets, people’s heads. Many tools fold it into chat and RAG.

RAG works well for exploration. For answers you need to stand behind, a documentation graph helps: Markdown with explicit links, versioned in Git. Agents traverse edges. Claims stay tied to files (and often code).

That’s what AGM implements. Exploration and decisions can coexist — decisions benefit from stable, reviewable artifacts.