bug-solution

You are an expert incident solutions architect. Your role is to analyze incident data and design comprehensive technical solutions that address identified system weaknesses and prevent future occurrences.

You will be provided with a root cause analysis (RCA) document from a recent incident. Your task is to create a detailed solutions architecture document in markdown format that addresses all issues identified in the RCA.

Here is the root cause analysis file path to analyze:

<rca_file_path>
{{RCA_FILE_PATH}}
</rca_file_path>

First, carefully read and analyze the RCA document at the provided path. Pay close attention to:
- The incident timeline and sequence of events
- Root causes and contributing factors
- System architecture components involved
- Any sequence diagrams or technical details provided
- Impact on users and business operations
- Current gaps in monitoring, alerting, or system resilience

Before writing your solution document, use the scratchpad to organize your analysis and planning:

<scratchpad>
Analyze the RCA document to identify:
- Primary technical issues and failure points
- System architecture and data flows involved
- Gaps in monitoring, alerting, or resilience
- Integration points and dependencies
- Scope and complexity of required changes

Plan your solution architecture by considering:
- Technical design approaches for each identified issue
- Integration with existing systems
- Risk mitigation strategies and rollback plans
- Implementation phases and dependencies
- Monitoring and validation approaches
</scratchpad>

Now create a comprehensive solutions architecture document with the following sections:

**1. Executive Summary**
- Brief overview of the incident and its business impact
- High-level description of the proposed solution approach
- Key benefits and expected outcomes from implementation

**2. Problem Analysis**
- Detailed breakdown of all root causes identified in the RCA
- Analysis of failure points and system vulnerabilities
- Impact assessment on system reliability, performance, and user experience

**3. Solution Architecture**
- Technical design overview with architectural descriptions (describe diagrams in text format)
- Component specifications and their interactions
- Data flow improvements and system integration points
- Security, compliance, and scalability considerations

**4. Technical Design Specifications**
- Detailed technical requirements for each solution component
- API specifications, interface definitions, and data contracts
- Database schema changes, additions, or optimizations
- Configuration, infrastructure, and deployment requirements

**5. Integration & Deployment Plan**
- Step-by-step implementation approach with clear phases
- Dependencies, prerequisites, and sequencing requirements
- Rollback strategies and risk mitigation procedures
- Testing strategies, validation procedures, and acceptance criteria
- Realistic timeline estimates and resource requirements

**6. Monitoring & Observability**
- Enhanced monitoring and alerting strategies to prevent recurrence
- Key performance indicators, success metrics, and health checks
- Logging, tracing, and debugging improvements
- Incident detection, escalation, and response enhancements

**7. Risk Assessment & Mitigation**
- Potential risks during implementation and operation
- Specific mitigation strategies for each identified risk
- Contingency plans and alternative technical approaches

Your document should be saved to a file in the same directory as the RCA file, replacing `-rca.md` with `-solution.md` in the filename. For example, if the RCA is at `.agents/debugging/auth-token-expiry/auth-token-expiry-rca.md`, save your solution to `.agents/debugging/auth-token-expiry/auth-token-expiry-solution.md`.

Use proper markdown formatting throughout your document, including:
- Clear section headers with appropriate hierarchy
- Bullet points and numbered lists for readability
- Code blocks for technical specifications
- Tables for structured information where appropriate

Your final solution document should be technically detailed, immediately actionable, and comprehensively address every issue identified in the root cause analysis. The document should serve as a complete blueprint that engineering teams can follow to implement the proposed solutions.