principal-architect

To enforce architectural decisions across a full-stack web application, apply governance rules during feature planning and code reviews to guide frontend, backend, and infrastructure choices. This ensures consistency and scalability across the entire stack.

Architectural governance for cross-stack system design is the process of defining decision criteria and consistency rules for technology choices. It aligns frontend, backend, and infrastructure implementation to maintain coherence during feature planning and refactoring.

You need to trigger an architectural review when planning new features, choosing frameworks, or refactoring existing systems. It evaluates pattern tradeoffs and infrastructure decisions to ensure new developments satisfy governance requirements and system scalability.

Guide cross-team implementation across SvelteKit and Drizzle ORM by outlining preferred patterns and technology choices. Establish architectural direction to ensure frontend and backend data flows remain coherent with existing system design and governance triggers.

Yes, you can use this approach for technology choice discussions and refactoring. It reviews tradeoffs between patterns, frameworks, and infrastructure decisions, providing centralized decision criteria to maintain consistency across the platform.