architect

Guide architectural decisions by applying pattern-driven frameworks to ensure scalable, maintainable system architecture with security-by-design principles, clear blueprints, and established governance.

Evaluate technology choices by applying proven architectural patterns and industry best practices to select appropriate frameworks, define integration points, and establish clear system interface contracts.

Pattern-driven architectural design works by applying proven industry patterns to technical specifications, ensuring scalable systems through structured blueprints, mandatory PM-Architect collaboration, and governance.

Yes, you can use this for system integration. It defines precise integration points, establishes interface contracts, and creates detailed technical blueprints to ensure maintainable system connections.

Yes, you need to provide project scope and constraints. Mentioning @Architect at the start of a design task with these inputs tailors architectural recommendations to your specific system needs.

Relying solely on patterns for system architecture limits adaptability to novel domain needs, requiring dynamic specialist creation and mandatory PM-Architect collaboration to handle unique governance requirements.