sciagent code + Gitea Actions CI/CD

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

docs/ARCHITECTURE_SUMMARY.md

@@ -0,0 +1,94 @@
+# Architecture Redesign Summary
+
+## Quick Overview
+
+This document provides a quick reference for the architectural improvements proposed for the ProfytAI Compliance Management Platform.
+
+## Key Improvements
+
+### 1. **Layered Architecture**
+- **API Layer**: HTTP request handling, validation, serialization
+- **Application Layer**: Business logic orchestration, use cases
+- **Domain Layer**: Core entities, business rules, interfaces
+- **Infrastructure Layer**: Database, external services, configuration
+
+### 2. **Dependency Injection**
+- Services depend on interfaces, not implementations
+- Easy to test with mocks
+- Flexible to swap implementations
+
+### 3. **Configuration Management**
+- Type-safe settings with Pydantic
+- Environment variable support
+- Centralized configuration
+
+### 4. **Security**
+- JWT authentication
+- CORS with specific origins
+- Rate limiting
+- Input validation at every layer
+
+### 5. **Database Integration**
+- Repository pattern
+- Neo4j integration ready
+- Migration support
+
+## File Structure Comparison
+
+### Before (Current)
+```
+be0/
+├── main.py (545 lines - everything in one file)
+├── src/
+│   ├── compliance_verifier.py
+│   └── utils.py
+```
+
+### After (Proposed)
+```
+be0/
+├── main.py (clean entry point)
+├── src/
+│   ├── api/ (routes, middleware, schemas)
+│   ├── application/ (services, use cases)
+│   ├── domain/ (entities, interfaces)
+│   ├── infrastructure/ (database, external, config)
+│   └── core/ (utilities)
+```
+
+## Migration Checklist
+
+- [ ] Create new directory structure
+- [ ] Set up configuration management
+- [ ] Implement domain entities
+- [ ] Create repository interfaces
+- [ ] Implement repository classes
+- [ ] Create service layer
+- [ ] Split routes into modules
+- [ ] Add authentication/authorization
+- [ ] Implement error handling
+- [ ] Add tests
+- [ ] Update documentation
+
+## Benefits
+
+1. **Maintainability**: Clear structure, easy to find code
+2. **Testability**: Each layer can be tested independently
+3. **Scalability**: Easy to add new features
+4. **Security**: Built-in at every layer
+5. **Team Collaboration**: Different teams can work on different layers
+
+## Next Steps
+
+1. Review `ARCHITECTURE_REDESIGN.md` for detailed design
+2. Review code examples in `be0/src/`
+3. Plan migration timeline
+4. Start with Phase 1 (Foundation)
+
+## Questions?
+
+Refer to the detailed `ARCHITECTURE_REDESIGN.md` document for:
+- Complete architecture explanation
+- Code examples
+- Migration strategy
+- Best practices