human-architect-mindset

To map domain models before choosing technologies, capture the actual problem space and domain concepts first to ensure domain-first thinking over premature technical bets. This approach prevents misaligned architectures by anchoring system design in actual business logic.

AI-aware problem decomposition breaks complex architectural problems into bounded, verifiable AI tasks with clear input and output contracts. This method evaluates when agentic patterns add real value versus unnecessary complexity during system design.

Navigate constraints during cross-component planning by surfacing technical, organizational, business, and political limitations that shape what can be shipped. This ensures alignment across dependencies and governance requirements before implementation begins.

The best way to plan a multi-service redesign while maintaining compatibility is applying systems thinking to map component interactions, dependencies, and failure modes. This process outputs an Implementation Blueprint and System Diagram to foresee cross-cutting risks.

Yes, this architectural thinking approach evaluates AI-first development by determining when AI tooling, edge inference, or agentic patterns add genuine value versus complexity. It outputs an AI Decomposition Plan to guide verifiable AI task integration.

You should not use domain-first thinking when a problem space is already fully mapped or when cross-component dependencies and constraints are negligible. It is specifically designed for complex, multi-component designs requiring deliberate architectural decisions.