bmad-method 6.0.0-alpha.0 → 6.0.0-alpha.10

package/src/modules/bmm/workflows/1-analysis/research/instructions-router.md

@@ -1,90 +1,133 @@
 # Research Workflow Router Instructions
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>This is a ROUTER that directs to specialized research instruction sets</critical>
+<critical>Communicate in {communication_language}, generate documents in {document_output_language}</critical>
+<critical>Web research is ENABLED - always use current {{current_year}} data</critical>
+
+<critical>🚨 ANTI-HALLUCINATION PROTOCOL - MANDATORY 🚨</critical>
+<critical>NEVER present information without a verified source - if you cannot find a source, say "I could not find reliable data on this"</critical>
+<critical>ALWAYS cite sources with URLs when presenting data, statistics, or factual claims</critical>
+<critical>REQUIRE at least 2 independent sources for critical claims (market size, growth rates, competitive data)</critical>
+<critical>When sources conflict, PRESENT BOTH views and note the discrepancy - do NOT pick one arbitrarily</critical>
+<critical>Flag any data you are uncertain about with confidence levels: [High Confidence], [Medium Confidence], [Low Confidence - verify]</critical>
+<critical>Distinguish clearly between: FACTS (from sources), ANALYSIS (your interpretation), and SPECULATION (educated guesses)</critical>
+<critical>When using WebSearch results, ALWAYS extract and include the source URL for every claim</critical>
+<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
 
 <!-- IDE-INJECT-POINT: research-subagents -->
 
 <workflow>
 
-<step n="1" goal="Welcome and Research Type Selection">
-<action>Welcome the user to the Research Workflow</action>
-
-**The Research Workflow supports multiple research types:**
-
-Present the user with research type options:
-
-**What type of research do you need?**
-
-1. **Market Research** - Comprehensive market analysis with TAM/SAM/SOM calculations, competitive intelligence, customer segments, and go-to-market strategy
-   - Use for: Market opportunity assessment, competitive landscape analysis, market sizing
-   - Output: Detailed market research report with financials
+<critical>This is a ROUTER that directs to specialized research instruction sets</critical>
 
-2. **Deep Research Prompt Generator** - Create structured, multi-step research prompts optimized for AI platforms (ChatGPT, Gemini, Grok, Claude)
-   - Use for: Generating comprehensive research prompts, structuring complex investigations
-   - Output: Optimized research prompt with framework, scope, and validation criteria
+<step n="1" goal="Validate workflow readiness" tag="workflow-status">
+<action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
+
+<check if="status file not found">
+  <output>No workflow status file found. Research is optional - you can continue without status tracking.</output>
+  <action>Set standalone_mode = true</action>
+</check>
+
+<check if="status file found">
+  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Parse workflow_status section</action>
+  <action>Check status of "research" workflow</action>
+  <action>Get project_level from YAML metadata</action>
+  <action>Find first non-completed workflow (next expected workflow)</action>
+  <action>Pass status context to loaded instruction set for final update</action>
+
+  <check if="research status is file path (already completed)">
+    <output>⚠️ Research already completed: {{research status}}</output>
+    <ask>Re-running will create a new research report. Continue? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Use workflow-status to see your next step.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+  <check if="research is not the next expected workflow (latter items are completed already in the list)">
+    <output>⚠️ Next expected workflow: {{next_workflow}}. Research is out of sequence.</output>
+    <output>Note: Research can provide valuable insights at any project stage.</output>
+    <ask>Continue with Research anyway? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Run {{next_workflow}} instead.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+<action>Set standalone_mode = false</action>
+</check>
+</step>
 
-3. **Technical/Architecture Research** - Evaluate technology stacks, architecture patterns, frameworks, and technical approaches
-   - Use for: Tech stack decisions, architecture pattern selection, framework evaluation
-   - Output: Technical research report with recommendations and trade-off analysis
+<step n="2" goal="Discover research needs through conversation">
 
-4. **Competitive Intelligence** - Deep dive into specific competitors, their strategies, products, and market positioning
-   - Use for: Competitor deep dives, competitive strategy analysis
-   - Output: Competitive intelligence report
+<action>Welcome {user_name} warmly. Position yourself as their research partner who uses live {{current_year}} web data. Ask what they're looking to understand or research.</action>
 
-5. **User Research** - Customer insights, personas, jobs-to-be-done, and user behavior analysis
-   - Use for: Customer discovery, persona development, user journey mapping
-   - Output: User research report with personas and insights
+<action>Listen and collaboratively identify the research type based on what they describe:
 
-6. **Domain/Industry Research** - Deep dive into specific industries, domains, or subject matter areas
-   - Use for: Industry analysis, domain expertise building, trend analysis
-   - Output: Domain research report
+- Market/Business questions → Market Research
+- Competitor questions → Competitive Intelligence
+- Customer questions → User Research
+- Technology questions → Technical Research
+- Industry questions → Domain Research
+- Creating research prompts for AI platforms → Deep Research Prompt Generator
 
-<ask>Select a research type (1-6) or describe your research needs:</ask>
+Confirm your understanding of what type would be most helpful and what it will produce.
+</action>
 
-<action>Capture user selection as {{research_type}}</action>
+<action>Capture {{research_type}} and {{research_mode}}</action>
 
+<template-output>research_type_discovery</template-output>
 </step>
 
-<step n="2" goal="Route to Appropriate Research Instructions">
+<step n="3" goal="Route to Appropriate Research Instructions">
 
 <critical>Based on user selection, load the appropriate instruction set</critical>
 
-<check>If research_type == "1" OR "market" OR "market research":</check>
-<action>Set research_mode = "market"</action>
-<action>LOAD: {installed_path}/instructions-market.md</action>
-<action>Continue with market research workflow</action>
-
-<check>If research_type == "2" OR "prompt" OR "deep research prompt":</check>
-<action>Set research_mode = "deep-prompt"</action>
-<action>LOAD: {installed_path}/instructions-deep-prompt.md</action>
-<action>Continue with deep research prompt generation</action>
-
-<check>If research_type == "3" OR "technical" OR "architecture":</check>
-<action>Set research_mode = "technical"</action>
-<action>LOAD: {installed_path}/instructions-technical.md</action>
-<action>Continue with technical research workflow</action>
-
-<check>If research_type == "4" OR "competitive":</check>
-<action>Set research_mode = "competitive"</action>
-<action>This will use market research workflow with competitive focus</action>
-<action>LOAD: {installed_path}/instructions-market.md</action>
-<action>Pass mode="competitive" to focus on competitive intelligence</action>
-
-<check>If research_type == "5" OR "user":</check>
-<action>Set research_mode = "user"</action>
-<action>This will use market research workflow with user research focus</action>
-<action>LOAD: {installed_path}/instructions-market.md</action>
-<action>Pass mode="user" to focus on customer insights</action>
-
-<check>If research_type == "6" OR "domain" OR "industry":</check>
-<action>Set research_mode = "domain"</action>
-<action>This will use market research workflow with domain focus</action>
-<action>LOAD: {installed_path}/instructions-market.md</action>
-<action>Pass mode="domain" to focus on industry/domain analysis</action>
-
-<critical>The loaded instruction set will continue from here with full context</critical>
+<check if="research_type == 1 OR fuzzy match market research">
+  <action>Set research_mode = "market"</action>
+  <action>LOAD: {installed_path}/instructions-market.md</action>
+  <action>Continue with market research workflow</action>
+</check>
+
+<check if="research_type == 2 or prompt or fuzzy match deep research prompt">
+  <action>Set research_mode = "deep-prompt"</action>
+  <action>LOAD: {installed_path}/instructions-deep-prompt.md</action>
+  <action>Continue with deep research prompt generation</action>
+</check>
+
+<check if="research_type == 3 technical or architecture or fuzzy match indicates technical type of research">
+  <action>Set research_mode = "technical"</action>
+  <action>LOAD: {installed_path}/instructions-technical.md</action>
+  <action>Continue with technical research workflow</action>
+
+</check>
+
+<check if="research_type == 4 or fuzzy match competitive">
+  <action>Set research_mode = "competitive"</action>
+  <action>This will use market research workflow with competitive focus</action>
+  <action>LOAD: {installed_path}/instructions-market.md</action>
+  <action>Pass mode="competitive" to focus on competitive intelligence</action>
+
+</check>
+
+<check if="research_type == 5 or fuzzy match user research">
+  <action>Set research_mode = "user"</action>
+  <action>This will use market research workflow with user research focus</action>
+  <action>LOAD: {installed_path}/instructions-market.md</action>
+  <action>Pass mode="user" to focus on customer insights</action>
+
+</check>
+
+<check if="research_type == 6 or fuzzy match domain or industry or category">
+  <action>Set research_mode = "domain"</action>
+  <action>This will use market research workflow with domain focus</action>
+  <action>LOAD: {installed_path}/instructions-market.md</action>
+  <action>Pass mode="domain" to focus on industry/domain analysis</action>
+</check>
+
+<critical>The loaded instruction set will continue from here with full context of the {research_type}</critical>
 
 </step>
 

package/src/modules/bmm/workflows/1-analysis/research/instructions-technical.md

@@ -1,39 +1,67 @@
 # Technical/Architecture Research Instructions
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>This workflow conducts technical research for architecture and technology decisions</critical>
+<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
+<critical>This is a HIGHLY INTERACTIVE workflow - make technical decisions WITH user, not FOR them</critical>
+<critical>Web research is MANDATORY - use WebSearch tool with {{current_year}} for current version info and trends</critical>
+<critical>ALWAYS verify current versions - NEVER use hardcoded or outdated version numbers</critical>
+<critical>Communicate all responses in {communication_language} and tailor to {user_skill_level}</critical>
+<critical>Generate all documents in {document_output_language}</critical>
+
+<critical>🚨 ANTI-HALLUCINATION PROTOCOL - MANDATORY 🚨</critical>
+<critical>NEVER invent version numbers, features, or technical details - ALWAYS verify with current {{current_year}} sources</critical>
+<critical>Every technical claim (version, feature, performance, compatibility) MUST have a cited source with URL</critical>
+<critical>Version numbers MUST be verified via WebSearch - do NOT rely on training data (it's outdated!)</critical>
+<critical>When comparing technologies, cite sources for each claim (performance benchmarks, community size, etc.)</critical>
+<critical>Mark confidence levels: [Verified {{current_year}} source], [Older source - verify], [Uncertain - needs verification]</critical>
+<critical>Distinguish: FACT (from official docs/sources), OPINION (from community/reviews), SPECULATION (your analysis)</critical>
+<critical>If you cannot find current information about a technology, state: "I could not find recent {{current_year}} data on [X]"</critical>
+<critical>Extract and include source URLs in all technology profiles and comparisons</critical>
+<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
 
 <workflow>
 
-<step n="1" goal="Technical Research Discovery">
-<action>Understand the technical research requirements</action>
+<step n="1" goal="Discover technical research needs through conversation">
 
-**Welcome to Technical/Architecture Research!**
+<action>Engage conversationally based on skill level:
 
-<ask>What technical decision or research do you need?
+<check if="{user_skill_level} == 'expert'">
+  "Let's research the technical options for your decision.
 
-Common scenarios:
+I'll gather current data from {{current_year}}, compare approaches, and help you think through trade-offs.
 
-- Evaluate technology stack for a new project
-- Compare frameworks or libraries (React vs Vue, Postgres vs MongoDB)
-- Research architecture patterns (microservices, event-driven, CQRS)
-- Investigate specific technologies or tools
-- Best practices for specific use cases
-- Performance and scalability considerations
-- Security and compliance research</ask>
+What technical question are you wrestling with?"
+</check>
 
-<template-output>technical_question</template-output>
+<check if="{user_skill_level} == 'intermediate'">
+  "I'll help you research and evaluate your technical options.
+
+We'll look at current technologies (using {{current_year}} data), understand the trade-offs, and figure out what fits your needs best.
+
+What technical decision are you trying to make?"
+</check>
+
+<check if="{user_skill_level} == 'beginner'">
+  "Think of this as having a technical advisor help you research your options.
 
-<ask>What's the context for this decision?
+I'll explain what different technologies do, why you might choose one over another, and help you make an informed decision.
 
-- New greenfield project
-- Adding to existing system (brownfield)
-- Refactoring/modernizing legacy system
-- Proof of concept / prototype
-- Production-ready implementation
-- Academic/learning purpose</ask>
+What technical challenge brought you here?"
+</check>
+</action>
 
+<action>Through conversation, understand:
+
+- **The technical question** - What they need to decide or understand
+- **The context** - Greenfield? Brownfield? Learning? Production?
+- **Current constraints** - Languages, platforms, team skills, budget
+- **What they already know** - Do they have candidates in mind?
+
+Don't interrogate - explore together. If they're unsure, help them articulate the problem.
+</action>
+
+<template-output>technical_question</template-output>
 <template-output>project_context</template-output>
 
 </step>
@@ -82,48 +110,68 @@ Consider:
 
 </step>
 
-<step n="3" goal="Identify Alternatives and Options">
-<action>Research and identify technology options to evaluate</action>
+<step n="3" goal="Discover and evaluate technology options together">
 
-<ask>Do you have specific technologies in mind to compare, or should I discover options?
+<critical>MUST use WebSearch to find current options from {{current_year}}</critical>
 
-If you have specific options, list them. Otherwise, I'll research current leading solutions based on your requirements.</ask>
+<action>Ask if they have candidates in mind:
 
-<check>If user provides options:</check>
-<template-output>user_provided_options</template-output>
+"Do you already have specific technologies you want to compare, or should I search for the current options?"
+</action>
 
-<check>If discovering options:</check>
-<action>Conduct web research to identify current leading solutions</action>
-<action>Search for:
+<action if="user has candidates">Great! Let's research: {{user_candidates}}</action>
 
-- "[technical_category] best tools 2025"
-- "[technical_category] comparison [use_case]"
-- "[technical_category] production experiences reddit"
-- "State of [technical_category] 2025"
-  </action>
+<action if="discovering options">Search for current leading technologies:
 
-<elicit-required/>
+<WebSearch>{{technical_category}} best tools {{current_year}}</WebSearch>
+<WebSearch>{{technical_category}} comparison {{use_case}} {{current_year}}</WebSearch>
+<WebSearch>{{technical_category}} popular frameworks {{current_year}}</WebSearch>
+<WebSearch>state of {{technical_category}} {{current_year}}</WebSearch>
+</action>
+
+<action>Share findings conversationally:
+
+"Based on current {{current_year}} data, here are the main options:
+
+{{discovered_options}}
+
+<check if="{user_skill_level} == 'expert'">
+These are the leaders right now. Which ones make sense to evaluate for your use case?"
+</check>
+
+<check if="{user_skill_level} == 'beginner'">
+Each of these is popular for different reasons. Let me know if you want me to explain what makes each one different."
+</check>
+</action>
 
-<action>Present discovered options (typically 3-5 main candidates)</action>
 <template-output>technology_options</template-output>
 
 </step>
 
-<step n="4" goal="Deep Dive Research on Each Option">
-<action>Research each technology option in depth</action>
+<step n="4" goal="Research each technology together in depth">
 
-<critical>For each technology option, research thoroughly</critical>
+<critical>For each option, use WebSearch to gather CURRENT {{current_year}} information</critical>
 
-<step n="4a" title="Technology Profile" repeat="for-each-option">
+<step n="4a" title="Deep dive on each technology" repeat="for-each-option">
 
-Research and document:
+<action>For {{technology_name}}, conduct comprehensive research:
+
+<WebSearch>{{technology_name}} overview what is {{current_year}}</WebSearch>
+<WebSearch>{{technology_name}} latest version release notes {{current_year}}</WebSearch>
+<WebSearch>{{technology_name}} pros cons trade-offs {{current_year}}</WebSearch>
+<WebSearch>{{technology_name}} production experience real world {{current_year}}</WebSearch>
+<WebSearch>{{technology_name}} vs alternatives comparison {{current_year}}</WebSearch>
+</action>
+
+<action>Share findings conversationally and collaboratively:
+
+"Here's what I found about {{technology_name}}:
 
 **Overview:**
+{{what_it_is_and_solves}}
 
-- What is it and what problem does it solve?
-- Maturity level (experimental, stable, mature, legacy)
-- Community size and activity
-- Maintenance status and release cadence
+**Current Status ({{current_year}}):**
+{{maturity_community_release_cadence}}
 
 **Technical Characteristics:**
 
@@ -172,8 +220,7 @@ Research and document:
 - Training costs
 - Total cost of ownership estimate
 
-<elicit-required/>
-<template-output>tech_profile_{{option_number}}</template-output>
+<template-output>tech*profile*{{option_number}}</template-output>
 
 </step>
 
@@ -283,7 +330,7 @@ For top 2-3 candidates:
 
 <ask>Are you researching architecture patterns (microservices, event-driven, etc.)?</ask>
 
-<check>If yes:</check>
+<check if="yes">
 
 Research and document:
 
@@ -308,6 +355,7 @@ Research and document:
 - Operational overhead
 
 <template-output>architecture_pattern_analysis</template-output>
+</check>
 
 </step>
 
@@ -342,8 +390,6 @@ Research and document:
 - Contingency options if primary choice doesn't work
 - Exit strategy considerations
 
-<elicit-required/>
-
 <template-output>recommendations</template-output>
 
 </step>
@@ -433,10 +479,56 @@ Create ADR format documentation:
 
 Select option (1-5):</ask>
 
-<check>If option 4:</check>
-<action>LOAD: {installed_path}/instructions-deep-prompt.md</action>
-<action>Pre-populate with technical research context</action>
+<check if="option 4">
+  <action>LOAD: {installed_path}/instructions-deep-prompt.md</action>
+  <action>Pre-populate with technical research context</action>
+</check>
 
 </step>
 
+<step n="FINAL" goal="Update status file on completion" tag="workflow-status">
+<check if="standalone_mode != true">
+  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Find workflow_status key "research"</action>
+  <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
+  <action>Update workflow_status["research"] = "{output_folder}/bmm-research-technical-{{date}}.md"</action>
+  <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
+
+<action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
+<action>Determine next agent from path file based on next workflow</action>
+</check>
+
+<output>**✅ Technical Research Complete**
+
+**Research Report:**
+
+- Technical research report generated and saved to {output_folder}/bmm-research-technical-{{date}}.md
+
+{{#if standalone_mode != true}}
+**Status Updated:**
+
+- Progress tracking updated: research marked complete
+- Next workflow: {{next_workflow}}
+  {{else}}
+  **Note:** Running in standalone mode (no progress tracking)
+  {{/if}}
+
+**Next Steps:**
+
+{{#if standalone_mode != true}}
+
+- **Next workflow:** {{next_workflow}} ({{next_agent}} agent)
+- **Optional:** Review findings with architecture team, or run additional analysis workflows
+
+Check status anytime with: `workflow-status`
+{{else}}
+Since no workflow is in progress:
+
+- Review technical research findings
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
+  {{/if}}
+  </output>
+  </step>
+
 </workflow>

package/src/modules/bmm/workflows/1-analysis/research/template-deep-prompt.md

@@ -62,7 +62,7 @@
 
 ---
 
-## Complete Research Prompt (Copy & Paste)
+## Complete Research Prompt (Copy and Paste)
 
 ```
 {{deep_research_prompt}}

package/src/modules/bmm/workflows/1-analysis/research/template-market.md

@@ -22,7 +22,7 @@
 
 ---
 
-## 1. Research Objectives & Methodology
+## 1. Research Objectives and Methodology
 
 ### Research Objectives
 
@@ -293,6 +293,40 @@
 
 ---
 
+## References and Sources
+
+**CRITICAL: All data in this report must be verifiable through the sources listed below**
+
+### Market Size and Growth Data Sources
+
+{{sources_market_size}}
+
+### Competitive Intelligence Sources
+
+{{sources_competitive}}
+
+### Customer Research Sources
+
+{{sources_customer}}
+
+### Industry Trends and Analysis Sources
+
+{{sources_trends}}
+
+### Additional References
+
+{{sources_additional}}
+
+### Source Quality Assessment
+
+- **High Credibility Sources (2+ corroborating):** {{high_confidence_count}} claims
+- **Medium Credibility (single source):** {{medium_confidence_count}} claims
+- **Low Credibility (needs verification):** {{low_confidence_count}} claims
+
+**Note:** Any claim marked [Low Confidence] or [Single source] should be independently verified before making critical business decisions.
+
+---
+
 ## Document Information
 
 **Workflow:** BMad Market Research Workflow v1.0
@@ -305,7 +339,9 @@
 - **Data Freshness:** Current as of {{date}}
 - **Source Reliability:** {{source_reliability_score}}
 - **Confidence Level:** {{confidence_level}}
+- **Total Sources Cited:** {{total_sources}}
+- **Web Searches Conducted:** {{search_count}}
 
 ---
 
-_This market research report was generated using the BMad Method Market Research Workflow, combining systematic analysis frameworks with real-time market intelligence gathering._
+_This market research report was generated using the BMad Method Market Research Workflow, combining systematic analysis frameworks with real-time market intelligence gathering. All factual claims are backed by cited sources with verification dates._

package/src/modules/bmm/workflows/1-analysis/research/template-technical.md

@@ -198,13 +198,48 @@
 
 ---
 
+## References and Sources
+
+**CRITICAL: All technical claims, versions, and benchmarks must be verifiable through sources below**
+
+### Official Documentation and Release Notes
+
+{{sources_official_docs}}
+
+### Performance Benchmarks and Comparisons
+
+{{sources_benchmarks}}
+
+### Community Experience and Reviews
+
+{{sources_community}}
+
+### Architecture Patterns and Best Practices
+
+{{sources_architecture}}
+
+### Additional Technical References
+
+{{sources_additional}}
+
+### Version Verification
+
+- **Technologies Researched:** {{technology_count}}
+- **Versions Verified ({{current_year}}):** {{verified_versions_count}}
+- **Sources Requiring Update:** {{outdated_sources_count}}
+
+**Note:** All version numbers were verified using current {{current_year}} sources. Versions may change - always verify latest stable release before implementation.
+
+---
+
 ## Document Information
 
 **Workflow:** BMad Research Workflow - Technical Research v2.0
 **Generated:** {{date}}
 **Research Type:** Technical/Architecture Research
 **Next Review:** [Date for review/update]
+**Total Sources Cited:** {{total_sources}}
 
 ---
 
-_This technical research report was generated using the BMad Method Research Workflow, combining systematic technology evaluation frameworks with real-time research and analysis._
+_This technical research report was generated using the BMad Method Research Workflow, combining systematic technology evaluation frameworks with real-time research and analysis. All version numbers and technical claims are backed by current {{current_year}} sources._