massive architecture creation overhaul

src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/README.md

@@ -41,7 +41,7 @@ The workflow adapts its validation based on project level:
 
 ### Level 3-4 Projects
 
-- Full validation of PRD, solution architecture, and comprehensive stories
+- Full validation of PRD, architecture document, and comprehensive stories
 - Deep cross-reference checking across all artifacts
 - Validates architectural decisions don't introduce scope creep
 - Checks UX artifacts if applicable
@@ -65,7 +65,7 @@ workflow solutioning-gate-check
 The workflow will automatically search your project's output folder for:
 
 - Product Requirements Documents (PRD)
-- Solution Architecture documents
+- Architecture documents
 - Technical Specifications
 - Epic and Story breakdowns
 - UX artifacts (if applicable)
@@ -108,6 +108,13 @@ The workflow uses systematic validation rules adapted to each project level:
 - **Greenfield project setup coverage**
 - **Risk identification and mitigation**
 
+For projects using the new architecture workflow (decision-architecture.md), additional validations include:
+
+- **Implementation patterns defined for consistency**
+- **Technology versions verified and current**
+- **Starter template initialization as first story**
+- **UX specification alignment (if provided)**
+
 ## Special Features
 
 ### Intelligent Adaptation

src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/checklist.md

@@ -7,7 +7,7 @@
 - [ ] PRD exists and is complete (Level 2-4 projects)
 - [ ] PRD contains measurable success criteria
 - [ ] PRD defines clear scope boundaries and exclusions
-- [ ] Solution Architecture document exists (Level 3-4 projects)
+- [ ] Architecture document exists (architecture\*.md) (Level 3-4 projects)
 - [ ] Technical Specification exists with implementation details
 - [ ] Epic and story breakdown document exists
 - [ ] All documents are dated and versioned
@@ -29,6 +29,9 @@
 - [ ] Architecture doesn't introduce features beyond PRD scope
 - [ ] Performance requirements from PRD match architecture capabilities
 - [ ] Security requirements from PRD are fully addressed in architecture
+- [ ] If architecture.md: Implementation patterns are defined for consistency
+- [ ] If architecture.md: All technology choices have verified versions
+- [ ] If UX spec exists: Architecture supports UX requirements
 
 ### PRD to Stories Coverage (Level 2-4)
 
@@ -67,6 +70,7 @@
 ### Greenfield Project Specifics
 
 - [ ] Initial project setup and configuration stories exist
+- [ ] If using architecture.md: First story is starter template initialization command
 - [ ] Development environment setup is documented
 - [ ] CI/CD pipeline stories are included early in sequence
 - [ ] Database/storage initialization stories are properly placed

src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md

@@ -32,7 +32,7 @@ After setup, return here to validate implementation readiness.
 
 - Level 0-1: Tech spec and simple stories only (no PRD, minimal solutioning)
 - Level 2: PRD, tech spec, epics/stories (no separate architecture doc)
-- Level 3-4: Full suite - PRD, solution architecture, epics/stories, possible UX artifacts
+- Level 3-4: Full suite - PRD, architecture document, epics/stories, possible UX artifacts
   </action>
 
 <critical>The validation approach must adapt to the project level - don't look for documents that shouldn't exist at lower levels</critical>
@@ -54,7 +54,7 @@ After setup, return here to validate implementation readiness.
 <action>For Level 2-4 projects, locate:
 
 - Product Requirements Document (PRD)
-- Solution Architecture document (Level 3-4 only)
+- Architecture document (architecture.md) (Level 3-4 only)
 - Technical Specification (Level 2 includes architecture within)
 - Epic and story breakdowns
 - UX artifacts if the active path includes UX workflow
@@ -119,9 +119,10 @@ After setup, return here to validate implementation readiness.
 <action>PRD ↔ Architecture Alignment (Level 3-4):
 
 - Verify every PRD requirement has corresponding architectural support
-- Check that architecture decisions don't contradict PRD constraints
-- Identify any architecture additions beyond PRD scope (potential gold-plating)
-- Ensure non-functional requirements from PRD are addressed in architecture
+- Check that architectural decisions don't contradict PRD constraints
+- Identify any architectural additions beyond PRD scope (potential gold-plating)
+- Ensure non-functional requirements from PRD are addressed in architecture document
+- If using new architecture workflow: verify implementation patterns are defined
   </action>
 
 <action>PRD ↔ Stories Coverage (Level 2-4):

src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/validation-criteria.yaml

@@ -56,9 +56,8 @@ validation_rules:
   level_3_4:
     required_documents:
       - prd
-      - solution_architecture
+      - architecture
       - epics_and_stories
-      - tech_spec # Optional at Level 4
 
     validations:
       - name: "PRD Completeness"
@@ -75,6 +74,9 @@ validation_rules:
           - "Integration points defined"
           - "Security architecture specified"
           - "Performance considerations addressed"
+          - "If architecture.md: Implementation patterns defined"
+          - "If architecture.md: Technology versions verified and current"
+          - "If architecture.md: Starter template command documented (if applicable)"
 
       - name: "PRD-Architecture Alignment"
         checks:
@@ -82,6 +84,8 @@ validation_rules:
           - "NFRs from PRD reflected in architecture"
           - "Technology choices support requirements"
           - "Scalability matches expected growth"
+          - "If UX spec exists: Architecture supports UX requirements"
+          - "If UX spec exists: Component library supports interaction patterns"
 
       - name: "Story Implementation Coverage"
         checks:
@@ -103,6 +107,7 @@ special_contexts:
   greenfield:
     additional_checks:
       - "Project initialization stories exist"
+      - "If using architecture.md: First story is starter template initialization"
       - "Development environment setup documented"
       - "CI/CD pipeline stories included"
       - "Initial data/schema setup planned"

src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml

@@ -27,7 +27,7 @@ default_output_file: "{output_folder}/implementation-readiness-report-{{date}}.m
 # Expected input documents (varies by project level)
 recommended_inputs:
   - prd: "{output_folder}/prd*.md"
-  - architecture: "{output_folder}/solution-architecture*.md"
+  - architecture: "{output_folder}/architecture*.md or {output_folder}/architecture*.md"
   - tech_spec: "{output_folder}/tech-spec*.md"
   - epics_stories: "{output_folder}/epic*.md"
   - ux_artifacts: "{output_folder}/ux*.md"