fullstack-architect

To define scalable architecture across a monorepo, establish consistent repo layouts, shared data contracts, and boundary rules for root Python and web layers. This minimizes cross-layer coupling and maintains project consistency.

The best way to scaffold a new feature area is to generate scaffolded directories alongside typed interfaces and shared data contracts. This enforces boundary rules and minimizes cross-layer coupling from the start.

ADR documentation provides a framework for architecture decisions that guides future work and governance. Recording these decisions in ops/decisions maintains consistency during contract evolution and cross-cutting boundary design.

TypeScript interfaces for shared data contracts should be defined in web/lib/types.ts. This centralizes type definitions to maintain consistency across the web layer and root Python layers.

Yes, you can enforce architecture decisions across both root Python and web layers. The governance framework specifies shared data contracts and boundary rules to maintain consistency across these distinct technology layers.

You need to establish API contracts and system boundaries during repo-wide scaffolding and cross-cutting boundary design. This is essential when starting new feature areas or evolving shared contracts to prevent cross-layer coupling.