Stop Letting AI Agents Design Your Architecture

Three organizations in the last month. Same pattern: someone opens Claude, ChatGPT, or Copilot, asks for an architecture, and gets a confident, well-articulated proposal that sounds like it came from a very senior engineer. It hasn't thought about the problem at all — it's pattern-matching against training data.

The core problem: AI is pathologically agreeable

• Ask Claude if microservices make sense for a 3-person team — it will enthusiastically explain why they're excellent.
• Ask if a custom ML pipeline is better than a managed service — it lays out a design.
• Real architects say "no" and push back on complexity. Claude can't.

This isn't lying or being wrong. It's being incapable of the critical skill: knowing what not to build, asking "why" five times, and telling the CTO their conference-inspired idea is terrible for the actual team.

The Jenga tower architecture

The AI-designed output passes the squint test: event-driven here, CQRS there, service mesh. But it's designed for the median of everything Claude has seen — a generic best practice for a generic company. Real architecture requires context:

• Pick Postgres over DynamoDB because your team knows Postgres and you'd rather ship in two weeks than learn a new data model.
• Skip the service mesh because you have four services, not forty.
• Use a monolith because the problem is simple and microservices would be career-driven development.

An AI agent has none of this context — and worse, doesn't know it doesn't have it.

The Jira ticket pipeline

Once the architecture is accepted, the same people ask the AI to break it down. It produces epics, stories, acceptance criteria — ready to drop into Jira. Engineers who spent years honing their craft are now implementing Claude's design, one ticket at a time. The people with the most context become ticket implementers; the entity with the least context makes the architectural decisions.

"But someone senior reviewed it"

A busy tech lead gets handed a coherent proposal with proper terminology and diagrams. How much pushback can they give when the response to "I don't think this is right" is "Claude spent twenty minutes on this and you want to throw it away?"