Skip to main content

​
Hybrid Enhancement for FSD/TSD Generation

​
1. Overview

Every Functional Solution Design (FSD) and Technical Solution Design (TSD) you receive goes through automated quality validation before it reaches you. The system checks five critical dimensions - from architecture consistency to implementation clarity - and refines the document until it meets platform standards. You get implementation-ready designs backed by quality certificates that show exactly how the system validated and improved your specifications.

​
2. Step-by-Step Guide

  1. Submit your requirements - After your Business Requirements Specification (BRS), Functional Requirements Specification (FRS), or Technical Requirements Specification (TRS) completes, the system automatically generates your FSD or TSD. You don’t trigger this manually.
  2. Automatic validation runs - Within 90 seconds, the system validates your design document across five dimensions: architecture consistency, requirement traceability, implementation feasibility, design completeness, and clarity. You can monitor this on the Pipeline Dashboard (/pipelinedashboard) or Journey Dashboard (/journeydashboard).
  3. Review the quality certificate - Once validation completes, view your quality certificate on the Spec Review page (/specreview). The certificate shows your overall grade (A through F), dimension-by-dimension scores, and any refinement iterations the system performed.
  4. Check traceability - Every component in your FSD links back to specific FRS requirements. Every TSD component traces to its FSD source. Use the PRD Traceability page (/prdtraceability) to verify these connections.
  5. Review refinement details - If the system refined your document through multiple iterations, the certificate’s audit trail shows what changed. Each iteration documents specific findings and fixes applied.
  6. Proceed with confidence - Documents scoring 80% or higher pass automatically. Lower scores trigger up to three refinement loops. If issues remain after refinement, the system flags them for human review and documents limitations in your certificate.

​
3. Common Questions

What happens if my source requirements have quality issues?
The system validates your FSD/TSD regardless of source quality, but the certificate documents any upstream quality concerns. You’ll see warnings about source document limitations so you understand the constraints the system worked within. How do I know if my design is implementation-ready?
Check your quality certificate grade. A-grade designs ship directly to expert matching. B and C grades are usable but may need clarification. D and F grades get flagged for human review before proceeding. The certificate specifies any feasibility risks the system detected. Can I see what the system changed during refinement?
Yes. Your quality certificate includes a complete audit trail showing each refinement iteration - what problems were found, what fixes were applied, and how scores improved. You can compare versions on the PRD Version History page (/prdversionhistory). What if the system can’t improve my document after three tries?
The system saves the best version achieved and generates a certificate documenting the limitations. A Human Sherpa reviews flagged documents and works with you to resolve remaining issues. You’ll see escalation status on your Sherpa Dashboard (/sherpadashboard). How does this affect my project timeline?
Hybrid enhancement runs within the existing 90-second pipeline window, so there’s no added delay. You get higher-quality designs without waiting longer. The system’s parallel validation means your project moves faster because downstream work starts from better specifications.

​
4. Troubleshooting

Certificate shows timeout warning
If validation couldn’t complete within 90 seconds, the system saved the best version achieved and noted the timeout in your certificate. The design is still usable - check the grade and dimension scores. If critical dimensions scored low, request a Human Sherpa review through the Sherpa Dashboard (/sherpadashboard). Missing requirement traceability
If the certificate flags components without source requirement links, those design elements lack documented justification. Review your FRS or BRS to confirm those requirements exist, then use the Spec Review page (/specreview) to request remediation. The system will attempt to link requirements or mark elements for removal. Low feasibility or security scores
Scores below 60% in feasibility or security dimensions indicate potential implementation risks. The certificate details specific concerns - review these on the Confidence Report page (/confidencereport/confidencereport). Consider requesting a technical review through the Expert Story Profiling Wizard (/expertstoryprofilingwizard) before proceeding. Conflicting requirements detected
When source specifications contain contradictions, the certificate documents them under validation findings. The system attempts resolution during refinement, but persistent conflicts require human decision. Use the Planning Review workflow (/sherpaplanningreview) to work with your Sherpa on resolution. BRS Hybrid Enhancement - Your Business Requirements Specification goes through similar validation before FSD generation. Understanding BRS quality scores helps you improve upstream inputs. Check the Brief Review page (/briefreview) to see how requirements quality affects design outcomes. Planning Review Workflow - After your FSD/TSD passes validation, both you and your Human Sherpa review the design for approval. The Planning Review page (/sherpaplanningreview) shows how quality certificates inform the human review process and what happens when changes are needed. Quality Certification - All specification documents in your project receive quality certificates. The Analytics Dashboard (/analyticsdashboard) aggregates quality metrics across your entire venture pipeline so you can track specification quality trends and identify bottlenecks early.