ring:pre-dev-trd-creation

Technology-agnostic architecture gating establishes HOW/WHERE design decisions and validates data ownership, security, and integration patterns before selecting specific tech stacks. This prevents vendor lock-in and implementation rework.

Define architecture by selecting patterns like modular monolith or microservices over specific technologies, establishing interfaces, and applying Gate 3 prerequisites to validate design completeness independently of products.

You need technology-agnostic architecture patterns for cross-team projects where you must define architecture first, allowing later tech selection like Go or TS stacks without causing implementation rework.

Yes, you validate data ownership and security planning before choosing technologies by using architecture templates and checklists that enforce completeness and agnostic patterns independent of specific products.

Yes, the Gate 3 TRD workflow supports multiple domains by scoping TRD guidance across prerequisites, design validation, and architecture templates to ensure comprehensive architecture completeness across project areas.

Selecting products before defining architecture gates causes vendor lock-in and misaligned implementations, requiring rework when the chosen technology fails to fit required agnostic patterns and data ownership rules.