architecture name standardization

src/modules/bmm/workflows/4-implementation/create-story/checklist.md

@@ -4,7 +4,7 @@ validation-target: 'Newly generated story markdown file'
 required-inputs:
   - 'epics.md (preferred) or PRD'
 optional-inputs:
-  - 'solution-architecture document for architecture context'
+  - 'architecture document for architecture context'
 validation-rules:
   - 'Story structure matches sections: Status, Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Change Log, Dev Agent Record'
   - 'Dev Notes include Project Structure Notes and References subsections'

src/modules/bmm/workflows/4-implementation/create-story/instructions.md

@@ -16,7 +16,7 @@
     <action>Resolve variables from config_source: story_dir (dev_story_location), output_folder, user_name, communication_language. If story_dir missing and {{non_interactive}} == false → ASK user to provide a stories directory and update variable. If {{non_interactive}} == true and missing, HALT with a clear message.</action>
     <action>Create {{story_dir}} if it does not exist</action>
     <action>Resolve installed component paths from workflow.yaml: template, instructions, validation</action>
-    <action>Resolve recommended inputs if present: epics_file, prd_file, solution-architecture_file</action>
+    <action>Resolve recommended inputs if present: epics_file, prd_file, architecture_file</action>
   </step>
 
   <step n="2" goal="Discover and load source documents">
@@ -25,7 +25,7 @@
       1) tech_spec_file (epic-scoped)
       2) epics_file (acceptance criteria and breakdown)
       3) prd_file (business requirements and constraints)
-      4) solution-architecture_file (architecture constraints)
+      4) architecture_file (architecture constraints)
       5) Architecture docs under docs/ and output_folder/: tech-stack.md, unified-project-structure.md, coding-standards.md, testing-strategy.md, backend-architecture.md, frontend-architecture.md, data-models.md, database-schema.md, rest-api-spec.md, external-apis.md (include if present)
     </action>
     <action>READ COMPLETE FILES for all items found in the prioritized set. Store content and paths for citation.</action>
@@ -69,7 +69,7 @@
 
   <step n="4" goal="Extract requirements and derive story statement">
     <action>From tech_spec_file (preferred) or epics_file: extract epic {{epic_num}} title/summary, acceptance criteria for the next story, and any component references. If not present, fall back to PRD sections mapping to this epic/story.</action>
-    <action>From solution-architecture and architecture docs: extract constraints, patterns, component boundaries, and testing guidance relevant to the extracted ACs. ONLY capture information that directly informs implementation of this story.</action>
+    <action>From architecture and architecture docs: extract constraints, patterns, component boundaries, and testing guidance relevant to the extracted ACs. ONLY capture information that directly informs implementation of this story.</action>
     <action>Derive a clear user story statement (role, action, benefit) grounded strictly in the above sources. If ambiguous and {{non_interactive}} == false → ASK user to clarify. If {{non_interactive}} == true → generate the best grounded statement WITHOUT inventing domain facts.</action>
     <template-output file="{default_output_file}">requirements_context_summary</template-output>
   </step>

src/modules/bmm/workflows/4-implementation/create-story/workflow.yaml

@@ -22,7 +22,7 @@ variables:
   story_dir: "{config_source}:dev_story_location" # Directory where stories are stored
   epics_file: "{output_folder}/epics.md" # Preferred source for epic/story breakdown
   prd_file: "{output_folder}/PRD.md" # Fallback for requirements
-  solution-architecture_file: "{output_folder}/architecture.md" # Optional architecture context
+  architecture_file: "{output_folder}/architecture.md" # Optional architecture context
   tech_spec_file: "" # Will be auto-discovered from docs as tech-spec-epic-{{epic_num}}-*.md
   tech_spec_search_dir: "{project-root}/docs"
   tech_spec_glob_template: "tech-spec-epic-{{epic_num}}*.md"
@@ -44,6 +44,6 @@ default_output_file: "{story_dir}/story-{{epic_num}}.{{story_num}}.md"
 recommended_inputs:
   - epics: "Epic breakdown (epics.md)"
   - prd: "PRD document"
-  - solution-architecture: "Solution Architecture (optional)"
+  - architecture: "Architecture (optional)"
 
 web_bundle: false

src/modules/bmm/workflows/4-implementation/epic-tech-context/README.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-Generate a comprehensive Technical Specification for a single epic from PRD, Epics file and Solution Architecture to produce a document with full acceptance criteria and traceability mapping. Creates detailed implementation guidance that bridges business requirements with technical execution.
+Generate a comprehensive Technical Specification for a single epic from PRD, Epics file and Architecture to produce a document with full acceptance criteria and traceability mapping. Creates detailed implementation guidance that bridges business requirements with technical execution.
 
 ## Key Features
 
@@ -35,7 +35,7 @@ workflow tech-spec --input PRD.md --input architecture.md --input front-end-spec
 
 - **output_folder**: Location for generated technical specification
 - **epic_id**: Used in output filename (extracted from PRD or prompted)
-- **recommended_inputs**: PRD, solution-architecture, front-end spec, brownfield notes
+- **recommended_inputs**: PRD, architecture, front-end spec, brownfield notes
 
 ## Workflow Structure
 
@@ -104,7 +104,7 @@ tech-spec/
 ### Output Structure
 
 1. **Overview and Scope** - Project context and boundaries
-2. **System Architecture Alignment** - Connection to solution-architecture
+2. **System Architecture Alignment** - Connection to architecture
 3. **Detailed Design** - Services, data models, APIs, and workflows
 4. **Non-Functional Requirements** - Performance, security, reliability, observability
 5. **Dependencies and Integrations** - External systems and technical dependencies
@@ -116,7 +116,7 @@ tech-spec/
 ## Requirements
 
 - **PRD Document**: Product Requirements Document with clear acceptance criteria
-- **Architecture Document**: solution-architecture or technical design
+- **Architecture Document**: architecture or technical design
 - **Repository Access**: For dependency analysis and framework detection
 - **Epic Context**: Clear epic identification and scope definition
 

src/modules/bmm/workflows/4-implementation/epic-tech-context/instructions.md

@@ -30,11 +30,11 @@
 Status file shows project_level = {{project_level}}.
 
 Tech-spec workflow is typically only needed for Level 3-4 projects.
-For Level 0-2, solution-architecture usually generates tech specs automatically.
+For Level 0-2, architecture usually generates tech specs automatically.
 
 Options:
 1. Continue anyway (manual tech spec generation)
-2. Exit (check if solution-architecture already generated tech specs)
+2. Exit (check if architecture already generated tech specs)
 3. Run workflow-status to verify project configuration
 
 What would you like to do?</ask>
@@ -47,7 +47,7 @@ What would you like to do?</ask>
 
 The status file tracks progress across all workflows and stores project configuration.
 
-Note: This workflow is typically invoked automatically by solution-architecture, or manually for JIT epic tech specs.
+Note: This workflow is typically invoked automatically by architecture, or manually for JIT epic tech specs.
 
 Options:
 1. Run workflow-status first to create the status file (recommended)