You are a business analyst tasked with creating a detailed Business Logic document based on the following Frontend FSD and module flow diagram.

Module: {module_name}
Description: {module_description}
Tech Stack: {tech_stack}

Function: {function_name}
Description: {function_description}

Frontend FSD Content:
{fe_fsd_content}

Module Flow:
{module_flow}

Screens Flow:
{Screens_flow}

Please provide a comprehensive Business Logic document with the following sections:

# Overview
[Provide a clear overview of the business logic requirements and objectives]

# Data Models
[Detail the data models and their relationships]
- Entity definitions
- Data types and constraints
- Relationships and dependencies
- Required fields and validations

# Business Rules
[List and explain all business rules]
1. Validation Rules
   - Input validations
   - Business validations
   - Cross-field validations

2. Processing Rules
   - Calculation rules
   - State transition rules
   - Access control rules

3. Domain Rules
   - Industry-specific rules
   - Compliance requirements
   - Business policies

# Processing Logic
[Describe the step-by-step processing logic]
1. Data Flow
   - Input processing
   - Data transformations
   - Output generation

2. Workflows
   - Process sequences
   - Decision points
   - State transitions

3. Algorithms
   - Business calculations
   - Data processing steps
   - Complex operations

# Integration Points
[Document all integration requirements]
1. API Dependencies
   - Required APIs
   - Data formats
   - Authentication

2. External Systems
   - Third-party integrations
   - Data synchronization
   - Communication protocols

3. Service Interactions
   - Service dependencies
   - Message formats
   - Error handling

# Error Handling
[Define error scenarios and handling]
1. Validation Errors
   - Input validation errors
   - Business rule violations
   - Data integrity errors

2. Processing Errors
   - System errors
   - Integration errors
   - Timeout scenarios

3. Recovery Procedures
   - Error recovery steps
   - Fallback mechanisms
   - Data consistency handling

IMPORTANT:
- Provide clear, detailed explanations for each section
- Include specific validation rules and constraints
- Document all business rules with examples
- Detail error scenarios and recovery procedures
- Reference related components and dependencies
- Consider security and compliance requirements