Map codebase architecture and dependencies

Map codebase services and dependencies into persistent knowledge graph

Creating an auditable, queryable service map across multiple repos when you need to track deployment units and their communication patterns.

• · service list with component_type/domain/owner
• · communication edges (REST/gRPC/Kafka/DB)

• · architecture.md knowledge graph
• · rendered Excalidraw diagrams
• · lint reports (cycles, orphans)

• · Excalidraw Architect MCP (kg_* tools)
• · Read access to codebase

Discovery pass (identify all services) before linking pass (add edges); stable kebab-case IDs across sessions

Parallel edges not supported (same source/target pair replaces); id drift silently corrupts cumulative graph; dangling references fail lint

• · Persistent graph (cumulative)
• · Multi-pass workflow prevents errors
• · Lint catches cycles and dangling refs
• · Domain-based rendering for readability