Add full monorepo: virtual-banker, backend, frontend, docs, scripts, deployment

Co-authored-by: Cursor <cursoragent@cursor.com>

docs/specs/deployment/cicd.md

@@ -0,0 +1,73 @@
+# CI/CD Pipeline Specification
+
+## Overview
+
+Continuous Integration and Continuous Deployment pipeline.
+
+## Build Pipeline
+
+### Stages
+
+1. **Source**: Code checkout
+2. **Build**: Compile/build application
+3. **Test**: Run tests
+4. **Package**: Create container images
+5. **Deploy**: Deploy to environment
+
+### Tools
+
+**CI/CD Platform**: GitHub Actions, GitLab CI, or Jenkins
+
+**Build**: Docker build
+**Registry**: Container registry (Docker Hub, ECR, GCR)
+
+## Test Strategy
+
+### Test Types
+
+**Unit Tests**: Component-level tests
+**Integration Tests**: Service integration tests
+**E2E Tests**: End-to-end user flow tests
+
+### Test Execution
+
+- Run on every commit
+- Block deployment on test failures
+- Parallel test execution
+
+## Deployment Strategies
+
+### Blue-Green Deployment
+
+**Method**: Deploy new version alongside old, switch traffic
+**Benefits**: Zero downtime, instant rollback
+**Use Case**: Production deployments
+
+### Canary Deployment
+
+**Method**: Gradually roll out new version to subset of users
+**Benefits**: Risk mitigation, gradual rollout
+**Use Case**: Major updates
+
+## Rollback Procedures
+
+### Automatic Rollback
+
+**Triggers**:
+- Health check failures
+- Error rate spike
+- Performance degradation
+
+### Manual Rollback
+
+**Process**:
+1. Identify issue
+2. Rollback to previous version
+3. Verify rollback success
+4. Investigate issue
+
+## References
+
+- Infrastructure: See `infrastructure.md`
+- Deployment: See `disaster-recovery.md`
+

docs/specs/deployment/disaster-recovery.md

@@ -0,0 +1,69 @@
+# Disaster Recovery Specification
+
+## Overview
+
+Disaster recovery procedures and backup strategies.
+
+## Backup Strategies
+
+### Database Backups
+
+**Full Backups**: Daily full database dumps
+**Incremental Backups**: Continuous WAL archiving (PostgreSQL)
+**Storage**: Off-site backup storage
+**Retention**: 30 days full, 7 days incremental
+
+### Application Backups
+
+**Configuration**: Backup configuration files
+**Secrets**: Secure backup of secrets
+**Code**: Version control (Git)
+
+## Recovery Procedures
+
+### Recovery Scenarios
+
+**1. Database Corruption**:
+- Restore from latest backup
+- Replay WAL logs
+- Verify data integrity
+
+**2. Service Failure**:
+- Restart services
+- Verify health
+- Check logs
+
+**3. Data Center Failure**:
+- Failover to secondary region
+- Restore from backups
+- Verify functionality
+
+### Recovery Testing
+
+**Frequency**: Quarterly
+**Tests**: Restore from backups, verify data integrity
+
+## RTO/RPO Targets
+
+**RTO (Recovery Time Objective)**: 1 hour
+**RPO (Recovery Point Objective)**: 5 minutes (max data loss)
+
+## Multi-Region Failover
+
+### Failover Strategy
+
+**Primary Region**: Active services
+**Secondary Region**: Standby/replica services
+**Failover**: Automatic or manual failover
+
+### Data Replication
+
+**Method**: Database replication, data synchronization
+**Latency**: Acceptable replication lag
+**Consistency**: Eventual consistency acceptable
+
+## References
+
+- Infrastructure: See `infrastructure.md`
+- Scaling: See `scaling.md`
+

docs/specs/deployment/infrastructure.md

@@ -0,0 +1,43 @@
+# Infrastructure as Code Specification
+
+## Overview
+
+Infrastructure as Code (IaC) for containerization and orchestration.
+
+## Containerization Strategy
+
+**Technology**: Docker
+
+**Images**:
+- Application services
+- Indexers
+- APIs
+- Worker processes
+
+## Orchestration Patterns
+
+**Technology**: Kubernetes
+
+**Components**:
+- Deployments: Application services
+- StatefulSets: Database, stateful services
+- Jobs: Batch processing
+- CronJobs: Scheduled tasks
+
+## Service Discovery
+
+**Method**: Kubernetes DNS
+**Service Names**: `service-name.namespace.svc.cluster.local`
+**Internal Communication**: Use service names
+
+## Configuration Management
+
+**Method**: ConfigMaps and Secrets
+**External Config**: Environment variables
+**Secrets**: Kubernetes Secrets or external secret management
+
+## References
+
+- CI/CD: See `cicd.md`
+- Scaling: See `scaling.md`
+

docs/specs/deployment/scaling.md

@@ -0,0 +1,61 @@
+# Scaling Strategy Specification
+
+## Overview
+
+Horizontal and vertical scaling strategies for the platform.
+
+## Horizontal Scaling Patterns
+
+### Application Scaling
+
+**Method**: Add more service instances
+**Auto-scaling**: Based on CPU, memory, request rate
+**Load Balancing**: Distribute traffic across instances
+
+### Database Scaling
+
+**Read Replicas**: Scale read capacity
+**Sharding**: Partition data for write scaling
+**Connection Pooling**: Efficient connection management
+
+## Database Scaling
+
+### Read Replicas
+
+**Strategy**: Multiple read replicas for read-heavy workloads
+**Replication**: Async replication from primary
+**Use Case**: API read operations
+
+### Sharding
+
+**Strategy**: Partition data by chain_id
+**Implementation**: Database partitioning
+**Use Case**: Very large datasets
+
+## Caching Strategy
+
+### Redis Cache
+
+**Use Cases**:
+- API response caching
+- Session storage
+- Rate limiting counters
+- Frequently accessed data
+
+### CDN Caching
+
+**Use Cases**:
+- Static assets
+- API responses (short TTL)
+
+## Load Balancing Configuration
+
+**Method**: Kubernetes service or external load balancer
+**Algorithm**: Round-robin or least connections
+**Health Checks**: Regular health checks, route to healthy instances
+
+## References
+
+- Infrastructure: See `infrastructure.md`
+- CI/CD: See `cicd.md`
+