architect-first

Prevent architectural drift by enforcing complete design documentation before implementation, validating structural choices via multi-agent review, and running zero-coupling checks to ensure module independence.

Enforce zero coupling by requiring structural validation checks during the architectural phase, ensuring module independence and capability preservation before any implementation code is written.

Externalize mutable configuration to YAML by enforcing it as a non-negotiable architectural rule during the design phase, separating configuration from logic before module implementation begins.

Yes, multi-agent validation requires review by Product Owner, Architect, and User/Stakeholder roles to finalize structural decisions, ensuring capability preservation and reduced implementation risk.

Use the rapid code escape hatch only when pragmatic implementation is necessary and a test-driven safety net with logging and observation points is already in place to prevent fragile deployments.

Implementation stops because the architecture flow uses hard stop rules that block code execution when documentation is missing, coupling is detected, or system capabilities are reduced.