Most teams put low-level architecture in the wrong place

This article discusses the common mistake of putting low-level (component) architecture documentation in a central repository, arguing it belongs in the codebase itself. It distinguishes between high-level architecture (business, solution, system) which fits a central repo, and component-level details like middleware choices, request flows, and interface designs. The author explains that keeping this documentation with the code helps both human developers and AI coding agents by providing context, constraints, and specifications exactly where they are needed, ensuring architecture evolves with the code and is versioned.