What problem does it solve? It turns vague architecture questions ("where should this code live", "monolith or microservices", "which pattern here") into grounded decisions with explicit trade-offs, recorded rationale in ADRs, and C4 diagrams, instead of unrecorded habits that get re-litigated later. ## Core Features & Use Cases - Diagnosis before design: Distinguishes real architecture problems (wrong boundaries, coupling) from issues that belong to code review or performance optimization, and routes accordingly. - Boundary and coupling analysis: Evaluates module frontiers by reason-for-change, dependency direction, and testability, including monolith-vs-services guidance with named criteria. - Decision records and communication: Produces ADRs with discarded alternatives and accepted costs, plus C4-level diagrams matched to the audience. - Use Case: A team debating whether to split a billing module into a separate service gets a comparison of alternatives across maintenance cost, coupling, and reversibility, a clear recommendation, and an ADR documenting why the option was chosen. ## Quick Start Ask the assistant to help decide how to structure a module or whether to split a service, for example: "Should I extract the payment logic into a separate microservice or keep it in the monolith?"
